From: Andreas Schwab <schwab@suse.de>
To: Robert Pluim <rpluim@gmail.com>
Cc: "Mattias Engdegård" <mattias.engdegard@gmail.com>,
"Chen Zhaoyang" <chenzhauyang@gmail.com>,
emacs-devel@gnu.org
Subject: Re: Escape syntax in docstrings
Date: Tue, 28 Mar 2023 14:27:17 +0200 [thread overview]
Message-ID: <mvm8rfhukm2.fsf@suse.de> (raw)
In-Reply-To: <87sfdpm5sn.fsf@gmail.com> (Robert Pluim's message of "Tue, 28 Mar 2023 14:14:32 +0200")
On Mär 28 2023, Robert Pluim wrote:
>>>>>> On Thu, 23 Mar 2023 23:02:08 +0100, Mattias Engdegård <mattias.engdegard@gmail.com> said:
>
> Mattias> (That Emacs doesn't reject undefined character escape sequences such
> Mattias> as "\y" is not only a constant source of bugs, it also makes it
> Mattias> difficult for us to add new escape sequences without worrying about
> Mattias> breaking some (misguided) code. Almost every other language complain
> Mattias> about this.)
>
> How strict do you want to be? Emacsʼ own source code has some decidely
> non-supported escape sequences, especially when specifying characters
> using the `?\c' syntax.
The elisp manual is explicit that a redundant backslash in ?\c is
ignored, and even recommends its use to avoid confusion in some cases.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-03-28 12:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 20:46 Escape syntax in docstrings Chen Zhaoyang
2023-03-23 22:02 ` Mattias Engdegård
2023-03-24 16:17 ` James Cloos
2023-03-24 21:17 ` Philip Kaludercic
2023-03-28 12:14 ` Robert Pluim
2023-03-28 12:27 ` Andreas Schwab [this message]
2023-03-28 15:23 ` Robert Pluim
2023-03-24 4:04 ` Ruijie Yu via Emacs development discussions.
2023-03-24 4:44 ` Chen Zhaoyang
2023-03-24 18:29 ` Eli Zaretskii
2023-03-24 19:58 ` Chen Zhaoyang
-- strict thread matches above, loose matches on Subject: below --
2023-03-23 22:32 Chen Zhaoyang
2023-03-24 13:22 ` Mattias Engdegård
2023-03-24 15:58 ` David Ongaro
2023-03-24 17:22 ` Chen Zhaoyang
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=mvm8rfhukm2.fsf@suse.de \
--to=schwab@suse.de \
--cc=chenzhauyang@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=rpluim@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).