GNU bug report logs - #21746
24.5; purpose of dired-keep-marker-copy?

Previous Next

Package: emacs;

Reported by: "Roland Winkler" <winkler <at> gnu.org>

Date: Fri, 23 Oct 2015 19:45:02 UTC

Severity: wishlist

Found in version 24.5

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #8 received at 21746 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Roland Winkler <winkler <at> gnu.org>, 21746 <at> debbugs.gnu.org
Subject: RE: bug#21746: 24.5; purpose of dired-keep-marker-copy?
Date: Fri, 23 Oct 2015 13:30:29 -0700 (PDT)
> I have never figured out a
> reason why copying a file in dired gives the copied file a marker
> `C'.

The reason (IMO) is that the marker indicates what the
operation was, so you can easily identify - *and then
operate on* the files that were copied (or whatever
the operation was).

What might be missing for you is this bit of info:
`* c' lets you change the char that is used for a given
mark.  So you can, for example, change all `C' marks at
a given moment to, say, `*' marks, and then use any
action on the marked files (which acts on `*'-marked
files).  Or change it to `D' and then delete the flagged
files.

Because mark `C' is used, there is no confusion with
files that might be marked with `*' or any other mark.

You can have any number of different marks at any time,
giving them any conceptual meaning you like.  Change
any of them to `*' to convert their files and dirs to
a set that you then act on in some way.

Dunno how much of this is documented in the manual,
but once you look at `C-h m' and then its mention
of `* c', you can pretty much imagine how it can be
put to good use.




This bug report was last modified 3 years and 82 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.