Zsh Mailing List Archive
Messages sorted by:
Re: [PATCH v2 2/3] Fix the ':A' word modifier on paths with '..' components.
- X-seq: zsh-workers 38778
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: [PATCH v2 2/3] Fix the ':A' word modifier on paths with '..' components.
- Date: Fri, 1 Jul 2016 09:05:29 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=HfyMFkfBDUZMaUa+zQfAr0uS4l2A3tpEF8t55ViOLWw=; b=ITWoRyZJBya+fMfzvfZ4S0OGNglOKAMOt2e7AasUDrd4Oen/lSNe3i/zFzhcP7WuEo aB3NJF08/gG4wqdfGb7DkKBqqjRC8ypqdZpBSeuT3CzwQXEDj+Dd0ZDjCJ5dyBYnnnmX DTSh44+tv/gRidt7g7/CYxRBVXE0Z4MEB006baRGobqeCwXWoYIQJp9HEzKG5akQzSrE Op1hHo9Rr22lSNJWUfaI2vN5OWm6KZVc5Rjq0WQ2w2GtuQ6nnFDobNMTFaEW8O4LHyPF cTmWH8ACSRqs0Y7waIRJzEsmqFeRST61EfMQnsRAhvqGNd0qRhy2bhE6BGOZK8iWDpas j2Mg==
- In-reply-to: <20160701051106.GA31422@tarsus.local2>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20160613085218.GA9572@tarsus.local2> <firstname.lastname@example.org> <email@example.com> <CAHYJk3QPM+wKmzoT5jhPD90e=kYpdT0Yf2hNXcZd9woUSov+Mg@mail.gmail.com> <20160625162807.GA9840@tarsus.local2> <CAHYJk3SrjHP3mT+c7xWH49ozhh18WHvLC5LRUzoZwWnkSSv8fA@mail.gmail.com> <20160627002031.GA20366@tarsus.local2> <160628074851.ZM26955@torch.brasslantern.com> <20160701051106.GA31422@tarsus.local2>
On Jul 1, 5:11am, Daniel Shahaf wrote:
} Subject: Re: [PATCH v2 2/3] Fix the ':A' word modifier on paths with '..'
} What's the use-case for the "resolve '..' before symlinks" behaviour?
} Was it an intentional design feature, or simply a documented bug?
} (Honest question.)
PWS will have to weigh in on that one. The use-case may simply have
been the intention to make :A a superset of :a.
} (Perhaps instead of a new option, a new syntax; e.g., have $foo:A retain
} its meaning and $foo:A:A have the new meaning. Or make :A take an
} optional argument.)
Not ideal IMO because either would make :A differ from all other history
modifiers in this respect. I.e. :A:A should mean to resolve to real
path and then resolve to real path again, like :h:h means to chop two
elements off the tail (and thus the second :A should be a no-op like
repeating :t); and no other has an optional argument. However, worth
Sorry to just sort of leave things there. I don't have a strong
objection to changing the :A default given the :a:A equivalence, and
that seems the least confusing final outcome if we conclude that the
likelihood of breaking scripts is small, but I would like to reach a
Messages sorted by: