From: John Wiegley <jwiegley@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: async.el: A simple asynchronous framework for Emacs
Date: Mon, 25 Jun 2012 19:05:58 -0500 [thread overview]
Message-ID: <m2wr2vuec9.fsf@gmail.com> (raw)
In-Reply-To: <87395lyam9.fsf@gmail.com> (Thierry Volpiatto's message of "Sat, 23 Jun 2012 23:35:58 +0200")
>>>>> Thierry Volpiatto <thierry.volpiatto@gmail.com> writes:
> I must use the same form in many places for that:
> (let ((buf (loop for b in (buffer-list)
> thereis (and (string-match
> "\\`\\*ftp.*"
> (buffer-name b)) b))))
> (when buf (kill-buffer buf))))
> callback))
> maybe you have an idea to make a function that return the form one time
> for all and avoid these duplicates.
I'd probably just make a function that contains your `loop' usage.
>> This is no longer necessary in the latest version of dired-async. When an
>> async operations begin, the background of each related line is made yellow.
>> As the operations finish, the yellow is removed.
> This is true only for dired, I do not use dired, only helm, so I need a
> message to tell me when operation finish.
Ah, I understand now!
>> I would not be opposed, however, to a single async message which says,
>> (format "All asynchronous %s(s) have completed" operation).
> It is a single message that popup only once when all is finish. So for 500
> files, it popup only at the end:
> Asynchronous copy of 500 file(s) done
> What would be great is customizing the function to use for showing message,
> using `message' by default. One could use something else like
> `tooltip-show' or function using external program like notify-send or like.
Gotcha, this is a necessary configuration detail. I'll add it.
John
next prev parent reply other threads:[~2012-06-26 0:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 2:51 async.el: A simple asynchronous framework for Emacs John Wiegley
2012-06-19 5:11 ` Thien-Thi Nguyen
2012-06-19 5:36 ` John Wiegley
2012-06-19 13:29 ` Stefan Monnier
2012-06-19 20:44 ` John Wiegley
2012-06-19 21:46 ` Stefan Monnier
2012-06-20 0:20 ` John Wiegley
2012-06-20 0:53 ` John Wiegley
2012-06-20 5:34 ` John Wiegley
2012-06-20 7:24 ` SAKURAI Masashi
2012-06-20 7:52 ` John Wiegley
2012-06-20 8:13 ` John Wiegley
2012-06-20 8:24 ` John Wiegley
2012-06-20 9:32 ` SAKURAI Masashi
2012-06-20 20:36 ` Thien-Thi Nguyen
2012-06-20 23:52 ` John Wiegley
2012-06-21 13:17 ` Thien-Thi Nguyen
2012-06-22 16:01 ` Le Wang
2012-06-22 20:07 ` Thien-Thi Nguyen
2012-06-24 9:30 ` Chong Yidong
2012-06-19 21:38 ` Christopher Allan Webber
2012-06-21 8:31 ` Thierry Volpiatto
[not found] ` <m2lijg8ibx.fsf@vulcan.local.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <87a9zv1fw4.fsf@gmail.com>
[not found] ` <m2ehp73t8o.fsf@vulcan.local.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <871ul63yky.fsf@gmail.com>
[not found] ` <m2zk7tzr5e.fsf@vulcan.local.i-did-not-set--mail-host-address--so-tickle-me>
[not found] ` <87395lyam9.fsf@gmail.com>
2012-06-26 0:05 ` John Wiegley [this message]
2012-06-26 9:41 ` Thierry Volpiatto
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2wr2vuec9.fsf@gmail.com \
--to=jwiegley@gmail.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.