From: Pavel@Janik.cz (Pavel Janík)
Cc: Stefan Monnier <monnier+gnu/emacs@RUM.cs.yale.edu>, emacs-devel@gnu.org
Subject: Re: minibuffer vs dialog-boxes
Date: Sat, 20 Apr 2002 10:34:36 +0200 [thread overview]
Message-ID: <m3vgamojj7.fsf@Janik.cz> (raw)
In-Reply-To: <Pine.SUN.3.91.1020418192257.8613H-100000@is> (Eli Zaretskii's message of "Thu, 18 Apr 2002 19:23:49 +0300 (IDT)")
From: Eli Zaretskii <eliz@is.elta.co.il>
Date: Thu, 18 Apr 2002 19:23:49 +0300 (IDT)
> > In order to bring the user's attention to the minibuffer when an item
> > such as "Edit -> Search" is activated from the menu, I was just thinking
> > that we could draw a big rectangle around the minibuffer, blinking
> > (or zooming in-and-out) until some input is typed in.
>
> Shouldn't some ingenious use of minibuffer-prompt-face be enough?
Some days ago I proposed changing the background color of the whole
minibuffer. Minibuffer-prompt-face is not enough I think. Prompt can be
short (like I-search:) and thus it is not enough to get user' attention.
Changing the background color of minibuffer will be similar to the effect
of mode-line-inactive face. Minibuffer will "stand up" from Emacs. Another
useful thing can be to change display engine to allow minibuffer at the top
of the Emacs frame...
--
Pavel Janík
panic("floppy: Port bolixed.");
-- 2.2.16 include/asm-sparc/floppy.h
next prev parent reply other threads:[~2002-04-20 8:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 11:54 minibuffer vs dialog-boxes Stefan Monnier
2002-04-18 12:51 ` Miles Bader
2002-04-18 14:24 ` Kai Großjohann
2002-04-18 14:28 ` Miles Bader
2002-04-18 16:23 ` Eli Zaretskii
2002-04-20 8:34 ` Pavel Janík [this message]
2002-04-20 11:48 ` Eli Zaretskii
2002-04-20 12:07 ` Miles Bader
2002-04-21 20:02 ` Richard Stallman
2002-04-24 14:51 ` Pavel Janík
2002-04-19 5:25 ` Richard Stallman
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=m3vgamojj7.fsf@Janik.cz \
--to=pavel@janik.cz \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@RUM.cs.yale.edu \
/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).