all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: Justin Fields <justinlime1999@gmail.com>
Cc: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: [PATCH] Add file-ring to dired-aux.el
Date: Tue, 22 Oct 2024 17:53:57 +0200	[thread overview]
Message-ID: <875xpk5e22.fsf@web.de> (raw)
In-Reply-To: <SN6PR03MB3871CA1929453B506FDB3993FC432@SN6PR03MB3871.namprd03.prod.outlook.com> (Justin Fields's message of "Mon, 21 Oct 2024 15:05:05 +0000")

Justin Fields <justinlime1999@gmail.com> writes:

> But, to summarize, the general idea is that you capture files into the
> list, in which you can perform actions with them LATER. This also
> forgoes the need
> of having multiple visible dired buffers present in the first place.
> [...]

Thanks.  This is a bit similar to how selections work in file managers.

But - wouldn't a dedicated dired buffer listing exactly those files not
be more intuitive?  Instead of adding a bunch of new commands operating
on the remembered files you could just use the "normal" dired commands.


Michael.



  parent reply	other threads:[~2024-10-22 15:53 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 15:05 [PATCH] Add file-ring to dired-aux.el Justin Fields
2024-10-21 17:47 ` [External] : " Drew Adams
2024-10-22 15:53 ` Michael Heerdegen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-21  8:11 Justin Fields
2024-10-21  9:48 ` Eli Zaretskii
2024-10-21 10:14   ` Justin Fields
2024-10-21 10:38     ` Eli Zaretskii
2024-10-28 10:31       ` Björn Bidar
     [not found]       ` <87v7xctt6p.fsf@>
2024-10-28 12:42         ` Eli Zaretskii
2024-10-21 12:35   ` Michael Heerdegen via Emacs development discussions.
2024-10-22 18:15 ` Juri Linkov
2024-10-22 18:43   ` Eli Zaretskii
2024-10-23  6:47     ` Justin Fields

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875xpk5e22.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=emacs-devel@gnu.org \
    --cc=justinlime1999@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.