[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: opening /tmp//foo doesn't work.
From: |
Chong Yidong |
Subject: |
Re: opening /tmp//foo doesn't work. |
Date: |
Sat, 12 Nov 2005 12:23:51 -0500 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
address@hidden (Tomas Zerolo) writes:
> On Sat, Nov 12, 2005 at 11:46:58AM +0059, Han Boetes wrote:
>> Hi,
>>
>> If you try to open /tmp//foo emacs will try to open /foo, of
>> course this is a great feature, but it forgets that /tmp//foo is a
>> valid notation of /tmp/foo.
>
> To interpret /tmp//foo is surprising to me. For example, my OS says
> /tmp//foo --> /tmp/foo, as I think most Unixen do (I think POSIX
> dictates that).
The reason is convenience. This allows you to enter a new filename
without having to erase the default offered in the minibuffer. (A
similar example: /tmp/~/foo goes to ~/foo). I use this feature all
the time.
If you want to visit /tmp/foo, might I suggest entering /tmp/foo
instead of /tmp//foo?
Re: opening /tmp//foo doesn't work., Tomas Zerolo, 2005/11/12
- Re: opening /tmp//foo doesn't work.,
Chong Yidong <=
- Start value in minibuffer [Was: opening /tmp//foo doesn't work.], Lars Hansen, 2005/11/13
- RE: Start value in minibuffer [Was: opening /tmp//foo doesn't work.], Drew Adams, 2005/11/13
- Re: Start value in minibuffer [Was: opening /tmp//foo doesn't work.], Lennart Borgman, 2005/11/13
- RE: Start value in minibuffer [Was: opening /tmp//foo doesn't work.], Drew Adams, 2005/11/13
- Re: Start value in minibuffer [Was: opening /tmp//foo doesn't work.], Lennart Borgman, 2005/11/13
- Re: Start value in minibuffer [Was: opening /tmp//foo doesn't work.], Richard M. Stallman, 2005/11/15
- Re: Start value in minibuffer [Was: opening /tmp//foo doesn't work.], Miles Bader, 2005/11/13
- Re: Start value in minibuffer [Was: opening /tmp//foo doesn't work.], Lennart Borgman, 2005/11/13
Re: Start value in minibuffer, Stefan Monnier, 2005/11/13
Re: Start value in minibuffer, Kim F. Storm, 2005/11/13