From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Juri Linkov' <juri@jurta.org>,
deniz.a.m.dogan@gmail.com, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: delete-file default to buffer-file-name if non-nil
Date: Mon, 17 May 2010 09:51:27 -0400 [thread overview]
Message-ID: <jwvy6fiwsdk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <09068505550E4734B4B3E6F5DCEB8A98@us.oracle.com> (Drew Adams's message of "Sun, 16 May 2010 17:28:31 -0700")
>> The argument INITIAL-CONTENTS is obsolete and should not be used.
>> It's possible to insert the default value to the minibuffer
>> with `M-n'.
> So it is. But I happen to disagree that it should be obsolete. ;-)
You're wrong, of course.
> A better approach is to let the user decide the behavior.
> I have this option (FWIW):
> | When the default value argument to functions such as
> | `completing-read', `read-file-name', `read-from-minibuffer', and
> | `read-string' is non-nil and the initial-input argument is nil or
> | "", the default value can be added to the prompt as a hint or
> | inserted into the minibuffer as the initial input.
IIUC this is not using the initial-contents argument (more to the
point, it's only active if this arg is nil, i.e. if the caller properly
treats it a deprecated).
So this is perfectly compatible with initial-contents's obsolescence.
Stefan
next prev parent reply other threads:[~2010-05-17 13:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 18:05 delete-file default to buffer-file-name if non-nil Deniz Dogan
2010-05-15 18:30 ` Davis Herring
2010-05-15 22:10 ` Deniz Dogan
2010-05-16 20:04 ` Richard Stallman
2010-05-16 20:20 ` Drew Adams
2010-05-16 23:09 ` Juri Linkov
2010-05-17 0:28 ` Drew Adams
2010-05-17 13:51 ` Stefan Monnier [this message]
2010-05-17 14:56 ` Drew Adams
2010-05-17 16:15 ` Deniz Dogan
2010-05-17 23:09 ` Juri Linkov
2010-05-18 22:38 ` Juri Linkov
2010-05-17 14:40 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvy6fiwsdk.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=deniz.a.m.dogan@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.org \
--cc=rms@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.