unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chen Zhaoyang <chenzhauyang@gmail.com>
To: emacs-devel@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Escape syntax in docstrings
Date: Thu, 23 Mar 2023 17:32:56 -0500	[thread overview]
Message-ID: <877cv7nlnr.fsf@gmail.com> (raw)

Mattias Engdegård <mattias.engdegard@gmail.com> writes:

> Yes, this was changed recently, but I feel vindicated by your report: "\x" never
> meant what the author thought it did (or at least what I think the author
> thought it did): it is a hex escape without digits and used to be equivalent to
> "\000", yielding the control character NUL. Run `C-h f slash-in-docstring` in
> Emacs 29 or older and see for yourself.

Thank you for you clarification! I totally did not know about the fact
that "\x" means NUL in docstrings. 
I do agree that using the slash to represent λ in docstring is not so
good to begin with.

>> (defun agda-input-compose (f g)
>>  "\x -> concatMap F (G x)"
>
> Good catch. Would you tell the Agdas about it?

Yeah, I am grepping for cases like this and will submit a patch to them soon.

>> Can we document this change of behavior? 
>
> Will do.

Cool, thank you again!

-- 
Chen Zhaoyang




             reply	other threads:[~2023-03-23 22:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23 22:32 Chen Zhaoyang [this message]
2023-03-24 13:22 ` Escape syntax in docstrings Mattias Engdegård
2023-03-24 15:58 ` David Ongaro
2023-03-24 17:22   ` Chen Zhaoyang
  -- strict thread matches above, loose matches on Subject: below --
2023-03-23 20:46 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
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

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=877cv7nlnr.fsf@gmail.com \
    --to=chenzhauyang@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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).