zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] Document _canonical_paths.
Date: Thu, 18 Aug 2016 18:09:28 -0700	[thread overview]
Message-ID: <160818180928.ZM30000@torch.brasslantern.com> (raw)
In-Reply-To: <20160818165523.GA25890@tarsus.local2>

On Aug 18,  4:55pm, Daniel Shahaf wrote:
}
} If we really want the docstring to be present in both locations, I think
} one of them should be autogenerated from the other.

I think that would be an overengineered solution to what ought to be a
non-problem.  We definitely don't want the function files being modified
by the doc formatter, and the alternative -- requiring every function
file to contain a specially-formatted comment -- is both a barrier to
users who want to contribute functions, and likely to make any such
comments more difficult to read as simple text.

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.  If you prefer not to contribute functions that have
such comments and to write yodl instead, good for you; and if you want
to write yodl for functions that others have contributed, then that's
even better; but I object to the removal of another programmer's
commentary unless a corresponding *programming* change has made it
inaccurate or obsolete.


  reply	other threads:[~2016-08-19  1:09 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 [this message]
2016-08-19 15:56           ` Daniel Shahaf

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=160818180928.ZM30000@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --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).