From: Richard Stallman <rms@gnu.org>
Cc: dooglus@gmail.com, emacs-devel@gnu.org,
stephen_leake@member.fsf.org, eliz@gnu.org,
drew.adams@oracle.com, miles@gnu.org
Subject: Re: abbreviate-file-name on Windows seems incorrect
Date: Tue, 09 Jan 2007 12:57:13 -0500 [thread overview]
Message-ID: <E1H4LDl-0005xJ-9X@fencepost.gnu.org> (raw)
In-Reply-To: <45A2E241.1050101@gnu.org> (message from Jason Rumney on Tue, 09 Jan 2007 00:30:57 +0000)
> Can you check whether the efficiency gain is really significant in
> practice?
Compared with the current version of abbreviate-file-name, getenv seems
to take a little more than twice as long to complete on my system. So it
might be reasonable to expect the time for abbreviate-file-name to
triple if it is changed to calculate the value of HOME every time it is
needed based on getenv alone.
Ok, that is enough reason to keep it the way it is.
next prev parent reply other threads:[~2007-01-09 17:57 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 7:56 abbreviate-file-name on Windows seems incorrect Drew Adams
2007-01-06 11:37 ` Lennart Borgman (gmail)
2007-01-06 14:18 ` Eli Zaretskii
2007-01-06 15:03 ` Lennart Borgman (gmail)
2007-01-06 11:56 ` Eli Zaretskii
2007-01-06 16:22 ` Drew Adams
2007-01-06 21:51 ` Eli Zaretskii
2007-01-06 22:42 ` Drew Adams
2007-01-07 2:44 ` Miles Bader
2007-01-07 4:12 ` Eli Zaretskii
2007-01-07 14:29 ` Stephen Leake
2007-01-07 20:47 ` Eli Zaretskii
2007-01-07 22:03 ` Drew Adams
2007-01-07 22:08 ` Drew Adams
2007-01-08 1:40 ` Chris Moore
2007-01-08 2:04 ` Drew Adams
2007-01-08 10:15 ` Jason Rumney
2007-01-08 16:29 ` Drew Adams
2007-01-09 0:01 ` Richard Stallman
2007-01-09 0:30 ` Jason Rumney
2007-01-09 12:55 ` Stephen Leake
2007-01-09 17:57 ` Richard Stallman [this message]
2007-01-08 8:44 ` Stephen Leake
2007-01-08 13:07 ` Chris Moore
2007-01-08 19:30 ` Eli Zaretskii
2007-01-09 12:52 ` Stephen Leake
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=E1H4LDl-0005xJ-9X@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dooglus@gmail.com \
--cc=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=stephen_leake@member.fsf.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.