unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 24542@debbugs.gnu.org
Subject: bug#24542: 25.1.50; The symbol `@' and sexp scanning
Date: Tue, 03 Jan 2017 08:03:54 -0500	[thread overview]
Message-ID: <87inpw5m85.fsf@users.sourceforge.net> (raw)
In-Reply-To: <87pok48g65.fsf@web.de> (Michael Heerdegen's message of "Tue, 03 Jan 2017 13:46:26 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:
>> `@' has the prefix syntax flag, the elisp manual says `(elisp) Syntax Flags':
>>
>>    * `p' identifies an additional prefix character for Lisp syntax.
>>      These characters are treated as whitespace when they appear between
>>                           ^^^^^^^^^^^^^^^^^^^^^
>>      expressions.  When they appear within an expression, they are
>>      handled according to their usual syntax classes.
>>
>> So (eq element '@) acts the same as (eq element ' ).
>
> I don't agree with your interpretation.  `@' is an (textual
> representation of an) expression in the above example, so "these
> characters" don't "appear between expressions" in this case.  Could be
> that this wording led to a wrong implementation, however.

Well, it's a bit ambiguous whether a character sequence composed soley
of prefix characters should be considered an expression or not.
Obviously the end result is wrong for Lisp, i.e., does not correspond
with what `read' thinks.





  reply	other threads:[~2017-01-03 13:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-25 17:42 bug#24542: 25.1.50; The symbol `@' and sexp scanning Michael Heerdegen
2017-01-02 16:58 ` Michael Heerdegen
2017-01-02 20:37   ` npostavs
2017-01-03 12:46     ` Michael Heerdegen
2017-01-03 13:03       ` npostavs [this message]
2020-09-04 13:05       ` Lars Ingebrigtsen
2020-09-04 13:31         ` Eli Zaretskii
2020-09-04 14:22           ` Stefan Monnier
2024-04-10 23:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-11  3:42   ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-12 17:29     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-12 21:32       ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13  1:55         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87inpw5m85.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=24542@debbugs.gnu.org \
    --cc=michael_heerdegen@web.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).