all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Drew Adams <drew.adams@oracle.com>
Cc: bug-gnu-emacs@gnu.org, 4654@emacsbugs.donarmstrong.com
Subject: bug#4654: 23.1; Elisp manual doc of abbreviate-file-name
Date: Tue, 06 Oct 2009 16:21:15 -0400	[thread overview]
Message-ID: <jwvpr90e0mj.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <A7B578F309F04902ACE8A24F56BECB9D@us.oracle.com> (Drew Adams's message of "Tue, 6 Oct 2009 10:54:09 -0700")

> 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.
 
"a root directory" means "/".  The reason is that substituting "/" for
"~" doesn't really abbreviate anything.  If anythingn to me it "looks"
longer because I expect ~ to expand to something longer.


        Stefan








  reply	other threads:[~2009-10-06 20:21 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 [this message]
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   ` bug#4654: marked as done (23.1; Elisp manual doc of abbreviate-file-name) Emacs bug Tracking System
     [not found] ` <1E8768BDE1464D019FC9EED701E222F4@us.oracle.com>
2009-10-07 17:44   ` bug#4654: 23.1; Elisp manual doc of abbreviate-file-name 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvpr90e0mj.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=4654@emacsbugs.donarmstrong.com \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=drew.adams@oracle.com \
    /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.