unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ami Fischman <ami@fischman.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: emacs-devel@gnu.org
Subject: Re: bug with automount-dir-prefix handling in abbreviate-file-name
Date: Thu, 6 Aug 2009 10:07:36 -0700	[thread overview]
Message-ID: <9aa0cfde0908061007y518f3e1cue90d2cd1e4b95c69@mail.gmail.com> (raw)
In-Reply-To: <m3ocqsj2w1.fsf@hase.home>

Are you saying that everything is working as intended, or are you
saying that abbreviate-file-name's behavior is as expected, but that
the find-file failure is a bug?

The only reason I mentioned abbreviate-file-name was to point out
where in the backtrace the directory name became unusable.  It still
seems like a bug to me that this results in an error.

Perhaps a clearer demonstration of what I think the problem is is to
use the default values:
sudo mkdir -p /tmp_mnt/fooblah
emacs -Q
C-x C-f /tmp_mnt/fooblah/
results in the message:
apply: Setting current directory: no such file or directory, /fooblah/
and no dired buffer.

-a


On Thu, Aug 6, 2009 at 9:58 AM, Andreas Schwab<schwab@linux-m68k.org> wrote:
> Ami Fischman <ami@fischman.org> writes:
>
>> The error is caused by abbreviate-file-name stripping /home from /home/fischman.
>
> Which is exactly the point of automount-dir-prefix.
>
> Andreas.
>
> --
> Andreas Schwab, schwab@linux-m68k.org
> GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
> "And now for something completely different."
>




  reply	other threads:[~2009-08-06 17:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-06 16:35 bug with automount-dir-prefix handling in abbreviate-file-name Ami Fischman
2009-08-06 16:58 ` Andreas Schwab
2009-08-06 17:07   ` Ami Fischman [this message]
2009-08-06 18:09 ` Stefan Monnier
2009-08-06 18:39   ` Ami Fischman
2009-08-07  4:45     ` Stefan Monnier
2009-08-07  8:54       ` Andreas Schwab
2009-08-07 14:20         ` Ami Fischman

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=9aa0cfde0908061007y518f3e1cue90d2cd1e4b95c69@mail.gmail.com \
    --to=ami@fischman.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@linux-m68k.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).