From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Document _canonical_paths.
Date: Fri, 19 Aug 2016 15:56:39 +0000 [thread overview]
Message-ID: <20160819155639.GA17597@fujitsu.shahaf.local2> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2016-08-19 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 22:48 Daniel Shahaf
2016-08-17 6:28 ` Bart Schaefer
2016-08-17 16:31 ` Daniel Shahaf
2016-08-17 16:53 ` Bart Schaefer
2016-08-18 16:55 ` Daniel Shahaf
2016-08-19 1:09 ` Bart Schaefer
2016-08-19 15:56 ` Daniel Shahaf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160819155639.GA17597@fujitsu.shahaf.local2 \
--to=d.s@daniel.shahaf.name \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).