From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: Re: doc string of insert-default-directory is unclear Date: Sat, 09 Feb 2008 15:24:32 +0200 Message-ID: References: <001301c86604$8c9e5c30$2c49908d@us.oracle.com> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1202563574 5155 80.91.229.12 (9 Feb 2008 13:26:14 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 9 Feb 2008 13:26:14 +0000 (UTC) Cc: bug-gnu-emacs@gnu.org To: "Drew Adams" Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sat Feb 09 14:26:36 2008 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JNpj2-0005pw-0A for geb-bug-gnu-emacs@m.gmane.org; Sat, 09 Feb 2008 14:26:36 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JNpiZ-00053m-0A for geb-bug-gnu-emacs@m.gmane.org; Sat, 09 Feb 2008 08:26:07 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JNpiR-00051K-Kb for bug-gnu-emacs@gnu.org; Sat, 09 Feb 2008 08:25:59 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JNpiQ-0004zB-2u for bug-gnu-emacs@gnu.org; Sat, 09 Feb 2008 08:25:59 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JNpiP-0004z1-Pu for bug-gnu-emacs@gnu.org; Sat, 09 Feb 2008 08:25:57 -0500 Original-Received: from nitzan.inter.net.il ([213.8.233.22]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JNpiP-0006Ad-CO for bug-gnu-emacs@gnu.org; Sat, 09 Feb 2008 08:25:57 -0500 Original-Received: from HOME-C4E4A596F7 (IGLD-83-130-218-44.inter.net.il [83.130.218.44]) by nitzan.inter.net.il (MOS 3.7.3a-GA) with ESMTP id JCO67466 (AUTH halo1); Sat, 9 Feb 2008 15:22:02 +0200 (IST) In-reply-to: <001301c86604$8c9e5c30$2c49908d@us.oracle.com> (drew.adams@oracle.com) X-detected-kernel: by monty-python.gnu.org: FreeBSD 4.7-5.2 (or MacOS X 10.2-10.4) (2) X-BeenThere: bug-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:17510 Archived-At: > From: "Drew Adams" > Date: Sat, 2 Feb 2008 17:31:49 -0800 > > Don't ask me why it's unclear to me, if it's clear to you. In that > case, just take it that at least one user finds this unclear. > > 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. > Please consider rephrasing the entire doc string. A good starting > point could be to explain the significance of the initial contents > being non-empty. I took a shot at this. The new doc string is this: *Non-nil means when reading a filename start with default dir in minibuffer. When the initial minibuffer contents show a name of a file or a directory, typing RETURN without editing the initial contents is equivalent to typing the default file name. If this variable is non-nil, the minibuffer contents are always initially non-empty, and typing RETURN without editing will fetch the default name, if one is provided. Note however that this default name is not necessarily the same as initial contents inserted in the minibuffer, if the initial contents is just the default directory. If this variable is nil, the minibuffer often starts out empty. In that case you may have to explicitly fetch the next history element to request the default name; typing RETURN without editing will leave the minibuffer empty. For some commands, exiting with an empty minibuffer has a special meaning, such as making the current buffer visit no file in the case of `set-visited-file-name'.