From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.devel Subject: Re: async.el: A simple asynchronous framework for Emacs Date: Mon, 25 Jun 2012 19:05:58 -0500 Message-ID: References: <87bokdoylc.fsf@gmail.com> <87a9zv1fw4.fsf@gmail.com> <871ul63yky.fsf@gmail.com> <87395lyam9.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1340669229 21464 80.91.229.3 (26 Jun 2012 00:07:09 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 26 Jun 2012 00:07:09 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 26 02:07:08 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SjJJB-0002KU-BD for ged-emacs-devel@m.gmane.org; Tue, 26 Jun 2012 02:07:05 +0200 Original-Received: from localhost ([::1]:47282 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjJJB-0007XN-0a for ged-emacs-devel@m.gmane.org; Mon, 25 Jun 2012 20:07:05 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:42079) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjJJ8-0007X5-7O for emacs-devel@gnu.org; Mon, 25 Jun 2012 20:07:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SjJJ4-0004WR-G5 for emacs-devel@gnu.org; Mon, 25 Jun 2012 20:07:01 -0400 Original-Received: from mail-gh0-f169.google.com ([209.85.160.169]:35519) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjJJ3-0004W1-T5 for emacs-devel@gnu.org; Mon, 25 Jun 2012 20:06:58 -0400 Original-Received: by ghrr18 with SMTP id r18so4076741ghr.0 for ; Mon, 25 Jun 2012 17:06:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:references:mail-followup-to:date:in-reply-to :message-id:user-agent:mime-version:content-type; bh=5RrlajxHVV2hixJIe8vk3KPWNViOB1xcRWW5WMDEp1A=; b=xOG9dJiFghsQdAKeKh7qTeY3alqdTFrOFSiOnY0vW1AXshX8KU4igvouZslAAKrn8y TBXI01e9ZW6m/asUCK3lFZW/hq7ydxabgNQtqTVwHkV5UfK3/qKOMrNgbHJ4RFmKQy61 qEHrsTTE7e+kJJrVgql78W2zm8G4kUA1T4I5+QWLOxchSZBBA2iNsXR5D9AY5faeqK35 3U+dyGmIKd3xwheFvIK3FuVIFsUoNBWPNYHlsj+yi/64nFh/3TmqYHL0rF3juGzgpl/O T3knXDkRSSLUH9W4zfHTjupZZU+2aSolzKvYYpmbHrdj3S6uB3Ujk4nbHb3oVNjd9zsk qrKA== Original-Received: by 10.50.219.162 with SMTP id pp2mr9855161igc.40.1340669216015; Mon, 25 Jun 2012 17:06:56 -0700 (PDT) Original-Received: from vulcan.local (c-98-215-105-167.hsd1.il.comcast.net. [98.215.105.167]) by mx.google.com with ESMTPS id uy3sm450465igc.14.2012.06.25.17.06.54 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 25 Jun 2012 17:06:55 -0700 (PDT) Original-Received: by vulcan.local (Postfix, from userid 501) id 071C1F0C69F2; Mon, 25 Jun 2012 19:05:58 -0500 (CDT) Mail-Followup-To: emacs-devel@gnu.org In-Reply-To: <87395lyam9.fsf@gmail.com> (Thierry Volpiatto's message of "Sat, 23 Jun 2012 23:35:58 +0200") User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.1 (darwin) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.160.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:151166 Archived-At: >>>>> Thierry Volpiatto 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