GNU bug report logs -
#29263
26.0.90; Regression in doc-string highlighting
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Sat, 11 Nov 2017 21:58:01 UTC
Severity: normal
Found in version 26.0.90
Done: Drew Adams <drew.adams <at> oracle.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 29263 in the body.
You can then email your comments to 29263 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#29263
; Package
emacs
.
(Sat, 11 Nov 2017 21:58:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sat, 11 Nov 2017 21:58:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
(defun foo ()
"Why does this show highlighting \* \( \) ??"
nil)
Starting with Emacs 26 this highlights the backslashes differently from
the rest of the doc string (using face `font-lock-warning-face').
This is totally inappropriate. Emacs is trying to be too clever here.
A backslash before `*' or a paren can mean any number of different
things in a doc string.
Consider this bit of a doc string, for instance:
When both optional args are non-nil, the `find' command run is this:
find . -mindepth MIN-DEPTH -maxdepth MAX-DEPTH
\\( -path \*edir1\* -o -path \*edir2\* ... \\)
-prune -o \\( ARGS \\) LS-SWITCHES"
It makes zero sense for `\*' here to have its backslash highlighted.
That just spreads confusion. Any number of other examples can be
imagined. A doc string is, above all, arbitrary natural-language text.
Trying to impose some clever semantics on backslashes is misguided.
Please revert this regressive behavior.
In GNU Emacs 26.0.90 (build 3, x86_64-w64-mingw32)
of 2017-10-13 built on LAPHROAIG
Repository revision: 906224eba147bdfc0514090064e8e8f53160f1d4
Windowing system distributor 'Microsoft Corp.', version 6.1.7601
Recent messages:
For information about GNU Emacs and the GNU system, type C-h C-a.
Saving file d:/usr/drew/drews-lisp-20/1111.el...
Wrote d:/usr/drew/drews-lisp-20/1111.el
Type C-x 1 to delete the help window, C-M-v to scroll help.
Char: \ (92, #o134, #x5c) point=142 of 41521 (0%) column=35
Configured using:
'configure --without-dbus --host=x86_64-w64-mingw32
--without-compress-install 'CFLAGS=-O2 -static -g3''
Configured features:
XPM JPEG TIFF GIF PNG RSVG SOUND NOTIFY ACL GNUTLS LIBXML2 ZLIB
TOOLKIT_SCROLL_BARS
bug closed, send any further explanations to
29263 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com>
Request was from
Drew Adams <drew.adams <at> oracle.com>
to
control <at> debbugs.gnu.org
.
(Sat, 11 Nov 2017 22:03:01 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#29263
; Package
emacs
.
(Sun, 12 Nov 2017 05:21:01 GMT)
Full text and
rfc822 format available.
Message #10 received at 29263 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 11 Nov 2017 13:57:33 -0800 (PST)
> From: Drew Adams <drew.adams <at> oracle.com>
>
> Starting with Emacs 26 this highlights the backslashes differently from
> the rest of the doc string (using face `font-lock-warning-face').
>
> This is totally inappropriate. Emacs is trying to be too clever here.
> A backslash before `*' or a paren can mean any number of different
> things in a doc string.
>
> Consider this bit of a doc string, for instance:
>
> When both optional args are non-nil, the `find' command run is this:
>
> find . -mindepth MIN-DEPTH -maxdepth MAX-DEPTH
> \\( -path \*edir1\* -o -path \*edir2\* ... \\)
> -prune -o \\( ARGS \\) LS-SWITCHES"
>
> It makes zero sense for `\*' here to have its backslash highlighted.
The reason will show itself if you move the mouse pointer on those
backslashes.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#29263
; Package
emacs
.
(Sun, 12 Nov 2017 05:33:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 29263 <at> debbugs.gnu.org (full text, mbox):
> The reason will show itself if you move the mouse pointer on those
> backslashes.
I already closed this, immediately after I opened it.
As you no doubt know.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#29263
; Package
emacs
.
(Sun, 12 Nov 2017 06:09:02 GMT)
Full text and
rfc822 format available.
Message #16 received at 29263 <at> debbugs.gnu.org (full text, mbox):
> Date: Sat, 11 Nov 2017 21:31:53 -0800 (PST)
> From: Drew Adams <drew.adams <at> oracle.com>
> Cc: 29263 <at> debbugs.gnu.org
>
> I already closed this, immediately after I opened it.
> As you no doubt know.
If you close without any message sent to the bug address, then no, I
don't get any messages when you close it.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 10 Dec 2017 12:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 7 years and 274 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.