From: Joakim Verona <joakim@verona.se>
Subject: how to move files in background with dired?
Date: Fri, 04 Mar 2005 11:44:16 +0100 [thread overview]
Message-ID: <m34qfrwv0f.fsf@naru.home> (raw)
Is there some way to manage a background transfer queue for dired?
Maybe its easier to understand what I mean if I explain how I would
like it to work:
- I mark a number of large files to be moved to another disk, which
takes time.
- dired puts the moves on a queue, and makes a "progress buffer"
showing how far each move or copy has progressed. (this would look
something like wget.el:s progress buffer)
- each move or copy is done in the background with cp or mv shell
commands, so emacs is not locked
- Im now free to add more moves or copys to the queue by direding some
other directory
Ideally the same interface would be used for remote operations, with
tramp or something.
Sounds doable. Has it been done?
--
Joakim Verona
www.verona.se
next reply other threads:[~2005-03-04 10:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-04 10:44 Joakim Verona [this message]
[not found] <mailman.2577.1109935580.32256.help-gnu-emacs@gnu.org>
2005-03-04 12:44 ` how to move files in background with dired? fineman.web
2005-03-04 18:15 ` William Xuuu
2005-03-06 20:40 ` fineman.web
2005-03-06 20:42 ` fineman.web
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=m34qfrwv0f.fsf@naru.home \
--to=joakim@verona.se \
/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).