From: Po Lu <luangruo@yahoo.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: emacs-devel@gnu.org, Juri Linkov <juri@linkov.net>
Subject: Re: Undo mode
Date: Fri, 21 Jan 2022 18:51:48 +0800 [thread overview]
Message-ID: <874k5xxsxn.fsf@yahoo.com> (raw)
In-Reply-To: <6d8355dee15cecfbc4af@heytings.org> (Gregory Heytings's message of "Fri, 21 Jan 2022 10:45:58 +0000")
Gregory Heytings <gregory@heytings.org> writes:
> I suggest to wait before such an (unlikely) hypothetical situation
> happens before concluding that something which disfigures the File
> menu must be done.
While the scenario I presented is hypothetical, the problem itself is
not. I spent a minute searching for a way to turn frame undeletion off
after enabling it, to debug a input focus related problem on X.
It turned out to be a bug in either GNOME Shell or XWayland, but at
first it only manifested after I turned on frame undeletion.
> And your hypothetical user can always do M-x undelete-frame TAB to see
> that there is an undelete-frame-mode.
What if he only knows to use `undelete-frame' from the menu bar?
next prev parent reply other threads:[~2022-01-21 10:51 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 20:45 Undo mode Juri Linkov
2022-01-21 0:42 ` Stefan Monnier
2022-01-21 8:16 ` Juri Linkov
2022-01-21 11:44 ` Eli Zaretskii
2022-01-21 13:50 ` Stefan Monnier
2022-01-21 15:07 ` Gregory Heytings
2022-01-21 1:57 ` Po Lu
2022-01-21 3:11 ` [External] : " Drew Adams
2022-01-21 3:40 ` Po Lu
2022-01-21 5:35 ` Drew Adams
2022-01-21 7:56 ` Tracking master (was: [External] : Re: Undo mode) Kévin Le Gouguec
2022-01-21 12:50 ` [External] : Re: Undo mode Stefan Monnier
2022-01-21 16:45 ` Drew Adams
2022-01-21 8:18 ` Juri Linkov
2022-01-21 8:56 ` Lars Ingebrigtsen
2022-01-21 9:15 ` Po Lu
2022-01-21 9:17 ` Lars Ingebrigtsen
2022-01-21 12:52 ` Stefan Monnier
2022-01-21 11:41 ` Eli Zaretskii
2022-01-21 7:17 ` Eli Zaretskii
2022-01-21 10:09 ` Stefan Kangas
2022-01-21 10:19 ` Gregory Heytings
2022-01-21 16:45 ` [External] : " Drew Adams
2022-01-21 11:56 ` Eli Zaretskii
2022-01-22 9:51 ` Stefan Kangas
2022-01-22 10:36 ` Eli Zaretskii
2022-01-22 12:01 ` Stefan Kangas
2022-01-21 8:41 ` Gregory Heytings
2022-01-21 9:40 ` Po Lu
2022-01-21 9:57 ` Gregory Heytings
2022-01-21 10:19 ` Po Lu
2022-01-21 10:26 ` Gregory Heytings
2022-01-21 10:34 ` Po Lu
2022-01-21 10:45 ` Gregory Heytings
2022-01-21 10:51 ` Po Lu [this message]
2022-01-21 12:10 ` Eli Zaretskii
2022-01-21 11:58 ` Eli Zaretskii
2022-01-21 13:50 ` Gregory Heytings
2022-01-21 14:32 ` Eli Zaretskii
2022-01-21 14:48 ` Gregory Heytings
2022-01-21 19:41 ` Eli Zaretskii
2022-01-21 20:58 ` Gregory Heytings
2022-01-22 0:47 ` Po Lu
2022-01-22 7:11 ` Eli Zaretskii
2022-01-22 8:32 ` Gregory Heytings
2022-01-22 8:52 ` Eli Zaretskii
2022-01-22 9:08 ` Gregory Heytings
2022-01-22 9:47 ` Po Lu
2022-01-22 9:51 ` Stefan Kangas
2022-01-22 9:58 ` Po Lu
2022-01-22 10:32 ` Eli Zaretskii
2022-01-22 11:15 ` Gregory Heytings
2022-01-22 11:18 ` Eli Zaretskii
2022-01-22 13:37 ` Gregory Heytings
2022-01-21 11:48 ` Eli Zaretskii
2022-01-21 13:18 ` Yuri Khan
2022-01-21 14:29 ` Eli Zaretskii
2022-01-21 15:07 ` Yuri Khan
2022-01-21 19:22 ` Eli Zaretskii
2022-01-21 16:46 ` [External] : " Drew Adams
2022-01-22 18:04 ` Juri Linkov
2022-01-21 8:55 ` Lars Ingebrigtsen
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=874k5xxsxn.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=gregory@heytings.org \
--cc=juri@linkov.net \
/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).