From: ken <gebser@mousecar.com>
To: Drew Adams <drew.adams@oracle.com>,
GNU Emacs List <help-gnu-emacs@gnu.org>
Subject: Re: need obsolete arg in (read-from-minibuffer ...)
Date: Fri, 18 Mar 2011 22:22:04 -0400 [thread overview]
Message-ID: <4D84134C.9010402@mousecar.com> (raw)
In-Reply-To: <D79FEA8BC7E14736808AD0927A040FF4@us.oracle.com>
On 03/18/2011 07:03 PM Drew Adams wrote:
>>> What do you mean by "work"? And what do you mean "without"
>>> the obsolete arg?
>> If I change the 2nd arg from "def-val" to "nil", then def-val
>> isn't displayed in the minibuffer for editing by the user.
>> However, the docs say that this arg is obsolete.
>> I take this to mean that it should be left as "nil".
>
> Correct. By "obsolete" the docs mean that that the Emacs developers think you
> should leave it as nil (i.e., not use the INITIAL-CONTENTS argument), and use
> only the DEFAULT-VALUE argument.
>
> They think that the only useful use cases make no use of INITIAL-CONTENTS. But
> see the doc string wrt the HIST arg, where they allow for an exception.
>
> However, if you understand the difference between DEFAULT-VALUE and
> INITIAL-CONTENTS, and _you prefer_ the behavior of INITIAL-CONTENTS for some
> reason in some particular context, then use it. Personally, I do not consider
> INITIAL-CONTENTS obsolete, FWIW.
>
> Remember that you can pull the DEFAULT-VALUE into the minibuffer using `M-n'.
> So the difference typically comes down to which you find more convenient: having
> a value in the minibuffer initially (and having to get rid of it if you really
> want something else instead) or pulling a value into the minibuffer when you
> need it, using `M-n'.
>
> If the default/initial value is used most of the time, then you might find it
> more convenient to have the minibuffer prefilled with it. If it is not used
> most of the time then you might find it more convenient not to have to clear it
> out of the minibuffer and type another value. And this relative convenience
> might change, depending on the command and the context.
>
> ....
Really? This is why that 2nd arg was declared obsolete!? That's rather
goofy. I thought there was some technical reason for it-- something to
do with code. Oh well.... Thanks for the answer.
next prev parent reply other threads:[~2011-03-19 2:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-18 20:23 need obsolete arg in (read-from-minibuffer ...) ken
2011-03-18 20:37 ` Drew Adams
2011-03-18 22:12 ` ken
2011-03-18 23:03 ` Drew Adams
2011-03-19 2:22 ` ken [this message]
2011-03-19 2:34 ` Drew Adams
[not found] ` <mailman.0.1300501334.15172.help-gnu-emacs@gnu.org>
2011-03-22 1:02 ` Stefan Monnier
[not found] ` <mailman.23.1300486344.31996.help-gnu-emacs@gnu.org>
2011-03-19 1:59 ` Stefan Monnier
2011-03-19 5:23 ` ken
2011-03-19 5:51 ` need obsolete arg in (read-from-minibuffer ...) in Version 2.0 ken
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=4D84134C.9010402@mousecar.com \
--to=gebser@mousecar.com \
--cc=drew.adams@oracle.com \
--cc=help-gnu-emacs@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.