From: Eli Zaretskii <eliz@gnu.org>
To: sbaugh@catern.com
Cc: sbaugh@janestreet.com, schwab@linux-m68k.org, 64533-done@debbugs.gnu.org
Subject: bug#64533: [PATCH] Support displaying function name in the header line
Date: Sat, 15 Jul 2023 11:02:50 +0300 [thread overview]
Message-ID: <83v8eld2l1.fsf@gnu.org> (raw)
In-Reply-To: <87r0phkndb.fsf@catern.com> (sbaugh@catern.com)
> From: sbaugh@catern.com
> Date: Sun, 09 Jul 2023 17:26:09 +0000 (UTC)
> Cc: Spencer Baugh <sbaugh@janestreet.com>, schwab@linux-m68k.org,
> 64533@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> +This should be a list of symbols. If it contains 'mode, display
> >> +in the mode line. If it contains 'header, display in the header
> >> +line."
> >
> > Which leaves it to the user to deduce that '(mode header) means both:
> > yet another reason not to prefer this kind of values in user options.
> >
> > It also doesn't tell how to disable this display: another riddle left
> > to the user to solve.
> >
> > Let's always remember that Emacs users are not necessarily experienced
> > Lispers. User options should not be "tricky", especially where such
> > trickery is unjustified. And the doc strings should not pose riddles,
> > however logical they seem to us.
> >
> > Thanks.
>
> Fair point. Back to the single symbol.
Thanks, installed on master, and closing the bug.
next prev parent reply other threads:[~2023-07-15 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 17:56 bug#64533: [PATCH] Support displaying function name in the header line Spencer Baugh
2023-07-08 18:04 ` Eli Zaretskii
2023-07-08 18:14 ` Spencer Baugh
2023-07-08 18:33 ` Eli Zaretskii
2023-07-08 19:26 ` Spencer Baugh
2023-07-08 20:46 ` Andreas Schwab
2023-07-08 20:56 ` Spencer Baugh
2023-07-08 20:58 ` Spencer Baugh
2023-07-09 5:36 ` Eli Zaretskii
2023-07-09 17:26 ` sbaugh
2023-07-15 8:02 ` Eli Zaretskii [this message]
2023-07-09 5:29 ` Eli Zaretskii
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=83v8eld2l1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=64533-done@debbugs.gnu.org \
--cc=sbaugh@catern.com \
--cc=sbaugh@janestreet.com \
--cc=schwab@linux-m68k.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).