Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160612094916.ZM9751@torch.brasslantern.com>
Date: Sun, 12 Jun 2016 09:49:16 -0700
In-Reply-To: <20160612142843.GD10072@tarsus.local2>
Comments: In reply to Daniel Shahaf <d.s@daniel.shahaf.name>
        "Re: [PATCH 2/3] Fix the ':A' word modifier on paths with '..' components." (Jun 12,  2:28pm)
References: <1465580184-3095-1-git-send-email-danielsh@tarsus.local2> 
	<1465580184-3095-2-git-send-email-danielsh@tarsus.local2> 
	<CAHYJk3RGbXMQacRTCfK2PFnN10rfX46dcy_LPi6P9E5b29hiAA@mail.gmail.com> 
	<160610124623.ZM9598@torch.brasslantern.com> 
	<20160612142843.GD10072@tarsus.local2>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: [PATCH 2/3] Fix the ':A' word modifier on paths with '..' components.
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jun 12,  2:28pm, Daniel Shahaf wrote:
}
} So, how about:
} 
} - :a remains as it is today
} - :A when CHASE_DOTS set: same as :A today (resolves '..' first and
}   symlinks second)
} - :A when CHASE_DOTS unset: as in the patch: equivalent to realpath(3)
}   except that non-existing trailing path components are permitted
} 
} Would that address everyone's concerns?

I believe it would resolve most of mine.  :A is a relatively new feature
so it would be understandable for it to evolve a bit.  However, it is in
use in a few places already (e.g., expand-absolute-path, VCS_INFO_quilt,
zsh-mime-handler).  I don't think any of those uses would be compromised
by this change, but if anyone wants to do a more thorough search for use
cases, don't be shy.

} Note this doesn't use CHASE_LINKS at all, neither in :A nor in :a.

Makes sense; :a plus CHASE_LINKS would be :A.