From: Eli Zaretskii <eliz@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: me@eshelyaron.com, monnier@iro.umontreal.ca,
aaronjensen@gmail.com, 63988-done@debbugs.gnu.org
Subject: bug#63988: 30.0.50; Recent header line format changes cause spin/seg fault with format-mode-line
Date: Fri, 23 Jun 2023 13:53:39 +0300 [thread overview]
Message-ID: <83pm5m1mbw.fsf@gnu.org> (raw)
In-Reply-To: <83y1kltgeq.fsf@gnu.org> (message from Eli Zaretskii on Thu, 15 Jun 2023 08:59:09 +0300)
> Cc: 63988@debbugs.gnu.org, aaronjensen@gmail.com, monnier@iro.umontreal.ca
> Date: Thu, 15 Jun 2023 08:59:09 +0300
> From: Eli Zaretskii <eliz@gnu.org>
>
> 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.
Time's up, so I've now reverted all the commits that dealt with this
feature, and I'm marking this bug done.
next prev parent reply other threads:[~2023-06-23 10:53 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 [this message]
2023-07-05 15:30 ` Spencer Baugh
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=83pm5m1mbw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63988-done@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--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).