Re: Next release (5.3)

[Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>]

Peter Stephenson wrote on Wed, Jul 20, 2016 at 15:15:17 +0100:
> On Wed, 20 Jul 2016 16:00:06 +0200
> Vincent Lefevre <vincent@xxxxxxxxxx> wrote:
> > But it does not say how ".." is resolved.
> 
> Yes, we should be clear it's the way zsh has done it with the default
> option settings for directories in the past.

This patch conflicts with my 21779 [I did not push immediately after
posting to allow for feedback].

I think both of them make sense: 21779 specifies the behaviour in
absolute terms and 21784 provides the "this is the algorithm 'cd' uses"
information.

Cheers,

Daniel

> pws
> 
> diff --git a/Doc/Zsh/expn.yo b/Doc/Zsh/expn.yo
> index c5f3c00..eb90e8d 100644
> --- a/Doc/Zsh/expn.yo
> +++ b/Doc/Zsh/expn.yo
> @@ -220,6 +220,13 @@ startitem()
>  item(tt(a))(
>  Turn a file name into an absolute path:  prepends the current directory,
>  if necessary, and resolves any use of `tt(..)' and `tt(.)' in the path.
> +The resolution takes in the same manner as when changing directories
> +when neither of the options tt(CHASE_DOTS) or tt(CHASE_LINKS) is
> +set, i.e. this is on the logical, not the physical, directory.
> +For example, the components tt(before/here/../after) resolve
> +to tt(before/after) regardless of any symbolic links that may
> +occur when traversing the path.
> +
>  Note that the transformation takes place even if the file or any
>  intervening directories do not exist.
>  )
>