unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: "Loading"
Date: Wed, 14 Mar 2012 15:07:43 +0100	[thread overview]
Message-ID: <m3ehsvqnrk.fsf@stories.gnus.org> (raw)
In-Reply-To: <87obrzo8qy.fsf@gmx.de> (Michael Albinus's message of "Wed, 14 Mar 2012 10:02:45 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

> The progress-reporter, spinning in the echo area, is not an option,
> because the minibuffer shall be usable. Therefore I'm thinking about to
> reactivate the old proposal of a progress-reporter extension, spinning \
> | / in the modeline (more precisely: in `mode-line-remote').

I think spinning something in the mode line to indicate that we're
waiting for network traffic is a very good idea.

> 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.
Spinning in the buffer itself may be unnecessarily distracting.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/



  parent reply	other threads:[~2012-03-14 14:07 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-13 21:38 "Loading" Lars Magne Ingebrigtsen
2012-03-14  2:02 ` "Loading" Stefan Monnier
2012-03-14  2:18   ` "Loading" Lars Magne Ingebrigtsen
2012-03-14  9:02 ` "Loading" Michael Albinus
2012-03-14 13:27   ` "Loading" Stefan Monnier
2012-03-14 13:38     ` "Loading" Michael Albinus
2012-03-14 14:28       ` "Loading" Stefan Monnier
2012-03-14 14:50         ` "Loading" Michael Albinus
2012-03-14 14:07   ` Lars Magne Ingebrigtsen [this message]
2012-03-14 14:33     ` "Loading" Tassilo Horn
2012-03-14 14:43       ` "Loading" Lars Magne Ingebrigtsen
2012-03-14 14:55         ` "Loading" Michael Albinus
2012-03-15  1:40           ` "Loading" Dave Abrahams
2012-03-15  8:28             ` "Loading" Michael Albinus
2012-03-15  9:33               ` "Loading" Dave Abrahams
2012-03-15 10:26                 ` "Loading" Michael Albinus
2012-03-15 11:22                   ` "Loading" Dave Abrahams
2012-03-15 11:55                     ` "Loading" Tassilo Horn
2012-03-15 12:05                       ` "Loading" Michael Albinus
2012-03-15 15:29                       ` "Loading" Dave Abrahams
2012-03-15 15:51                         ` "Loading" Lars Magne Ingebrigtsen
2012-03-15 16:12                           ` "Loading" Lars Magne Ingebrigtsen
2012-03-19 13:32                             ` "Loading" Ted Zlatanov
2012-03-15 11:59                     ` "Loading" Michael Albinus
2012-03-14 17:07   ` "Loading" Eli Zaretskii
2012-03-14 18:29     ` "Loading" Michael Albinus

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=m3ehsvqnrk.fsf@stories.gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).