all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Stefan Kangas <stefan@marxist.se>
Cc: 21871@debbugs.gnu.org
Subject: bug#21871: Emacs Lisp Mode (at least): spurious parens in column 0 don't get bold red highlighting.
Date: Mon, 20 Sep 2021 17:50:03 +0000	[thread overview]
Message-ID: <YUjJy9q3HTQBqSUU@ACM> (raw)
In-Reply-To: <CADwFkm=SczZPTJYVr38UUke767cse818WFQCGSrSpOC+aTxUxQ@mail.gmail.com>

Hello, Stefan.

On Sun, Sep 19, 2021 at 15:14:18 -0700, Stefan Kangas wrote:
> Alan Mackenzie <acm@muc.de> writes:

> > Hello, Emacs.

> > In the Emacs manual page "Left Margin Paren", it says that:

> >    To help you catch violations of this convention, Font Lock mode
> >    highlights confusing opening delimiters (those that ought to be quoted)
> >    in bold red.

> > , where "this convention" is the convention of not putting opening parens
> > in column 0 when they aren't at the beginning of defuns.

> > In Emacs Lisp Mode, this highlighting isn't done.  It isn't in CC Mode,
> > either.

> The above text no longer exists, and in Emacs 27.1 or later, we no
> longer treat an unescaped ( in column zero in a docstring as the
> beginning of a defun.  (See `(elisp) Documentation Tips', final
> paragraph.)

> So should this bug be closed, or is there anything more to do here?

I would say it should definitely be closed, the fix that has been
implemented being far and away better than that anticipated by the bug
report.  :-)

> > This is either a bug in the code, or a bug in the documentation.  I
> > rather tend to the view that this bold red highlighting should be done
> > when open-paren-in-column-0-is-defun-start is non-nil.  I think it did,
> > at one stage, but searching the emacs-devel archives doesn't reveal what
> > happened.

-- 
Alan Mackenzie (Nuremberg, Germany).





  reply	other threads:[~2021-09-20 17:50 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 16:30 bug#21871: Emacs Lisp Mode (at least): spurious parens in column 0 don't get bold red highlighting Alan Mackenzie
     [not found] ` <mailman.2066.1447172952.7904.bug-gnu-emacs@gnu.org>
2015-11-12 12:44   ` Alan Mackenzie
2015-11-12 16:36     ` Glenn Morris
2015-11-12 18:12       ` Alan Mackenzie
     [not found] ` <mailman.2173.1447351928.7904.bug-gnu-emacs@gnu.org>
2015-11-12 18:54   ` Alan Mackenzie
2015-11-12 19:17     ` Eli Zaretskii
2016-05-15 21:50     ` Dmitry Gutov
2016-05-16 10:20       ` Alan Mackenzie
2016-05-16 13:18         ` Dmitry Gutov
2016-05-16 15:00           ` Andreas Röhler
2016-05-17  9:02           ` Alan Mackenzie
2017-09-02 13:19             ` Eli Zaretskii
2020-04-11 15:00 ` Noam Postavsky
2021-09-19 22:14 ` Stefan Kangas
2021-09-20 17:50   ` Alan Mackenzie [this message]
2021-09-21 23:07     ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YUjJy9q3HTQBqSUU@ACM \
    --to=acm@muc.de \
    --cc=21871@debbugs.gnu.org \
    --cc=stefan@marxist.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.