From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: man pages aren't updated
Date: Wed, 2 Nov 2016 20:12:18 -0700 [thread overview]
Message-ID: <161102201218.ZM1574@torch.brasslantern.com> (raw)
In-Reply-To: <20161103005120.GA6442@localhost.localdomain>
On Nov 3, 8:51am, Han Pingtian wrote:
}
} On Wed, Nov 02, 2016 at 04:38:17PM +0000, Daniel Shahaf wrote:
} > That's just a routine diagnostic buried among hundreds of its kind;
} > people won't pay it any attention. (And configure -q hides it.) I meant
} > a new, explicit warning: "yodl not found; documentation won't be built".
}
} Agree. It would be good if there was such a message.
There's a bit of a conflict here: If you download the tarball, instead of
pulling from git, then you're supposed to also download the documentation
tarball rather than (need to) build the documentation yourself. So the
message appropriate for a developer might not be appropriate for a
package installer or other user.
next prev parent reply other threads:[~2016-11-03 3:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161101034638.GA4209__13062.8586317927$1478010076$gmane$org@localhost.localdomain>
2016-11-01 15:37 ` Daniel Shahaf
2016-11-02 2:09 ` Han Pingtian
[not found] ` <20161102020916.GA5804__39989.4180395224$1478052681$gmane$org@localhost.localdomain>
2016-11-02 3:00 ` Daniel Shahaf
2016-11-02 5:53 ` Han Pingtian
[not found] ` <20161102055343.GB5804__17355.3773820915$1478066113$gmane$org@localhost.localdomain>
2016-11-02 16:38 ` Daniel Shahaf
2016-11-03 0:51 ` Han Pingtian
2016-11-03 3:12 ` Bart Schaefer [this message]
2016-11-01 3:46 Han Pingtian
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=161102201218.ZM1574@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@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).