From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: mattiase@acm.org, richardn26@gmail.com, 63722@debbugs.gnu.org
Subject: bug#63722: 29.0.91; (elisp) Skip to end #@00 does not work
Date: Fri, 26 May 2023 13:36:01 +0300 [thread overview]
Message-ID: <83353jl6r2.fsf@gnu.org> (raw)
In-Reply-To: <87353jl8lf.fsf@gmx.de> (message from Michael Albinus on Fri, 26 May 2023 11:56:12 +0200)
> Cc: richardn26@gmail.com, 63722@debbugs.gnu.org
> From: Michael Albinus <michael.albinus@gmx.de>
> Date: Fri, 26 May 2023 11:56:12 +0200
>
> Mattias Engdegård <mattiase@acm.org> writes:
>
> >>> The undocumented #@00 behaviour has indeed been co-opted by parts of
> >>> the community as an 'pretend end-of-file occurs here' mechanism,
> >>
> >> Should this be documented then?
> >
> > I don't think we should do that right now -- the behaviour (read as
> > nil) is not ideal and should not be made permanent; we still have the
> > option to change it (but not in emacs 29, of course).
> >
> > We could also come up with a less obscure replacement syntax, given
> > that there may be a genuine need.
>
> Everything right. But it is used meanwhile in the wild ... perhaps we
> should document then, that this usage is deprecated?
I see no reason to deprecate it, let alone remove it, FWIW.
next prev parent reply other threads:[~2023-05-26 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 14:19 bug#63722: 29.0.91; (elisp) Skip to end #@00 does not work richard newton
2023-05-25 18:44 ` Eli Zaretskii
2023-05-26 9:22 ` Mattias Engdegård
2023-05-26 9:43 ` Michael Albinus
2023-05-26 9:51 ` Mattias Engdegård
2023-05-26 9:56 ` Michael Albinus
2023-05-26 10:36 ` Eli Zaretskii [this message]
2023-05-26 11:55 ` Mattias Engdegård
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=83353jl6r2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63722@debbugs.gnu.org \
--cc=mattiase@acm.org \
--cc=michael.albinus@gmx.de \
--cc=richardn26@gmail.com \
/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).