unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <acorallo@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71117@debbugs.gnu.org, andreas.roehler@easy-emacs.de,
	kevin.legouguec@gmail.com
Subject: bug#71117: 30.0.50; output of describe-function
Date: Wed, 29 May 2024 11:17:39 -0400	[thread overview]
Message-ID: <yp1h6egtzos.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <868qzsuafa.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 29 May 2024 14:25:45 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Andrea Corallo <acorallo@gnu.org>
>> Cc: Eli Zaretskii <eliz@gnu.org>,  71117@debbugs.gnu.org,
>>   andreas.roehler@easy-emacs.de
>> Date: Tue, 28 May 2024 18:25:05 -0400
>> 
>> Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:
>> 
>> > Thinking of e.g. 'C-h 4' (for the "other-window" connotation) or 'C-h H'
>> > (for "current _H_elp buffer"); help-find-source would then be bound to
>> > 'C-h 4 s', for example.
>> >
>> > (info-other-window currently hogs 'C-h 4 i' unfortunately… though
>> > nowadays 'C-x 4 4 i' also works, and 'C-x 4 i' is currently free 🤔
>> >
>> > 'C-x 4 h' is also free to use as a prefix, but maybe a bit of a
>> > fingerful)
>> >
>> > Don't give too much weight to my ramblings; I find 'C-h z' a bit
>> > cryptic, but I don't know that my alternatives are better.
>> 
>> I think those are actually good points, 'C-h z' is not very nice and
>> 'C-h 4 s' would be probably easier to remember as 's' has the same
>> meaning in the *Help* buffer it-self.
>
> I don't want to rebind "C-h 4 i", but "C-h 4 s" or "C-h 4 RET" should
> be good.
>
> This also needs an update in NEWS and the manual.

Okay done, please have a look as usual.

Also, we have a warning now on master because lisp/ldefs-boot.el needs
to be regenerated.  I did run admin/update_autogen but the diff is a
little bigger then I expected (is not only related to the introduced
function).  Should I commit this? Do we have another way to regenerate
ldefs-boot.el we typically use?

Thanks

  Andrea





  reply	other threads:[~2024-05-29 15:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 13:53 bug#71117: 30.0.50; output of describe-function Andreas Röhler
2024-05-22 14:10 ` Eli Zaretskii
2024-05-22 17:46 ` Kévin Le Gouguec
2024-05-22 18:24   ` Eli Zaretskii
2024-05-22 22:22     ` Kévin Le Gouguec
2024-05-23  5:25       ` Eli Zaretskii
2024-05-28 17:44         ` Andrea Corallo
2024-05-28 18:20           ` Eli Zaretskii
2024-05-28 19:42             ` Andrea Corallo
2024-05-28 22:04               ` Kévin Le Gouguec
2024-05-28 22:25                 ` Andrea Corallo
2024-05-29 11:25                   ` Eli Zaretskii
2024-05-29 15:17                     ` Andrea Corallo [this message]
2024-05-29 15:54                       ` Eli Zaretskii
2024-05-29 16:04                         ` Andrea Corallo
2024-05-29 11:38                 ` Eli Zaretskii
2024-05-23  6:28   ` Juri Linkov
2024-05-23 11:51     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-23 17:20       ` Juri Linkov
2024-05-23 20:23         ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=yp1h6egtzos.fsf@fencepost.gnu.org \
    --to=acorallo@gnu.org \
    --cc=71117@debbugs.gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    --cc=eliz@gnu.org \
    --cc=kevin.legouguec@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).