unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Yuri Khan <yuri.v.khan@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: Delete marked files from dired
Date: Fri, 2 Jun 2017 08:40:36 -0700 (PDT)	[thread overview]
Message-ID: <46e8d5f9-db01-4d73-896b-a30d3d84001a@default> (raw)
In-Reply-To: <CAP_d_8WMSWf=N+TpiBRLomDJa19gtyrRJn4LygT-ectgNZKLoA@mail.gmail.com>

> Does somebody remember the story of different marks?
> 
> I mean, Dired has D for flagging for deletion, * for marking for most
> other operations, and a command to change one mark to another. Ibuffer
> has D for killing and > for other operations.
> 
> Most other file managers have just one kind of mark and
> it works the same way for copying, moving, and deleting.
> 
> I wonder how and why that feature evolved?

It is a very useful feature.  You can easily have any
number of different marks, representing _different sets_
of files, and then act on any given set in various ways.

Dired keys that act on marked files typically act on the
files marked `*'.  (Those marked `D' are usually called
"flagged", not just "marked", and only one key, `D', acts
directly on them.)

Changing files marked with `*' to another mark keeps
them marked (keeps that set defined) but removes them
from being acted on (by commands that act on `*'-marked
files, which is the typical case).

Changing another mark back to `*' lets you then act
on its files.  If there are already some other files
marked `*' when you do that then you have effectively
joined those two sets (union).

You get the idea.  It's really pretty simple and quite
visible - you can see the various labeled sets.

It's a bit like using tags in Bookmark+, but only one
mark at a time applies to a given file.



  reply	other threads:[~2017-06-02 15:40 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-01 22:10 Delete marked files from dired notbob
2017-06-01 22:24 ` John Mastro
2017-06-01 22:32 ` Emanuel Berg
2017-06-01 23:09 ` Harry Putnam
2017-06-01 23:12   ` Harry Putnam
2017-06-02  0:29   ` Emanuel Berg
2017-06-02  4:55     ` Yuri Khan
2017-06-02 15:40       ` Drew Adams [this message]
2017-06-02 16:34       ` Thien-Thi Nguyen
2017-06-02 21:47       ` Emanuel Berg
2017-06-02 21:54         ` Emanuel Berg
2017-06-02  1:06 ` Emanuel Berg
2017-06-02  5:12 ` Marcin Borkowski
2017-06-02  5:31 ` Marco Wahl
2017-06-02 15:40   ` notbob
2017-06-02 21:52     ` Emanuel Berg
2017-06-03 21:15       ` Robert Thorpe
2017-06-03 22:16         ` Emanuel Berg
2017-06-04  4:58           ` Harry Putnam
2017-06-15  1:17     ` notbob
2017-06-15  1:34       ` notbob
2017-06-15  9:17         ` Ralf Fassel
2017-06-16 15:44           ` notbob
2017-06-16 15:53             ` notbob
2017-06-16 20:02               ` Marcin Borkowski
2017-06-19  9:21               ` Ralf Fassel
2017-06-19 13:06                 ` Emanuel Berg
2017-06-20  1:03                 ` notbob
2017-06-20  4:53                   ` Emanuel Berg
2017-06-20 10:33                   ` Ralf Fassel
2017-06-20 12:54                     ` Emanuel Berg
2017-06-15  4:56       ` Marcin Borkowski
2017-06-15  6:29       ` Emanuel Berg

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=46e8d5f9-db01-4d73-896b-a30d3d84001a@default \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=yuri.v.khan@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.
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).