unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: jadamson@partners.org (Joel J. Adamson)
To: help-gnu-emacs@gnu.org
Subject: Re: safe delete with dired?
Date: Thu, 29 Nov 2007 16:19:29 -0500	[thread overview]
Message-ID: <874pf4kavy.fsf@W0053328.mgh.harvard.edu> (raw)
In-Reply-To: 3a939056-25bb-4ce8-a55a-6438947ee438@i29g2000prf.googlegroups.com

"metaperl.com" <metaperl@gmail.com> writes:

> is there some way for dired to simply move the files marked via "d" to
> a directory instead of actually deleting them?

You can change the marks from "D" to "*" using "* c" and then operate on
them as regularly marked files.  The trick is to automate that (or you
could just start with marking them "m" instead of marking them with D).

Joel

-- 
Joel J. Adamson
Biostatistician
Pediatric Psychopharmacology Research Unit
Massachusetts General Hospital
Boston, MA  02114
(617) 643-1432
(303) 880-3109

      reply	other threads:[~2007-11-29 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-29 21:07 safe delete with dired? metaperl.com
2007-11-29 21:19 ` Joel J. Adamson [this message]

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=874pf4kavy.fsf@W0053328.mgh.harvard.edu \
    --to=jadamson@partners.org \
    --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).