Emacs integration - an overview
jdc at uwo.ca
Tue Sep 6 18:03:44 CDT 2005
Matt Mackall <mpm at selenic.com> writes:
> On Thu, Sep 01, 2005 at 01:00:42PM -0400, Dan Christensen wrote:
>> Dan Christensen <jdc at uwo.ca> writes:
>> > Bryan O'Sullivan <bos at serpentine.com> writes:
>> >> On Wed, 2005-08-31 at 14:18 -0400, Dan Christensen wrote:
>> >>> But it happens because python's sys.getcwd returns the canonical path,
>> >>> after expanding symlinks. Maybe the solution is for hg to use
>> >>> os.path.realpath on all filenames?
>> >> I don't think so. It's pretty expensive.
> So if you're timing this on Linux, be warned that you may be
> pessimizing other systems.
Ok, thanks for the info. I don't have easy access to other systems
to test, but how slow are we talking about? As far as I can see,
this is only needed for paths specified on the command line, and
there shouldn't be too many of those.
By the way, on further thought this seems like something that could
affect a lot more than mercurial.el. For example, imagine that a
sysadmin decides to move a user's home directory from /home/user
to /home2/user because /home is getting full. The sysadmin leaves
a symlink behind, and doesn't change any other settings, to try
to make this as transparent to the user as possible. If the user
has an hg repo in her home directory, then if she does
hg commit ~/file
hg will respond that the file isn't under hg root!
More information about the Mercurial