From: Spencer Baugh <sbaugh@janestreet.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Eshel Yaron <me@eshelyaron.com>,
63988@debbugs.gnu.org, aaronjensen@gmail.com,
monnier@iro.umontreal.ca
Subject: bug#63988: 30.0.50; Recent header line format changes cause spin/seg fault with format-mode-line
Date: Wed, 05 Jul 2023 11:30:41 -0400 [thread overview]
Message-ID: <ier1qhmjrz2.fsf@janestreet.com> (raw)
In-Reply-To: <83y1kltgeq.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 15 Jun 2023 08:59:09 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Eshel Yaron <me@eshelyaron.com>
>> Cc: aaronjensen@gmail.com, 63988@debbugs.gnu.org, Stefan Monnier
>> <monnier@iro.umontreal.ca>
>> Date: Sat, 10 Jun 2023 12:07:22 +0300
>>
>> > So maybe we should declare this feature a failed experiment and remove
>> > it?
>>
>> FWIW I think that make sense, but IMO it'd be best to only remove the
>> treatment of `:eval` in `window_wants_header_line`, and keep the new
>> treatment of `header-line-format` being a cons cell with a void or
>> nil-valued variable car. That's still useful because it works well with
>> minor mode variables, and it's less risky as it doesn't involve
>> evaluating arbitrary lisp, just inspecting a variable.
>
> Why would it make sense to leave the non-nil car case?
>
> It sounds like the consensus here is that indeed this feature is not
> worth the complications, and so, unless I hear some good reasons not
> to do so, I intend to delete it in a week's time.
Ugh, I am only just now seeing this... I would have appreciated a CC
since I'm the one who requested this feature, or maybe a mail sent to
the original bug report...
Anyway, the reason for this feature remains what is described in
bug#63825: displaying a header line only when there is information to be
displayed in the header line.
Concretely, for which-function-mode: it is nice to have
which-func-format displayed in the header line, but in some kinds of
buffers it does not have any information to display. When a window is
displaying such a buffer, I'd prefer to not have a header line, because
the header line will just be empty.
This use case has no need for the full-fledged :eval mode of this
feature. It works fine with the non-nil car case.
How else should I achieve this?
I could add this functionality to which-func-mode directly: it could
learn to set header-line-format buffer-locally only in buffers that
support which-func-mode. Would that be acceptable? If so I'll send a
patch for that.
next prev parent reply other threads:[~2023-07-05 15:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-10 1:09 bug#63988: 30.0.50; Recent header line format changes cause spin/seg fault with format-mode-line Aaron Jensen
2023-06-10 6:47 ` Eli Zaretskii
2023-06-10 8:56 ` Eli Zaretskii
2023-06-10 9:07 ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-15 5:59 ` Eli Zaretskii
2023-06-16 2:30 ` Aaron Jensen
2023-06-23 10:53 ` Eli Zaretskii
2023-07-05 15:30 ` Spencer Baugh [this message]
2023-07-05 15:40 ` Eli Zaretskii
2023-06-10 16:16 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-10 17:42 ` Eli Zaretskii
2023-06-10 17:51 ` Aaron Jensen
2023-06-10 19:11 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-10 11:08 ` Aaron Jensen
2023-06-10 11:22 ` Eli Zaretskii
2023-06-10 11:59 ` Aaron Jensen
2023-06-10 13:04 ` Eli Zaretskii
2023-06-10 15:06 ` Aaron Jensen
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=ier1qhmjrz2.fsf@janestreet.com \
--to=sbaugh@janestreet.com \
--cc=63988@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=eliz@gnu.org \
--cc=me@eshelyaron.com \
--cc=monnier@iro.umontreal.ca \
/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).