unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Emanuel Berg <moasen@zoho.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Delete marked files from dired
Date: Fri, 02 Jun 2017 23:47:52 +0200	[thread overview]
Message-ID: <87k24u9i47.fsf@debian.uxu> (raw)
In-Reply-To: CAP_d_8WMSWf=N+TpiBRLomDJa19gtyrRJn4LygT-ectgNZKLoA@mail.gmail.com

Yuri Khan <yuri.v.khan@gmail.com> writes:

>> He is marking them with keys * s which is
>> `dired-mark-subdir-files'. x, or
>> `dired-do-flagged-delete' doesn't work then (it
>> does for d, `dired-flag-file-deletion', as you
>> mention) but perhaps the OP was unaware of that
>> method as well so why not.
>
> 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.

I don't remember because I never knew, but there can
be tons of application. For example, one target file
and one source; then hit a key to invoke source on
target (e.g., move a file into a dir or feed indata
from a text file as argument to an executable).

In this case, I suspect it is to separate deletion
from everything else, as a convenience/security
mechanism. Which makes sense!

> Most other file managers have just one kind of mark
> and it works the same way for copying, moving,
> and deleting.

One counterexample is Gnus, tho not a generic file
manager, in practice is/could be just that with
respect to mail/articles/posts, which are/can be
stored as individual files (depending on backend).

In Gnus, there are tons of markings, even parallel
systems: e.g., one that tells the message have been
opened (or "read"), R, and one that tells it has been
answered, a.

-- 
underground experts united
http://user.it.uu.se/~embe8573




  parent reply	other threads:[~2017-06-02 21:47 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
2017-06-02 16:34       ` Thien-Thi Nguyen
2017-06-02 21:47       ` Emanuel Berg [this message]
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=87k24u9i47.fsf@debian.uxu \
    --to=moasen@zoho.com \
    --cc=help-gnu-emacs@gnu.org \
    /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).