unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: More visible mini-buffer prompt face
Date: Fri, 23 Feb 2007 11:58:56 -0800	[thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMAECKCPAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1HKgDd-0005fi-7M@fencepost.gnu.org>

>     I wonder if it would not be better to have a more visible
>     face for the minibuffer prompt by default. My suggestion
>     would be using a visible background color (some not too
>     sharp yellow perhaps).
>
> What color do you get now?
> Which of the options in the defface is being used?
> Could you propose a patch in that defface?

I see no reason for the prompt to stand out more, and changing the
background color is a bad idea, IMO. Background colors are often used to
highlight particular sections of text, not just to present normal text. Why
should a normal _prompt_ stand out especially?

If your code pops up menus that attract the user away from the minibuffer,
and then you expect the user to notice a minibuffer prompt that you issue,
then why not make the minibuffer prompt stand out more _in your code_? This
sounds like a UI (dialog) problem in your code, not a problem with the
default Emacs minibuffer prompt face.

In general, minibuffer prompts appear when the user expects them; in fact,
they are usually initiated by the user. The case you describe, with the user
attention far from the minibuffer when a prompt appears out of the blue
there, is a special case, and it should be treated as such (in your code,
which defines that dialog). A normal prompt should not especially stand out;
the default prompt face that I see (dark blue) is fine.

Your point about error messages is different (independent). In that case,
the user might not expect to see stuff appear in the echo area, so you might
want to attract attention to it. Nothing prevents particular code from
applying text properties to messages in the echo area. That too is best left
up to the particular application, IMO. The default message face should not
stand out.

  reply	other threads:[~2007-02-23 19:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 16:24 More visible mini-buffer prompt face Lennart Borgman (gmail)
2007-02-23 16:41 ` Juanma Barranquero
2007-02-23 17:46   ` Lennart Borgman (gmail)
2007-02-23 18:09     ` Stefan Monnier
2007-02-23 19:36 ` Richard Stallman
2007-02-23 19:58   ` Drew Adams [this message]
2007-02-23 21:47     ` Lennart Borgman (gmail)
2007-02-24  0:18       ` Drew Adams
2007-02-24  1:01         ` Lennart Borgman (gmail)
2007-02-24  1:08           ` Drew Adams
2007-02-24  1:27             ` Lennart Borgman (gmail)
2007-02-24  8:28     ` Richard Stallman
2007-02-24 22:16       ` Kim F. Storm
2007-02-24  1:35   ` Lennart Borgman (gmail)
2007-02-24  4:30     ` Daniel Brockman
2007-02-24 18:51       ` Lennart Borgman (gmail)
2007-02-24 14:20     ` Miles Bader
2007-02-24 14:36       ` Eli Zaretskii
2007-02-25  4:06     ` Richard Stallman
2007-02-26  3:27     ` Richard Stallman
2007-02-26 10:55       ` Mathias Dahl
2007-02-26 16:48         ` Lennart Borgman (gmail)
2007-02-27  7:38         ` Richard Stallman
2007-02-24 17:58 ` Mathias Dahl
2007-02-25  1:09   ` Lennart Borgman (gmail)
2007-02-25 20:44     ` Lennart Borgman (gmail)
2007-02-25  4:06   ` Richard Stallman
2007-02-25 11:01     ` Mathias Dahl
2007-02-26  3:27       ` Richard Stallman
2007-02-26 10:45         ` Mathias Dahl
2007-02-26 11:20           ` Juanma Barranquero
2007-02-26 23:53             ` Mathias Dahl
2007-02-27 19:07         ` Stuart D. Herring

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=EIENLHALHGIMHGDOLMIMAECKCPAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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).