bug#50658: Error messages including function names violates coding conventions

[Stefan Kangas]

Eli Zaretskii <eliz@gnu.org> writes:

>> 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.

Please find attached a patch.  WDYT?  Too wordy?

0001-Improve-coding-conventions-for-error-messages.patch
Description: Text Data