unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 31624-done@debbugs.gnu.org
Subject: bug#31624: 27.0; (elisp) `Syntax Flags'
Date: Sat, 02 Jun 2018 14:03:12 +0300	[thread overview]
Message-ID: <83k1rhe9hr.fsf@gnu.org> (raw)
In-Reply-To: <20180528213944.54389.qmail@mail.muc.de> (message from Alan Mackenzie on 28 May 2018 21:39:44 -0000)

> Date: 28 May 2018 21:39:44 -0000
> From: Alan Mackenzie <acm@muc.de>
> Cc: 31624@debbugs.gnu.org
> 
> In article <mailman.627.1527518890.1292.bug-gnu-emacs@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.





  reply	other threads:[~2018-06-02 11:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
     [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

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=83k1rhe9hr.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31624-done@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).