Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] Document _canonical_paths.
- X-seq: zsh-workers 39069
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: [PATCH] Document _canonical_paths.
- Date: Fri, 19 Aug 2016 15:56:39 +0000
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=mesmtp; bh=SLtk6f2rODsRyV696kuVrtmHcwA=; b=UpIAnM v8Qb6Yo4gTemjIB5KVsZayEzpIzFfR2qfzVuNnb64VFaEJyUqLVuyuwjprIIGOMN na6iWR6VYX/Z5lspUdG5BAlH6AN5LWwHDPAk+TLRV+7bQuvdyRGhWBifjuPn8LQO o6XduuzXWl2TZ5DIBIuoOC3Y34azg9ziFTa8s=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-sasl-enc :x-sasl-enc; s=smtpout; bh=SLtk6f2rODsRyV696kuVrtmHcwA=; b=UQYQE ZmpiN3hCV6sWBqy6qCpjjMkyxTiN8wNSsO2jXV3Y3k8Ghx3SpmJ8q2P1Av07MIpz HLdBc51dT5GHhqCvxZMkooEsOGjJWKltT6/eano0pxwUKEu8SYcA1EEXcL5Q04ku SWf90SPRO6QLxlECnEe2ZYXdtluW04PdE1vKWA=
- In-reply-to: <160818180928.ZM30000@torch.brasslantern.com>
- 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: <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>
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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author