unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Mathias Dahl" <mathias.dahl@gmail.com>
Cc: lennart.borgman@gmail.com, emacs-devel@gnu.org
Subject: Re: More visible mini-buffer prompt face
Date: Sat, 24 Feb 2007 23:06:01 -0500	[thread overview]
Message-ID: <E1HLAe9-0008H2-TQ@fencepost.gnu.org> (raw)
In-Reply-To: <7dbe73ed0702240958s6a54086bv1c6d2664571ea6bc@mail.gmail.com> (mathias.dahl@gmail.com)

     What we can, and should do, in my opinion, is make sure that nothing
    "bad" happens if the user at first does not see the prompt, if he just
    keeps tpying away. There might be cases like that (I haven't though
    about it), and we might want to try and fix those to work better.

How could that be even conceivable?  The prompt means that you have
temporarily entered a special mode in which your input has a different
meaning.  If you type as if you didn't know you had entered the
minibuffer, it has to be misunderstood.

The only way this COULD not be the case is if we had different
characters for the minibuffer.  For instance, if the characters you
used to type a search string were different from the ones that you use
while doing ordinary editing.  But that would be very inconvenient,
given the hardware and software environment that exists.

     I happen to agree with the ideas of the late Jef Raskin, when it
    comes to prompting the user. Especially in the Yes/No scenario. If you
    display this kind of prompt too much, the user will form a habit of
    always answering Yes (I think that the most common case).

The question of when to ask for confirmation, and how, is an important
one, but it isn't the same one.  In Emacs, the reason we have
both y-or-n-p and yes-or-no-p is partly to address this.

  parent reply	other threads:[~2007-02-25  4:06 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
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 [this message]
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=E1HLAe9-0008H2-TQ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman@gmail.com \
    --cc=mathias.dahl@gmail.com \
    /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).