unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Andreas Schwab'" <schwab@linux-m68k.org>
Cc: 12270@debbugs.gnu.org
Subject: bug#12270: 24.1.50; (elisp) Syntax Descriptors: "second character, if present"
Date: Fri, 24 Aug 2012 16:14:55 -0700	[thread overview]
Message-ID: <C927C57103064F00A579BF5B4E46EF68@us.oracle.com> (raw)
In-Reply-To: <m2k3wn6hri.fsf@linux-m68k.org>

> > This text does not seem correct to me.  At least it seems unclear.
> >  
> >  "The first character in a syntax descriptor must be a syntax class
> >   designator character.  The second character, if present, 
> specifies a
> >   matching character (e.g. in Lisp, the matching character 
> for `(' is
> >   `)'); a space specifies that there is no matching character."
> >  
> > How can the second char be absent if the third char is present?
> > It is wrong to speak of a char being "present" here, AFAICT.
> > What should be said instead of "present" is non-space:
> >
> >  "The second character, if not a space, specifies..."
> 
> Which third character?

Which?  Why - do you think there can be more than one third char?  "Which"
implies at a choice from a known group of at least two elements.

Perhaps you meant "What", and you meant to ask about the case where there is no
2nd char.

The point is that IF there is a second char (so that we can in fact speak of
"the second char") and IF it is not a space char, then that non-space char
specifies a matching char.  That is what needs to be conveyed.

In the examples given in the node, ". 23" and ". 14", a second char is PRESENT,
and yet it does NOT specify a matching char, because it is a space char.

The doc does say afterward that a space char specifies that there is no matching
char.  Good.  [It follows (but is not said explicitly) that a space char cannot
_be_ a matching char.]

It would be clearer to say "a non-space 2nd char specifies a matching char".
That's the point.  And that's all that needs to be said.

There is a second bug in this text, BTW: The first example is written `". 23"'
and the second is written `. 14'.  One of them, at least, is written wrong.






  reply	other threads:[~2012-08-24 23:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-24 15:45 bug#12270: 24.1.50; (elisp) Syntax Descriptors: "second character, if present" Drew Adams
2012-08-24 22:34 ` Andreas Schwab
2012-08-24 23:14   ` Drew Adams [this message]
2012-08-25  6:28     ` Andreas Schwab
2012-08-25 15:05       ` Drew Adams
2012-08-25 21:26         ` Andreas Schwab
2012-08-26  0:24           ` Drew Adams
2012-08-26  7:00             ` Andreas Schwab
2012-08-26 13:30               ` 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=C927C57103064F00A579BF5B4E46EF68@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=12270@debbugs.gnu.org \
    --cc=schwab@linux-m68k.org \
    /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).