From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: Global bar to display global information
Date: Tue, 16 Aug 2011 19:04:24 +0200 [thread overview]
Message-ID: <87d3g5e19j.fsf@wanadoo.es> (raw)
In-Reply-To: DFB8C1FDB9654CDAB5DA6F02F0A6A2DA@us.oracle.com
"Drew Adams" <drew.adams@oracle.com> writes:
>> Most of the time the minibuffer is an idle blank line at the bottom of
>> the frame. Using it for displaying some global info sounds quite
>> convenient. It could display the global info even while asking for
>> input, overwritting the area used by the info as necessary.
>
> Ouch! That's not what I meant at all.
I know. It was an alternative idea.
> I would not want to see such info displayed in the minibuffer/echo
> area itself (too complex, confusing, distracting, messy, noisy).
>
> And we already have ways of posting text to the echo area (same space
> as minibuffer) when the minibuffer is inactive: `message'. That
> messages get replaced by later messages and by minibuffer input is
> just a further demonstration that using the minibuffer/echo area for
> this global info would be a bad idea.
`message' is used for ephemeral info, very ephemeral (just a keypress
makes it go away). I was thinking about something stable that is hidden
(totally or partially) while the minibuffer/echo area is used for its
current purpose. But your comment about `message' makes me think that
*maybe* it would be confusing/distracting/etc when something is posted
to the echo area with `message' to be quickly replaced by the global
info. It may create a blinking effect.
I don't like standalone frames for things like the minibuffer or our
hypothetical global info display. I work on just one frame and reusing
the minibuffer area looks like a good idea, if it could be implemented
on a sane way. If that is not possible or convenient, a dedicated line
on each frame looks like the next choice.
(If the global info line is displayed on just one frame, what happens
when the user creates a new frame on a remote display?)
[snip]
next prev parent reply other threads:[~2011-08-16 17:04 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-16 14:33 Global bar to display global information Jérémy Compostella
2011-08-16 15:29 ` Drew Adams
2011-08-16 16:18 ` Óscar Fuentes
2011-08-16 16:40 ` Drew Adams
2011-08-16 17:04 ` Óscar Fuentes [this message]
2011-08-16 17:42 ` Drew Adams
2011-08-16 19:23 ` Jérémy Compostella
2011-08-16 19:46 ` chad
2011-08-16 19:48 ` chad
2011-09-25 12:42 ` Ted Zlatanov
2011-08-16 20:54 ` Jérémy Compostella
2011-08-16 22:32 ` chad
2011-08-16 22:49 ` Jérémy Compostella
2011-08-17 7:49 ` Nicolas Martyanoff
2011-08-17 9:07 ` martin rudalics
2011-08-17 9:27 ` Juri Linkov
2011-08-17 9:44 ` martin rudalics
2011-08-17 11:41 ` Jérémy Compostella
2011-08-17 14:05 ` Stefan Monnier
2011-08-17 15:38 ` Jérémy Compostella
2011-08-17 11:38 ` Nicolas Martyanoff
2011-08-20 13:20 ` Jérémy Compostella
2011-08-20 14:32 ` Óscar Fuentes
2011-08-20 16:02 ` martin rudalics
2011-08-20 16:42 ` Óscar Fuentes
2011-08-21 8:45 ` martin rudalics
2011-08-20 16:01 ` martin rudalics
2011-09-25 12:53 ` Ted Zlatanov
2011-08-16 20:00 ` Thien-Thi Nguyen
2011-08-16 17:31 ` Stefan Monnier
2011-08-17 20:12 ` Jérémy Compostella
2011-08-18 0:24 ` chad
2011-08-21 15:50 ` Jérémy Compostella
[not found] ` <jwvobziezor.fsf-monnier+emacs@gnu.org>
2011-12-30 13:21 ` Jérémy Compostella
2011-12-31 13:13 ` Jérémy Compostella
2012-01-01 22:11 ` Stefan Monnier
2012-04-24 13:06 ` Stefan Monnier
2012-04-26 18:12 ` Jérémy Compostella
2012-05-07 16:10 ` Stefan Monnier
2011-09-25 12:50 ` Ted Zlatanov
2011-08-16 17:42 ` joakim
2011-08-16 17:44 ` chad
2011-08-20 18:29 ` Andreas Röhler
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=87d3g5e19j.fsf@wanadoo.es \
--to=ofv@wanadoo.es \
--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.