From: Drew Adams <drew.adams@oracle.com>
To: Alan Mackenzie <acm@muc.de>, Drew Adams <drew.adams@oracle.com>
Cc: 31624@debbugs.gnu.org
Subject: bug#31624: 27.0; (elisp) `Syntax Flags'
Date: Tue, 29 May 2018 06:55:21 -0700 (PDT) [thread overview]
Message-ID: <58555cef-923e-4278-abd5-f58a567b808e@default> (raw)
In-Reply-To: <<20180528213944.54389.qmail@mail.muc.de>>
> 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.
next parent reply other threads:[~2018-05-29 13:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<mailman.627.1527518890.1292.bug-gnu-emacs@gnu.org>
[not found] ` <<20180528213944.54389.qmail@mail.muc.de>
2018-05-29 13:55 ` Drew Adams [this message]
2018-05-28 14:47 bug#31624: 27.0; (elisp) `Syntax Flags' Drew Adams
[not found] ` <mailman.627.1527518890.1292.bug-gnu-emacs@gnu.org>
2018-05-28 21:39 ` Alan Mackenzie
2018-06-02 11:03 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=58555cef-923e-4278-abd5-f58a567b808e@default \
--to=drew.adams@oracle.com \
--cc=31624@debbugs.gnu.org \
--cc=acm@muc.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).