all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: acorallo@gnu.org
Cc: 73626@debbugs.gnu.org
Subject: bug#73626: 30.0.91; Type specifiers of functions
Date: Sat, 09 Nov 2024 11:13:31 +0200	[thread overview]
Message-ID: <86zfm8n51g.fsf@gnu.org> (raw)
In-Reply-To: <86seskbi2q.fsf@gnu.org> (message from Eli Zaretskii on Fri, 25 Oct 2024 13:19:41 +0300)

> Cc: 73626@debbugs.gnu.org
> Date: Fri, 25 Oct 2024 13:19:41 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> 
> > From: Andrea Corallo <acorallo@gnu.org>
> > Cc: 73626@debbugs.gnu.org
> > Date: Fri, 25 Oct 2024 05:35:30 -0400
> > 
> > Eli Zaretskii <eliz@gnu.org> writes:
> > 
> > >> > Bottom line: we decided that this information is important enough to
> > >> > show it in the *Help* buffer, so we should explain its arcane parts to
> > >> > make them useful.
> > >> 
> > >> Agree. Is '(elisp)Top > Lisp Data Types' a reasonable place for that?
> > >
> > > Yes, I think so.
> > 
> > Ok gonna work on this.
> 
> Thanks!

Did you have a chance to work on this?





  reply	other threads:[~2024-11-09  9:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 12:25 bug#73626: 30.0.91; Type specifiers of functions Eli Zaretskii
2024-10-19  7:01 ` Eli Zaretskii
2024-10-23 22:29 ` Andrea Corallo
2024-10-24 15:47   ` Eli Zaretskii
2024-10-25  9:35     ` Andrea Corallo
2024-10-25 10:19       ` Eli Zaretskii
2024-11-09  9:13         ` Eli Zaretskii [this message]
2024-11-12 19:17           ` Andrea Corallo
2024-11-14  0:27             ` Andrea Corallo
2024-11-14  7:33               ` Eli Zaretskii
2024-11-19  9:55                 ` Andrea Corallo
2024-11-21 10:52                   ` Eli Zaretskii
2024-11-21 13:15                     ` Andrea Corallo
2024-11-21 13:48                       ` Eli Zaretskii
2024-11-21 14:57                         ` Andrea Corallo
2024-11-16  4:21               ` Richard Stallman

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=86zfm8n51g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73626@debbugs.gnu.org \
    --cc=acorallo@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 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.