From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: "Loading" Date: Wed, 14 Mar 2012 15:33:39 +0100 Message-ID: <8762e75k1o.fsf@thinkpad.tsdh.de> References: <87obrzo8qy.fsf@gmx.de> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1331735670 11211 80.91.229.3 (14 Mar 2012 14:34:30 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 14 Mar 2012 14:34:30 +0000 (UTC) Cc: Michael Albinus , emacs-devel@gnu.org To: Lars Magne Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 14 15:34:29 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 1S7pHY-0005Z2-Oe for ged-emacs-devel@m.gmane.org; Wed, 14 Mar 2012 15:34:28 +0100 Original-Received: from localhost ([::1]:36807 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7pHY-0004xl-3y for ged-emacs-devel@m.gmane.org; Wed, 14 Mar 2012 10:34:28 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:53834) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7pHM-0004wT-QW for emacs-devel@gnu.org; Wed, 14 Mar 2012 10:34:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S7pGy-0007Za-Tq for emacs-devel@gnu.org; Wed, 14 Mar 2012 10:34:16 -0400 Original-Received: from deliver.uni-koblenz.de ([141.26.64.15]:44849) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7pGy-0007Z9-Nm for emacs-devel@gnu.org; Wed, 14 Mar 2012 10:33:52 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by deliver.uni-koblenz.de (Postfix) with ESMTP id A9B0ED2515; Wed, 14 Mar 2012 15:33:50 +0100 (CET) X-Virus-Scanned: amavisd-new at uni-koblenz.de Original-Received: from deliver.uni-koblenz.de ([127.0.0.1]) by localhost (deliver.uni-koblenz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gAfr32p7LsMm; Wed, 14 Mar 2012 15:33:45 +0100 (CET) X-CHKRCPT: Envelopesender noch tassilo@member.fsf.org Original-Received: from thinkpad.tsdh.de (tsdh.uni-koblenz.de [141.26.67.142]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by deliver.uni-koblenz.de (Postfix) with ESMTPSA id D140AD251A; Wed, 14 Mar 2012 15:33:44 +0100 (CET) In-Reply-To: (Lars Magne Ingebrigtsen's message of "Wed, 14 Mar 2012 15:07:43 +0100") User-Agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.0.94 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 141.26.64.15 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:149045 Archived-At: Lars Magne Ingebrigtsen writes: >> I believe it would be a good thing, if running asynchronous >> operations are made visible consistently in Emacs. Maybe we could >> agree on the same function? > > In messages with images, there's usually more than one. Some may be > downloading, some may have failed and some may not be downloading at > all. I was thinking that it would make sense to "spin" the particular > images that are in the process of downloading to give the user an > obvious feedback on what's happening with each particular image. > > However, I'm not absolutely sure that's necessary. The three > categories could be distinguished otherwise. If the downloading > fails, perhaps a "broken image" image could be shown instead, and for > the images that aren't going to be downloaded, perhaps some other icon > could be shown. Maybe some spinner plus number of active/aborted/skipped processes, e.g., [\ (2/1/0)]? > Spinning in the buffer itself may be unnecessarily distracting. And it would be likely to break something. Remember when you introduced the seconds-counting Date header in gnus article mode and sometimes copying a region would copy from Date header to mark instead of from mark to point? Bye, Tassilo