unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: 71117@debbugs.gnu.org, acorallo@gnu.org, andreas.roehler@easy-emacs.de
Subject: bug#71117: 30.0.50; output of describe-function
Date: Wed, 29 May 2024 14:38:49 +0300	[thread overview]
Message-ID: <865xuwu9ti.fsf@gnu.org> (raw)
In-Reply-To: <87r0dl4mqd.fsf@gmail.com> (message from Kévin Le Gouguec on Wed, 29 May 2024 00:04:26 +0200)

> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: Eli Zaretskii <eliz@gnu.org>,  71117@debbugs.gnu.org,
>   andreas.roehler@easy-emacs.de
> Date: Wed, 29 May 2024 00:04:26 +0200
> 
> I don't actually have concrete examples where my allegedly-not-so-smart
> serving suggestion might fail 😉 The best I can come up with are
> what-ifs, e.g. "what if a user advises describe-* functions to rename
> *Help* buffers to something non-standard like *Help <SYM>*";

First, AFAICT describe-* functions don't know about the name of the
buffer.  So advising them will not affect the buffer name.

Second, if someone advises the functions which do know about that,
they have an uphill battle to fight, and IMNSHO they get what they
deserve.

Last, but not least, if we want to be holier that the Pope, we can use
the function help-buffer to get at the buffer, whatever its name.





  parent reply	other threads:[~2024-05-29 11:38 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
2024-05-29 15:54                       ` Eli Zaretskii
2024-05-29 16:04                         ` Andrea Corallo
2024-05-29 11:38                 ` Eli Zaretskii [this message]
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=865xuwu9ti.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71117@debbugs.gnu.org \
    --cc=acorallo@gnu.org \
    --cc=andreas.roehler@easy-emacs.de \
    --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).