GNU bug report logs - #31624
27.0; (elisp) `Syntax Flags'

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Mon, 28 May 2018 14:48:01 UTC

Severity: minor

Found in version 27.0

Done: Eli Zaretskii <eliz <at> gnu.org>

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 31624 in the body.
You can then email your comments to 31624 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-gnu-emacs <at> gnu.org:
bug#31624; Package emacs. (Mon, 28 May 2018 14:48: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. (Mon, 28 May 2018 14:48:01 GMT) Full text and rfc822 format available.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: bug-gnu-emacs <at> gnu.org
Subject: 27.0; (elisp) `Syntax Flags'
Date: Mon, 28 May 2018 07:47:09 -0700 (PDT)
Something seems to be missing. This node refers to "a" style, but that
seems to be defined nowhere.  The node defines "comment style" this way:

  A comment style is a set of flags 'b', 'c', and 'n', ...

No mention of style "a" there.  What is style "a"?  I don't see it
specified anywhere.

Presumably style "a" is some set composed of the flags 'b', 'c', and
'n', but what set?

And what about the relation between those "flags" and the "styles"?  If
a flag is an element in a set that is a style, why does the doc use
chars b and c to name both flags and styles - that just confuses things.
If you want to relate style "b" to flag 'b' then maybe use "B", not "b",
as the style name.

(Yes, I realize that this text is very old - at least as old as Emacs
20.  But it seems like it could/should be clearer.)




In GNU Emacs 27.0.50 (build 3, x86_64-w64-mingw32)
 of 2018-03-21
Repository revision: e70d0c9e66d7a8609450b2889869d16aeb0363b5
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --without-dbus --host=x86_64-w64-mingw32
 --without-compress-install -C 'CFLAGS=-O2 -static -g3''




Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#31624; Package emacs. (Mon, 28 May 2018 21:40:01 GMT) Full text and rfc822 format available.

Message #8 received at 31624 <at> debbugs.gnu.org (full text, mbox):

From: Alan Mackenzie <acm <at> muc.de>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 31624 <at> debbugs.gnu.org
Subject: Re: bug#31624: 27.0; (elisp) `Syntax Flags'
Date: 28 May 2018 21:39:44 -0000
Hello, Drew.

In article <mailman.627.1527518890.1292.bug-gnu-emacs <at> gnu.org> you wrote:
> Something seems to be missing. This node refers to "a" style, but that
> seems to be defined nowhere.  The node defines "comment style" this way:

>   A comment style is a set of flags 'b', 'c', and 'n', ...

> No mention of style "a" there.  What is style "a"?  I don't see it
> specified anywhere.

> Presumably style "a" is some set composed of the flags 'b', 'c', and
> 'n', but what set?

When neither flag 'b' nor flag 'c' is set, you have style "a".  

> And what about the relation between those "flags" and the "styles"?

When 'b' is set, you have style "b", when 'c' is set, you have style
"c".  I think having both of them set is undefined (but it does leave
room for a style "d" (shudder!)).

> If a flag is an element in a set that is a style, why does the doc use
> chars b and c to name both flags and styles - that just confuses
> things.  If you want to relate style "b" to flag 'b' then maybe use
> "B", not "b", as the style name.

I think that would be less confusing if something like my first sentence
were in the doc somewhere.

> (Yes, I realize that this text is very old - at least as old as Emacs
> 20.  But it seems like it could/should be clearer.)

I though style "c" was somewhat younger.  Maybe not.  But maybe it could
be clarified.

> In GNU Emacs 27.0.50 (build 3, x86_64-w64-mingw32)
>  of 2018-03-21
> Repository revision: e70d0c9e66d7a8609450b2889869d16aeb0363b5
> Windowing system distributor `Microsoft Corp.', version 6.1.7601
> Configured using:
>  `configure --without-dbus --host=x86_64-w64-mingw32
>  --without-compress-install -C 'CFLAGS=-O2 -static -g3''

-- 
Alan Mackenzie (Nuremberg, Germany).





Information forwarded to bug-gnu-emacs <at> gnu.org:
bug#31624; Package emacs. (Tue, 29 May 2018 13:56:02 GMT) Full text and rfc822 format available.

Message #11 received at 31624 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Alan Mackenzie <acm <at> muc.de>, Drew Adams <drew.adams <at> oracle.com>
Cc: 31624 <at> debbugs.gnu.org
Subject: RE: bug#31624: 27.0; (elisp) `Syntax Flags'
Date: Tue, 29 May 2018 06:55:21 -0700 (PDT)
> When neither flag 'b' nor flag 'c' is set, you have style "a".

If that's the definition of style a then the doc should state that.

> > And what about the relation between those "flags" and the "styles"?
> 
> When 'b' is set, you have style "b", when 'c' is set, you have style
> "c".  I think having both of them set is undefined (but it does leave
> room for a style "d" (shudder!)).
 
> > If a flag is an element in a set that is a style, why does the doc use
> > chars b and c to name both flags and styles - that just confuses
> > things.  If you want to relate style "b" to flag 'b' then maybe use
> > "B", not "b", as the style name.
> 
> I think that would be less confusing if something like my first sentence
> were in the doc somewhere.

Both changes are needed, I think.  It just confuses to use the
same name, with the only difference being single vs double quote
chars around it, for two different concepts/things.

> > (Yes, I realize that this text is very old - at least as old as Emacs
> > 20.  But it seems like it could/should be clearer.)
> 
> I though style "c" was somewhat younger.  Maybe not.  But maybe it could
> be clarified.

You're right - c is not in Emacs 20, for instance.




Reply sent to Eli Zaretskii <eliz <at> gnu.org>:
You have taken responsibility. (Sat, 02 Jun 2018 11:04:02 GMT) Full text and rfc822 format available.

Notification sent to Drew Adams <drew.adams <at> oracle.com>:
bug acknowledged by developer. (Sat, 02 Jun 2018 11:04:03 GMT) Full text and rfc822 format available.

Message #16 received at 31624-done <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Alan Mackenzie <acm <at> muc.de>
Cc: 31624-done <at> debbugs.gnu.org, drew.adams <at> oracle.com
Subject: Re: bug#31624: 27.0; (elisp) `Syntax Flags'
Date: Sat, 02 Jun 2018 14:03:12 +0300
> Date: 28 May 2018 21:39:44 -0000
> From: Alan Mackenzie <acm <at> muc.de>
> Cc: 31624 <at> debbugs.gnu.org
> 
> In article <mailman.627.1527518890.1292.bug-gnu-emacs <at> gnu.org> you wrote:
> > Something seems to be missing. This node refers to "a" style, but that
> > seems to be defined nowhere.  The node defines "comment style" this way:
> 
> >   A comment style is a set of flags 'b', 'c', and 'n', ...
> 
> > No mention of style "a" there.  What is style "a"?  I don't see it
> > specified anywhere.
> 
> > Presumably style "a" is some set composed of the flags 'b', 'c', and
> > 'n', but what set?
> 
> When neither flag 'b' nor flag 'c' is set, you have style "a".  

I added that to the text.

> > And what about the relation between those "flags" and the "styles"?
> 
> When 'b' is set, you have style "b", when 'c' is set, you have style
> "c".  I think having both of them set is undefined (but it does leave
> room for a style "d" (shudder!)).

I added a sentence that explains how styles and flags are related.

Thanks.




bug archived. Request was from Debbugs Internal Request <help-debbugs <at> gnu.org> to internal_control <at> debbugs.gnu.org. (Sat, 30 Jun 2018 11:24:04 GMT) Full text and rfc822 format available.

This bug report was last modified 6 years and 356 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.