[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#50658: Error messages including function names violates coding conve
From: |
Eli Zaretskii |
Subject: |
bug#50658: Error messages including function names violates coding conventions |
Date: |
Sat, 18 Sep 2021 18:00:00 +0300 |
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 18 Sep 2021 07:54:26 -0700
> Cc: 50658@debbugs.gnu.org
>
> While working on this, I realized that it is impossible to know if in
> something like:
>
> (error "frobnicator not available")
>
> The 'frobnicator' part is a Lisp symbol (that can be in lower-case), or
> if it is a regular word (that must be capitalized). It would obviously
> be helpful if our conventions could be unambiguous.
>
> Perhaps we could add a requirement here, something like: a Lisp symbol
> must always be in `quotes', or behind ": "?
Yes, I think the idea is that the error message proper starts after
the colon.
> (I guess this would also affect the text we want to put in `(elisp)
> Documentation Tips'.)
Yes.
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/18
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/18
- bug#50658: Error messages including function names violates coding conventions,
Eli Zaretskii <=
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/27
- bug#50658: Error messages including function names violates coding conventions, Eli Zaretskii, 2021/09/28
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/28
- bug#50658: Error messages including function names violates coding conventions, Eli Zaretskii, 2021/09/28
- bug#50658: Error messages including function names violates coding conventions, Stefan Kangas, 2021/09/28