emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: master ff4de1b: Fix quoting style in Lisp comments


From: Eli Zaretskii
Subject: Re: master ff4de1b: Fix quoting style in Lisp comments
Date: Mon, 13 Sep 2021 14:34:32 +0300

> From: Dmitry Gutov <dgutov@yandex.ru>
> Date: Mon, 13 Sep 2021 01:42:08 +0300
> 
> Hi Eli,
> 
> On 12.09.2021 19:51, Eli Zaretskii wrote:
> > -;; `eval' is hence the core of the culprit.  It's used on:
> > +;; 'eval' is hence the core of the culprit.  It's used on:
> > 
> > -;; encouraged to use `lisp-data-mode' instead.
> > +;; encouraged to use 'lisp-data-mode' instead.
> > 
> > -;; The time- functions below translate nil to `current-time' and
> > -;; accept an integer as of Emacs 25.  `decode-time' and
> > -;; `format-time-string' accept nil on Emacs 24 but don't accept an
> > +;; The time- functions below translate nil to 'current-time' and
> > +;; accept an integer as of Emacs 25.  'decode-time' and
> > +;; 'format-time-string' accept nil on Emacs 24 but don't accept an
> 
> Is this a good idea?

We decided to use this style in plain-text documentation long ago.

> I'm not sure we ever agreed to standardize on straight quotes in Lisp 
> comments (as opposed to plain text files like NEWS).

Comments, NEWS, PROBLEMS, DEBUG, commit log messages (thus the
generated ChangeLog files), and any other form of plain-text
documentation.

> More importantly, the symbol references inside `...' are font-locked 
> with font-lock-constant-face, and references inside '...' do not.

If we want to highlight 'like this' (and I'm not sure we do, but I
won't object if we did), then let's make such a change in font-lock,
by all means.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]