unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Emilio Lopes <eclig@gmx.net>
Subject: announcing defaults when reading from minibuffer
Date: Sun, 28 Aug 2005 14:23:54 +0200	[thread overview]
Message-ID: <mhddatfl1.fsf@tiscali.de> (raw)

I've just asked myself if there's any convention for announcing
defaults when reading from minibuffer.  Skimming the Elisp manual
didn't reveal anything in this regard.  Seaching the archives of this
list I found this message from RMS:

   The standard for Emacs is (default foo).  There may be some
   nonstandard functions that use [foo], due to imperfect quality
   control, but we should stick to the standard (unless we decide to
   change it).

[http://lists.gnu.org/archive/html/emacs-devel/2004-06/msg00085.html]

So I documented this convention in "(elisp) Text from Minibuffer".

Here's the patch:


2005-08-28  Emilio C. Lopes  <eclig@gmx.net>

	* minibuf.texi (Text from Minibuffer): mention convention for
	announcing default values when reading from the minibuffer.

diff -rN -c old-emacs-darcs.eclig/lispref/minibuf.texi new-emacs-darcs.eclig/lispref/minibuf.texi
*** old-emacs-darcs.eclig/lispref/minibuf.texi	Sun Aug 28 14:20:31 2005
--- new-emacs-darcs.eclig/lispref/minibuf.texi	Sun Aug 28 14:05:41 2005
***************
*** 154,159 ****
--- 154,167 ----
  empty string, @code{""}.  In this respect, it is different from all
  the other minibuffer input functions in this chapter.
  
+ Note that the standard way in Emacs to announce a default value when
+ reading from the minibuffer is to put it between parenthesis following
+ the word ``default'' as in
+ 
+ @smallexample
+ Enter value (default 42): 
+ @end smallexample
+ 
  If @var{keymap} is non-@code{nil}, that keymap is the local keymap to
  use in the minibuffer.  If @var{keymap} is omitted or @code{nil}, the
  value of @code{minibuffer-local-map} is used as the keymap.  Specifying

             reply	other threads:[~2005-08-28 12:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28 12:23 Emilio Lopes [this message]
2005-08-29  8:39 ` announcing defaults when reading from minibuffer Richard M. Stallman
2005-08-29 17:23   ` Emilio Lopes
2005-08-29 18:47 ` Bill Wohler
2005-08-30 10:30   ` Richard M. 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=mhddatfl1.fsf@tiscali.de \
    --to=eclig@gmx.net \
    /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).