[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: directory names ending with a colon confuse dired
From: |
Chris Moore |
Subject: |
Re: directory names ending with a colon confuse dired |
Date: |
Fri, 22 Sep 2006 00:31:10 +0200 |
On Fri, 2006-09-22 at 00:17 +0200, Chris Moore wrote:
> If I use 'dired' on a directory which has a subdirectory with a name
> ending with a colon, and do a recursive directory listing in there, I
> can't visit any files under subdirectories.
It seems the problem is related to the value of dired-subdir-alist.
With the directory called 'colon:', I see:
Its value is
(("/tmp/dir/" . #<marker at 1 in dir>))
If I rename 'colon:' to 'colon', then its value changes to this correct
value:
(("/tmp/dir/subdir/" . #<marker at 366 in dir>)
("/tmp/dir/colon/" . #<marker at 238 in dir>)
("/tmp/dir/" . #<marker at 1 in dir>))
- directory names ending with a colon confuse dired, Chris Moore, 2006/09/21
- Re: directory names ending with a colon confuse dired,
Chris Moore <=
- Re: directory names ending with a colon confuse dired, Chris Moore, 2006/09/21
- Re: directory names ending with a colon confuse dired, Chris Moore, 2006/09/21
- Re: directory names ending with a colon confuse dired, Richard Stallman, 2006/09/22
- Re: directory names ending with a colon confuse dired, Chris Moore, 2006/09/22
- Re: directory names ending with a colon confuse dired, Johan Bockgård, 2006/09/23
- Re: directory names ending with a colon confuse dired, Richard Stallman, 2006/09/23
- Re: directory names ending with a colon confuse dired, Chris Moore, 2006/09/25