From: Thierry Volpiatto <thievol@posteo.net>
To: Drew Adams <drew.adams@oracle.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
"peter.mao@gmail.com" <peter.mao@gmail.com>,
Eli Zaretskii <eliz@gnu.org>,
"63676@debbugs.gnu.org" <63676@debbugs.gnu.org>
Subject: bug#63676: cancelling editable dired causes UI problems with dired
Date: Sun, 28 May 2023 16:21:09 +0000 [thread overview]
Message-ID: <871qj0e7zs.fsf@posteo.net> (raw)
In-Reply-To: <SJ0PR10MB5488F158F1C89057D9B6BAC9F3459@SJ0PR10MB5488.namprd10.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 1012 bytes --]
Hello Drew,
Drew Adams <drew.adams@oracle.com> writes:
> With Dired+ you can create a Dired buffer for any
> arbitrary list of files & dirs, even interactively,
> in several ways. Such a buffer isn't connected
> with any particular directory listings (whether by
> `ls' or ls-lisp).
>
> E.g., commands `diredp-marked(-other-window)' do
> it for the marked files & dirs in a Dired buffer.
> (`C-M-*' is bound to `diredp-marked-other-window'.)
>
> You can then use WDired on such buffer, to make any
> changes you like.
>
> Dired+ hasn't tried to fix any WDired problems, so
> some WDired problems that you pointed to might
> still be problematic with Dired+; dunno.
Should work fine with emacs-29+ and broken before (needed a patched Wdired).
> I'm not an expert on WDired, and I haven't tried to look into use
> cases etc. But for the case you describe it seems to work OK
> (superficial testing).
>
>
> https://www.emacswiki.org/emacs/download/dired%2b.el
--
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2023-05-28 16:21 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
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 [this message]
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=871qj0e7zs.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=63676@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=eliz@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).