From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>,
"'Luc Teirlinck'" <teirllm@dms.auburn.edu>
Cc: bug-gnu-emacs@gnu.org
Subject: RE: doc string of insert-default-directory is unclear
Date: Sat, 9 Feb 2008 11:17:20 -0800 [thread overview]
Message-ID: <001501c86b50$64c8dc20$a350908d@us.oracle.com> (raw)
In-Reply-To: <uir0yqe9s.fsf@gnu.org>
> > > > In previous releases, the doc string said only what its
> > > > first line says. The rest was presumably added in Emacs 22
> > > > to clarify the meaning and use.
> > >
> > > Not just clarify, to document its different semantics.
> >
> > That semantic difference is not clear to me from the new
> > doc string you propose. Sorry. Could you point out the difference?
>
> I did not mean my changes, I meant the addition of the text that you
> complained about: it was added when the effects of the value of this
> variable were changed a few years ago.
I understood that. I should have said that the semantic difference is not
clear to me from either the Emacs 22 doc string or your proposed text. What
is the semantic difference from pre-Emacs 22? What behavior has changed?
> > "Typing RETURN without editing will leave the minibuffer
> > empty." No, it will exit the minibuffer
>
> Well, that's ambiguity of the work "leave": it also means "exit",
> which was my intent.
Right. Exit is less ambiguous.
> > I hate to say it, but I think that, in general, the added
> > text just adds confusion.
>
> If you mean my changes, then I didn't add anything. I just rearranged
> the text a bit and made some minor wording changes.
I meant both the Emacs 22 text and your proposed text. I don't think either
clarifies things.
> > What is the problem that adding this text is intended to
> > solve? If you tell me what the problem we are solving is, perhaps
> > I can help some more with the wording.
>
> I didn't have enough time for researching all the users of this
> variable's value, unfortunately. So I simply don't know. Perhaps Luc
> Teirlinck (cc'ed), who is the author of the doc string, could help.
OK, understood; I appreciate your trying to help. If someone lets me know,
I'll try to suggest an improvement. For the moment, IMO, we were better off
with just the one-liner.
prev parent reply other threads:[~2008-02-09 19:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 1:31 doc string of insert-default-directory is unclear Drew Adams
2008-02-09 13:24 ` Eli Zaretskii
2008-02-09 15:59 ` Drew Adams
2008-02-09 16:35 ` Eli Zaretskii
2008-02-09 19:17 ` Drew Adams [this message]
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='001501c86b50$64c8dc20$a350908d@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=bug-gnu-emacs@gnu.org \
--cc=eliz@gnu.org \
--cc=teirllm@dms.auburn.edu \
/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).