[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 9a5a35c: ; * doc/lispref/tips.texi (Programming Tips): Fix markup
From: |
Stefan Kangas |
Subject: |
master 9a5a35c: ; * doc/lispref/tips.texi (Programming Tips): Fix markup. |
Date: |
Tue, 28 Sep 2021 09:34:05 -0400 (EDT) |
branch: master
commit 9a5a35c5a65c88ae79c2dce8d5fa63df38418450
Author: Stefan Kangas <stefan@marxist.se>
Commit: Stefan Kangas <stefan@marxist.se>
; * doc/lispref/tips.texi (Programming Tips): Fix markup.
---
doc/lispref/tips.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/doc/lispref/tips.texi b/doc/lispref/tips.texi
index e8f7a3c..fa764f1 100644
--- a/doc/lispref/tips.texi
+++ b/doc/lispref/tips.texi
@@ -396,9 +396,9 @@ An error message should start with a capital letter but
should not end
with a period or other punctuation.
It is occasionally useful to tell the user where an error originated,
-even if @code{debug-on-error} is nil. In such cases, a lower-case
-Lisp symbol can be prepended to the error message. For example, the
-error message ``Invalid input'' could be extended to say
+even if @code{debug-on-error} is @code{nil}. In such cases, a
+lower-case Lisp symbol can be prepended to the error message. For
+example, the error message ``Invalid input'' could be extended to say
``some-function: Invalid input''.
@item
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 9a5a35c: ; * doc/lispref/tips.texi (Programming Tips): Fix markup.,
Stefan Kangas <=