From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>,
Thierry Volpiatto <thievol@posteo.net>
Cc: "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:04:55 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488F158F1C89057D9B6BAC9F3459@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87mt1p59s7.fsf@web.de>
> > You could avoid such problem by creating a dired buffer with _only_ the
> > files you want to modify (helm allows this), then switch to wdired-mode
> > and do your modifications.
> > Probably implementing this in dired (i.e. open a new dired buffer with
> > only marked files) would be a good addition.
>
> Thanks for mentioning this. Yes, we definitely want something like
> this. I was experimenting with such "helper" dired buffers myself
> (inspired by Icicles and Helm among others).
>
> It's surprisingly hard to integrate such buffers into the dired concept,
> though: you can't advertise them (else they would be displayed when you
> "open the respective directory"). If you don't advertise them, file
> changes in other buffers (like renamings) are not propagated into these
> additional buffers. Of course it must also work into the other
> direction. Implementing this feature in a proper manner is not as easy
> as it seems I think (you don't accidently want to take the
> opportunity?).
>
> OTOH, performing such more complex renaming operations should be
> supported as conveniently as possible in "standard" dired buffers.
(Caveat: I haven't followed this thread.)
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. 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
next prev parent reply other threads:[~2023-05-28 16:04 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 [this message]
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=SJ0PR10MB5488F158F1C89057D9B6BAC9F3459@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=63676@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=peter.mao@gmail.com \
--cc=thievol@posteo.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).