[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#51883: 29.0.50; Command to get accidentally deleted frames back
From: |
Eli Zaretskii |
Subject: |
bug#51883: 29.0.50; Command to get accidentally deleted frames back |
Date: |
Wed, 17 Nov 2021 19:14:31 +0200 |
> From: Juri Linkov <juri@linkov.net>
> Cc: Gregory Heytings <gregory@heytings.org>, 51883@debbugs.gnu.org,
> michael_heerdegen@web.de
> Date: Wed, 17 Nov 2021 19:06:06 +0200
>
> >> + (bindings--define-key menu [undelete-last-deleted-frame]
> >> + '(menu-item "Undelete Frame" undelete-frame
> >> + :enable undelete-frame-mode
> >> + :help "Undelete last deleted frame"))
> >
> > How about using "restore" instead of "undelete", here and everywhere
> > else? I think it's a tad more clear, and also easier to understand,
> > as it doesn't use negative tense.
>
> Michael pointed out that "restore" is a too confusing name
> where "restore" is opposite to making a frame fullscreen.
And I raised a brow when reading that. "Restore" is a very far cry
from "fullscreen". OTOH, browsers that keep history use "restore", so
I thought it will be a better terminology here.
> OTOH, "undelete" is similar to "undo", so "undelete" better explains
> what it does.
The difference is that "undo" is widely accepted terminology for what
that does.
> And the main advantage of the name "undelete-frame" is that it's
> immediately clear that it's opposite to "delete-frame".
But undelete-frame (the command) is NOT the opposite of delete-frame,
because it doesn't just delete the last frame you deleted.
Anyway, I don't intend to argue more; if you are unhappy with my
proposal, so be it.
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, (continued)
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Visuwesh, 2021/11/16
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Gregory Heytings, 2021/11/16
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Gregory Heytings, 2021/11/16
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Eli Zaretskii, 2021/11/16
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Gregory Heytings, 2021/11/16
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Gregory Heytings, 2021/11/17
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Eli Zaretskii, 2021/11/17
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Juri Linkov, 2021/11/17
- bug#51883: 29.0.50; Command to get accidentally deleted frames back,
Eli Zaretskii <=
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Gregory Heytings, 2021/11/19
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Eli Zaretskii, 2021/11/19
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Gregory Heytings, 2021/11/23
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Michael Heerdegen, 2021/11/27
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Gregory Heytings, 2021/11/27
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Eli Zaretskii, 2021/11/27
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Gregory Heytings, 2021/11/27
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Andreas Schwab, 2021/11/27
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Eli Zaretskii, 2021/11/27
- bug#51883: 29.0.50; Command to get accidentally deleted frames back, Michael Heerdegen, 2021/11/27