bug#70039: 30.0.50; list-packages install: Invalid read syntax: "#"

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]

[-- Attachment #1: Type: text/plain, Size: 525 bytes --]


Hello,

got this new error today when trying to install a package with M-x
list-packages.

When I revert this commit:

  7e32e8392ab "Fix recent test regressions"
  (Stefan Monnier <monnier@iro.umontreal.ca> 2024-03-22)

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#.

Attached is a test file.  If you (pp-fill (point-min) (point-max))
you will see this effect happen near the end of that file.


TIA,

Michael.



[-- Attachment #2: pp-fill-test.el --]
[-- Type: application/emacs-lisp, Size: 4394 bytes --]

bug#70039: 30.0.50; list-packages install: Invalid read syntax: "#"

[Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors]

> got this new error today when trying to install a package with M-x
> list-packages.
>
> When I revert this commit:
>
>   7e32e8392ab "Fix recent test regressions"
>   (Stefan Monnier <monnier@iro.umontreal.ca> 2024-03-22)
>
> 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, 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.


        Stefan

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]

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.