From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, gregory@heytings.org,
monnier@iro.umontreal.ca, 51883@debbugs.gnu.org
Subject: bug#51883: 29.0.50; Command to get accidentally deleted frames back
Date: Sun, 30 Jan 2022 22:49:13 +0200 [thread overview]
Message-ID: <865yq1dj81.fsf@mail.linkov.net> (raw)
In-Reply-To: <83h79l9jgp.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 30 Jan 2022 20:17:26 +0200")
>> >> So all concerns raised by Eli are addressed now
>> >> that make possible to enable it by default
>> >> as was discussed on emacs-devel:
>> >
>> > Once again, please do NOT enable this by default, I didn't agree to
>> > that. This feature should remain disabled by default for some time,
>> > until we have enough information to discuss whether it should be
>> > turned on by default. As discussed and agreed during its development.
>>
>> But after the recent discussion it was agreed to enable it by default
>> after fixing raised concerns. Everything is fixed now.
>> Should we restart the same discussion again?
>
> I see no need to restart that discussion, since we won't hear anything
> new in it. We made a decision back then, and there's no burning
> reason to change that decision, except that some people would like to
> have that feature turned on -- they can tun it on in their
> customizations.
>
> We discuss stuff and make decisions, and we should stick to our
> decisions unless they turn out to be grave mistakes, which this one
> isn't.
Unfortunately, this is a grave mistake, so it needs more discussion
on emacs-devel.
>> >> @item C-x 5 u
>> >> @kindex C-x 5 u
>> >> @findex undelete-frame
>> >> -@findex undelete-frame-mode
>> >> -When @code{undelete-frame-mode} is enabled, undelete one of the 16
>> >> -most recently deleted frames. Without a prefix argument, undelete the
>> >> -most recently deleted frame. With a numerical prefix argument between
>> >> -1 and 16, where 1 is the most recently deleted frame, undelete the
>> >> -corresponding deleted frame.
>> >> +@findex undelete-frame-max
>> >> +Undelete one of the recently deleted frames. The user option
>> >
>> > "One of the recently deleted frames" sounds like Emacs arbitrarily
>> > decides which one. Which is not what you wanted to say, surely.
>>
>> This was copied from old text: "undelete one of the 16 most recently deleted frames".
>
> Does that mean we must blindly copy it, even if it is confusing?
I will fix this, once the patch is accepted.
>> >> +(defcustom undelete-frame-max 1
>> >> + "Maximum number of deleted frames before oldest are thrown away."
>> >
>> > This doesn't say how to disable the feature.
>>
>> This feature can be disabled by customizing it to 0.
>
> I know. But the doc string keeps silent on that.
Will fix this as well.
>> >> (bindings--define-key menu [undelete-last-deleted-frame]
>> >> '(menu-item "Undelete Frame" undelete-frame
>> >> - :enable (and undelete-frame-mode
>> >> - (car undelete-frame--deleted-frames))
>> >> + :visible (car undelete-frame--deleted-frames)
>> >
>> > I think Gregory didn't like the disappearing item, and preferred it to
>> > be visible at all times, even if disabled.
>>
>> The invisible item makes the already overly long menu shorter,
>> especially for users who don't use frames.
>
> So you basically say we should disregard Gregory's opinion and prefer
> yours?
This definitely needs more discussion, so I'll post the problem's description
on emacs-devel.
next prev parent reply other threads:[~2022-01-30 20:49 UTC|newest]
Thread overview: 87+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 23:38 bug#51883: 29.0.50; Command to get accidentally deleted frames back Michael Heerdegen
2021-11-16 7:53 ` Juri Linkov
2021-11-16 8:14 ` Lars Ingebrigtsen
2021-11-16 20:46 ` Juri Linkov
2021-11-16 8:49 ` Visuwesh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-16 20:20 ` Juri Linkov
2021-11-16 15:17 ` Gregory Heytings
2021-11-16 17:05 ` Gregory Heytings
2021-11-16 17:40 ` Eli Zaretskii
2021-11-16 21:29 ` Gregory Heytings
2021-11-17 10:02 ` Gregory Heytings
2021-11-17 13:11 ` Eli Zaretskii
2021-11-17 17:06 ` Juri Linkov
2021-11-17 17:14 ` Eli Zaretskii
2021-11-19 9:00 ` Gregory Heytings
2021-11-19 12:17 ` Eli Zaretskii
2021-11-24 0:44 ` Gregory Heytings
2021-11-27 11:36 ` Michael Heerdegen
2021-11-27 11:53 ` Gregory Heytings
2021-11-27 12:05 ` Eli Zaretskii
2021-11-27 12:12 ` Gregory Heytings
2021-11-27 12:30 ` Andreas Schwab
2021-11-27 12:34 ` Eli Zaretskii
2021-11-27 12:23 ` Michael Heerdegen
2021-11-27 12:40 ` Eli Zaretskii
2021-11-27 13:22 ` Michael Heerdegen
2021-11-27 13:26 ` Eli Zaretskii
2021-11-27 13:34 ` Michael Heerdegen
2021-11-27 13:56 ` Eli Zaretskii
2021-11-27 13:59 ` Michael Heerdegen
2021-11-27 14:02 ` Eli Zaretskii
2021-11-27 14:08 ` Michael Heerdegen
2021-11-27 14:47 ` Eli Zaretskii
2021-11-27 14:12 ` Gregory Heytings
2021-11-27 14:24 ` Michael Heerdegen
2021-11-27 14:26 ` Gregory Heytings
2021-11-27 14:33 ` Michael Heerdegen
2021-11-27 14:42 ` Gregory Heytings
2021-11-27 14:54 ` Michael Heerdegen
2021-11-27 17:19 ` Gregory Heytings
2021-11-28 15:47 ` Michael Heerdegen
2021-11-29 13:38 ` Gregory Heytings
2021-11-29 18:18 ` Michael Heerdegen
2021-11-29 19:07 ` Michael Heerdegen
2021-11-29 20:19 ` Juri Linkov
2022-01-13 8:32 ` Juri Linkov
2022-01-14 8:12 ` Juri Linkov
2022-01-16 20:59 ` Juri Linkov
2022-01-17 0:08 ` Michael Heerdegen
2022-01-17 8:24 ` Juri Linkov
2022-01-17 13:00 ` Eli Zaretskii
2022-01-17 18:41 ` Juri Linkov
2022-01-17 18:51 ` Eli Zaretskii
2022-01-18 18:30 ` Juri Linkov
2022-01-19 18:37 ` Juri Linkov
2022-01-19 20:17 ` Eli Zaretskii
2021-12-12 2:44 ` Michael Heerdegen
2022-01-10 8:13 ` Michael Heerdegen
2021-11-27 14:48 ` Eli Zaretskii
2021-11-27 12:13 ` Michael Heerdegen
2022-01-22 18:10 ` Juri Linkov
2022-01-21 17:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 18:08 ` Juri Linkov
2022-01-22 21:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 9:11 ` Juri Linkov
2022-01-23 16:01 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 18:12 ` Juri Linkov
2022-01-23 21:26 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-24 18:12 ` Juri Linkov
2022-01-24 18:32 ` Eli Zaretskii
2022-01-25 9:28 ` martin rudalics
2022-01-25 12:29 ` Eli Zaretskii
2022-01-25 15:58 ` martin rudalics
2022-01-27 17:21 ` Juri Linkov
2022-01-27 17:27 ` Eli Zaretskii
2022-01-27 17:48 ` Juri Linkov
2022-01-24 23:00 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-27 17:19 ` Juri Linkov
2022-01-30 16:39 ` Juri Linkov
2022-01-30 16:59 ` Eli Zaretskii
2022-01-30 17:17 ` Juri Linkov
2022-01-30 18:17 ` Eli Zaretskii
2022-01-30 20:49 ` Juri Linkov [this message]
2021-11-16 20:30 ` Juri Linkov
2021-11-17 4:13 ` Richard Stallman
2021-11-17 10:07 ` Gregory Heytings
2021-11-17 16:39 ` bug#51883: [External] : " Drew Adams
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=865yq1dj81.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=51883@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=michael_heerdegen@web.de \
--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).