Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Directory completion acts as if CHASE_LINKS is set
- X-seq: zsh-workers 31704
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: Directory completion acts as if CHASE_LINKS is set
- Date: Thu, 05 Sep 2013 23:13:36 -0700
- In-reply-to: <l0bbuk$gqp$1@ger.gmane.org>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <l08meg$v06$1@ger.gmane.org> <130905083139.ZM29859@torch.brasslantern.com> <l0bbuk$gqp$1@ger.gmane.org>
On Sep 6, 1:42pm, Jan Larres wrote:
} Subject: Re: Directory completion acts as if CHASE_LINKS is set
}
} On 06/09/13 03:31, Bart Schaefer wrote:
} > In any case, this is a problem inherent in the way globbing interprets
} > "../" -- filename generation does not obey the same rules as "cd" path
} > resolution.
}
} Thanks, that patch does solve the issue with cd to a certain degree. But
} as you said yourself it is not specific to cd - for example, 'ls ../[TAB]'
} has the same problem.
No, you misunderstand. It actually *is* specific to cd -- ls is an
external command and will physically follow ../, so it is correct for
completion for ls to do so as well.
Only in shell builtins can ../ refer to $PWD:h/, and the only builtins
that have this behavior are cd and pushd.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author