From: owner@emacsbugs.donarmstrong.com (Emacs bug Tracking System)
To: Eli Zaretskii <eliz@gnu.org>
Subject: bug#4654: marked as done (23.1; Elisp manual doc of abbreviate-file-name)
Date: Wed, 07 Oct 2009 10:30:15 +0000 [thread overview]
Message-ID: <handler.4654.D4654.125491104521697.ackdone@emacsbugs.donarmstrong.com> (raw)
In-Reply-To: A7B578F309F04902ACE8A24F56BECB9D@us.oracle.com
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
Your message dated Wed, 07 Oct 2009 12:21:55 +0200
with message-id <83ab03mrlo.fsf@gnu.org>
and subject line Re: bug#4654: 23.1; Elisp manual doc of abbreviate-file-name
has caused the Emacs bug report #4654,
regarding 23.1; Elisp manual doc of abbreviate-file-name
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)
--
4654: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=4654
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
[-- Attachment #2: Type: message/rfc822, Size: 3439 bytes --]
From: "Drew Adams" <drew.adams@oracle.com>
To: <bug-gnu-emacs@gnu.org>
Subject: 23.1; Elisp manual doc of abbreviate-file-name
Date: Tue, 6 Oct 2009 10:54:09 -0700
Message-ID: <A7B578F309F04902ACE8A24F56BECB9D@us.oracle.com>
The doc string mentions this qualification, but the Elisp manual does
not: " (unless the home directory is a root directory)".
Please mention this in the manual also.
Question: Why? What is the rationale for not substituting `~' when it
is a root directory? If the reason is short to express, perhaps it
should be included in the doc. Understanding the rationale helps one
remember what the function does.
In GNU Emacs 23.1.1 (i386-mingw-nt5.1.2600)
of 2009-07-29 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (4.4)'
[-- Attachment #3: Type: message/rfc822, Size: 3687 bytes --]
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>, 4654-done@emacsbugs.donarmstrong.com
Cc: monnier@iro.umontreal.ca
Subject: Re: bug#4654: 23.1; Elisp manual doc of abbreviate-file-name
Date: Wed, 07 Oct 2009 12:21:55 +0200
Message-ID: <83ab03mrlo.fsf@gnu.org>
> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Wed, 7 Oct 2009 00:50:41 -0700
> Cc: 4654@emacsbugs.donarmstrong.com
>
> a. Always substituting `~' for the home dir is consistent; and it tells you
> where the file is wrt the home dir.
>
> b. Substituting `~' for the home dir except when it is the root dir breaks
> consistency; but it does tell you where the file is wrt root (in that one
> exceptional case only - otherwise, it tells you where the file is wrt the home
> dir). It also has the advantage of legacy: consistency with the past and
> existing code.
>
> c. If we were to substitute `~' for the home dir except when that is the root
> dir, on UNIX etc., but not substitute it for the home dir when that is the root
> dir, on Windows, that would ensure that `~' substitution would always shorten
> the file name. But that would introduce additional inconsistency.
>
> And in any case, substituting using `directory-abbrev-alist' does not guarantee
> shortening at all. Nothing prevents such "abbreviation" from lengthening the
> name.
>
> Overall, (a) is a better choice than (b) or (c) - unless the legacy
> consideration has particular importance here for some reason (I don't think it
> does).
I hope no one is seriously suggesting to change the behavior of one of
the oldest Emacs APIs...
I fixed the manual. The description now says
This function applies abbreviations from @code{directory-abbrev-alist}
to its argument, and also substitutes @samp{~} for the user's home
directory if the argument names a file in the home directory or one of
its subdirectories. (If the home directory is a root directory, it is
not replaced with @samp{~}, because this does not make the result
shorter on many systems.) You can use it for directory names and for
file names, because it recognizes abbreviations even as part of the
name.
I hope this is something everybody can live with.
next prev parent reply other threads:[~2009-10-07 10:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <83ab03mrlo.fsf@gnu.org>
2009-10-06 17:54 ` bug#4654: 23.1; Elisp manual doc of abbreviate-file-name Drew Adams
2009-10-06 20:21 ` Stefan Monnier
2009-10-06 21:12 ` Drew Adams
2009-10-07 5:47 ` Stefan Monnier
2009-10-07 7:50 ` Drew Adams
2009-10-07 14:09 ` Stefan Monnier
2009-10-07 15:21 ` Drew Adams
2009-10-07 10:30 ` Emacs bug Tracking System [this message]
[not found] ` <1E8768BDE1464D019FC9EED701E222F4@us.oracle.com>
2009-10-07 17:44 ` Eli Zaretskii
2009-10-07 17:55 ` Drew Adams
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=handler.4654.D4654.125491104521697.ackdone@emacsbugs.donarmstrong.com \
--to=owner@emacsbugs.donarmstrong.com \
--cc=eliz@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 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).