unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Dave Abrahams <dave@boostpro.com>
Cc: emacs-devel@gnu.org
Subject: Re: "Loading"
Date: Thu, 15 Mar 2012 11:26:12 +0100	[thread overview]
Message-ID: <87zkbicg8r.fsf@gmx.de> (raw)
In-Reply-To: <m2ipi6xl6k.fsf@pluto.luannocracy.com> (Dave Abrahams's message of "Thu, 15 Mar 2012 05:33:55 -0400")

Dave Abrahams <dave@boostpro.com> writes:

>>> Is there any reason a few characters couldn't be used for this in the
>>> left part of the minibuffer/echo area, without making that area
>>> completely unusable?
>>
>> Harder to implement. You would need to add a minor mode for the
>> minibuffer, which shows this fixed string. And for the echo area, you
>> would also need to touch `message' and friends.
>
> What about just splitting the minibuffer window horizontally?

Anything goes, of course. But I fear we would break the minibuffer
(which is a special buffer, with special handling). And there is still
the echo area problem.

The modeline is designed to provide indications to the user. I believe,
it is the natural place for showing unfinished network activities.

If it cannot be a spinning char due to the permanent refresh, than it
might be some coloured text, as running processes show already.

Best regards, Michael.



  reply	other threads:[~2012-03-15 10:26 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   ` "Loading" Lars Magne Ingebrigtsen
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                 ` Michael Albinus [this message]
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=87zkbicg8r.fsf@gmx.de \
    --to=michael.albinus@gmx.de \
    --cc=dave@boostpro.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 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).