Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts)
Date: Fri, 19 Aug 2016 15:56:39 +0000
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Document _canonical_paths.
Message-ID: <20160819155639.GA17597@fujitsu.shahaf.local2>
References: <1471387721-5256-1-git-send-email-danielsh@tarsus.local2>
 <160816232827.ZM19685@torch.brasslantern.com>
 <20160817163140.GA9003@tarsus.local2>
 <160817095330.ZM21532@torch.brasslantern.com>
 <20160818165523.GA25890@tarsus.local2>
 <160818180928.ZM30000@torch.brasslantern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <160818180928.ZM30000@torch.brasslantern.com>
User-Agent: Mutt/1.5.23 (2014-03-12)

Bart Schaefer wrote on Thu, Aug 18, 2016 at 18:09:28 -0700:
> If the programmer of the function went to the trouble of including a
> documentary comment, it's not the job of the documentation writer to
> nullify that.

39044 does not nullify Clint's work: the new manual text builds
on Clint's docstring and makes _canonical_paths more discoverable.

I concede that 39044 would have broken a workflow whereby one reads
a function's docstring by opening the file defining the function,
and I addressed the issue by committing an alternate patch that breaks
no workflow.

Let's move on.  The reason I got into _canonical_paths at all is that
I'm trying to improve _umount, see separate thread.

Cheers,

Daniel