bug#508: marked as done (emacs 22.2.1 becomes confused)

[Emacs bug Tracking System]

Your message dated Thu, 31 Jul 2008 17:17:07 -0400
with message-id <87iquleoto.fsf@stupidchicken.com>
and subject line Re: bug#508: emacs 22.2.1 becomes confused
has caused the Emacs bug report #508,
regarding emacs 22.2.1 becomes confused
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 don@donarmstrong.com
immediately.)


-- 
508: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=508
Emacs Bug Tracking System
Contact don@donarmstrong.com with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> emacs 22.2.1 becomes confused
>
>
>
>
> Date: 
>
> Mon, 30 Jun 2008 08:03:12 -0700
>
>
>
>
> Hi,
>
> I recently re-installed my system.  For various reasons not worth
> going into here,
> I renamed my home directory from /home/foo to /home/Foo and re-created my
> "foo" user name.  It is not possible to edit anything in the /home/Foo hierarchy
> with emacs.  At all.  I can cd to the correct directory and invoke "emacs file"
> and it will try to open the equivalently named file under /home/foo.  Somebody
> somewhere fiddled some code such that tab-completion works correctly, but
> when it comes to actually "visiting" the file, the blasted thing substitutes
> "$HOME" for "/home/Foo".  Someone please be kind enough to find that
> "strncasecmp" and replace it with "strncmp" and put out an emergency fix.
>
> Thank you.  Regards, Bruce
>
> $ /usr/bin/emacs --version
> GNU Emacs 22.2.1
> Copyright (C) 2008 Free Software Foundation, Inc.
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#508: emacs 22.2.1 becomes confused
>
>
>
>
> Date: 
>
> Thu, 31 Jul 2008 17:17:07 -0400
>
>
>
>
> Since no one has offered to write a directory-case-sensitive-p function,
> I've checked in Sven's first, simpler patch.  Even if it doesn't do the
> completely right thing in the failure case (e.g., a vfat home directory
> on GNU/Linux), all that does is fail to replace $HOME with ~, which is
> hardly fatal.
>
> After the release, if someone wants to write directory-case-sensitive-p,
> we can switch to that.
>
>
> --- End Message ---