From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: peter.mao@gmail.com, 63676@debbugs.gnu.org
Subject: bug#63676: cancelling editable dired causes UI problems with dired
Date: Sat, 27 May 2023 09:26:24 +0300 [thread overview]
Message-ID: <83cz2mjnn3.fsf@gnu.org> (raw)
In-Reply-To: <87pm6msdju.fsf@web.de> (message from Michael Heerdegen on Sat, 27 May 2023 04:39:33 +0200)
> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: Peter Mao <peter.mao@gmail.com>, 63676@debbugs.gnu.org
> Date: Sat, 27 May 2023 04:39:33 +0200
>
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > Currently aborting is more invasive than actually making changes.
>
> Sorry again, not true - obviously I have redefined more stuff in my
> config than I had remembered.
>
> So, personally I try to avoid to revert in all wdired commands,
> because reverting is slow for large buffers and loses information. Is
> there interest to get rid of reverting? dired and wdired have all the
> tools to avoid it.
As I said: the speed of aborting is not really important, IMO. If
reverting loses information, we should restore it after reverting.
next prev parent reply other threads:[~2023-05-27 6:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 4:51 bug#63676: cancelling editable dired causes UI problems with dired Peter Mao
2023-05-24 11:05 ` Eli Zaretskii
2023-05-24 12:09 ` Stephen Berman
2023-05-25 1:14 ` Peter Mao
2023-05-26 9:25 ` Eli Zaretskii
2023-05-26 23:51 ` Michael Heerdegen
2023-05-27 0:55 ` Michael Heerdegen
2023-05-27 2:39 ` Michael Heerdegen
2023-05-27 6:26 ` Eli Zaretskii [this message]
2023-05-27 6:24 ` Eli Zaretskii
2023-05-28 1:36 ` Michael Heerdegen
2023-05-28 4:09 ` Thierry Volpiatto
2023-05-28 5:01 ` Michael Heerdegen
2023-05-28 5:08 ` Thierry Volpiatto
2023-05-28 16:04 ` Drew Adams
2023-05-28 16:21 ` Thierry Volpiatto
2023-05-28 19:17 ` Drew Adams
2023-05-29 3:43 ` Thierry Volpiatto
2023-05-29 5:16 ` Drew Adams
2023-05-29 9:43 ` Thierry Volpiatto
2023-05-29 17:11 ` Drew Adams
2023-05-28 16:05 ` Drew Adams
2023-05-28 3:39 ` Michael Heerdegen
2023-05-28 6:43 ` Eli Zaretskii
2023-05-29 1:35 ` Michael Heerdegen
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=83cz2mjnn3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63676@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=peter.mao@gmail.com \
/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).