unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Heerdegen via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 70039@debbugs.gnu.org
Subject: bug#70039: 30.0.50; list-packages install: Invalid read syntax: "#"
Date: Fri, 29 Mar 2024 12:51:07 +0100	[thread overview]
Message-ID: <87zfuh2r4k.fsf@web.de> (raw)
In-Reply-To: <jwvjzlmxif4.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 28 Mar 2024 15:34:15 -0400")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> > the problem disappears.  This commit causes a destruction of my custom
> > file when it gets pp-filled, by adding newlines into #N# syntaxes, like
> > #1# => #1\n#.
>
> I pushed a patch to `master` which should fix this problem

Works for me, thanks.

> , but ... this is nasty.  I was thinking "how quickly one forgets how
> hard it is to parse backward" (thinking back to the time where I
> worked on `comment-backward`), but while testing I came across a
> similar problem that occurs because of the (forward) `scan-sexps`
> behavior, so it's even worse than that.

We call this a "wasps' nest" in Germany (of course using German words),
and I make this experience often.

Anyway, if you come along fixing Bug#24542, that would be - it would be
one more wasp less...


Michael.





      reply	other threads:[~2024-03-29 11:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 21:10 bug#70039: 30.0.50; list-packages install: Invalid read syntax: "#" Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-28 19:34 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-29 11:51   ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]

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=87zfuh2r4k.fsf@web.de \
    --to=bug-gnu-emacs@gnu.org \
    --cc=70039@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    --cc=monnier@iro.umontreal.ca \
    /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).