all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Mackenzie <acm@muc.de>,  juri@linkov.net,  emacs-devel@gnu.org
Subject: Re: Unhelpful text in C-h v search-default-mode
Date: Fri, 29 Dec 2023 15:19:48 -0500	[thread overview]
Message-ID: <yp1le9cyd5n.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83tto15j1t.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 29 Dec 2023 13:45:18 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Date: Fri, 29 Dec 2023 10:01:35 +0000
>> Cc: emacs-devel@gnu.org
>> From: Alan Mackenzie <acm@muc.de>
>> 
>> Incidentally, why do we need the long string of hex digits in the subr
>> names F616e....6461_anonymous_lambda_109?  These  are simply the ASCII
>> codes for "anonymous_lambda", and would appear to be utterly
>> superfluous.  They serve only to make it more difficult to use the
>> function name, or to talk about it, and they make the list-timers output
>> much wider than it need be.
>
> Let's ask Andrea (CC'ed) to tell why he decided to use this notation.

I believe it was just to have a unique name, for that probably at the
time I just used the C name.  I welcome patches to improve this if we
feel is important.

  Andrea



      reply	other threads:[~2023-12-29 20:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-24  9:45 Unhelpful text in C-h v search-default-mode Alan Mackenzie
2023-10-25  6:43 ` Juri Linkov
2023-12-29  7:12 ` Juri Linkov
2023-12-29  7:21   ` Emanuel Berg
2023-12-29  7:50   ` Eli Zaretskii
2023-12-29  7:54     ` Eli Zaretskii
2023-12-30 17:40       ` Juri Linkov
2023-12-29 10:01   ` Alan Mackenzie
2023-12-29 10:58     ` Emanuel Berg
2023-12-30 17:43       ` Juri Linkov
2023-12-31  3:23         ` Emanuel Berg
2023-12-29 11:45     ` Eli Zaretskii
2023-12-29 20:19       ` Andrea Corallo [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yp1le9cyd5n.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=acm@muc.de \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.