bug#21871: closed (Emacs Lisp Mode (at least): spurious parens in column 0 don't get bold red highlighting.)

[GNU bug Tracking System]

Your message dated Tue, 21 Sep 2021 16:07:04 -0700
with message-id 
<CADwFkmnPR7NNsRYSq4Q3J-D5ZX--gLPxsxLhjnZ5NsFy_jg6_Q@mail.gmail.com>
and subject line Re: bug#21871: Emacs Lisp Mode (at least): spurious parens in 
column 0 don't get bold red highlighting.
has caused the debbugs.gnu.org bug report #21871,
regarding Emacs Lisp Mode (at least): spurious parens in column 0 don't get 
bold red highlighting.
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
21871: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21871
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Emacs Lisp Mode (at least): spurious parens in column 0 don't get bold red highlighting.
>
>
>
>
> Date: 
>
> Tue, 10 Nov 2015 16:30:34 +0000
>
>
>
>
> User-agent: 
>
> Mutt/1.5.23 (2014-03-12)
>
>
>
>
> 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.
>
> 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).
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#21871: Emacs Lisp Mode (at least): spurious parens in column 0 don't get bold red highlighting.
>
>
>
>
> Date: 
>
> Tue, 21 Sep 2021 16:07:04 -0700
>
>
>
>
> Alan Mackenzie <acm@muc.de> writes:
>
> > 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.  :-)
>
> Excellent!  :-)
>
> I'm therefore closing this bug report.
>
>
> --- End Message ---