On Thu, Dec 31 2015, David Bremner wrote:
> Jani Nikula writes:
>
>> On Wed, 30 Dec 2015, "W. Trevor King" wrote:
>>> To describe the config file format, so folks don't have to dig through
>>> NEWS or the nmbug-status source to get that
Tomi Ollila writes:
>
> What we could simply have at the time being:
>
> devel/nmbug/nmbug
> devel/nmbug/nmbug.rst (or .1)
> devel/nmbug/nmbug-status
> devel/nmbug/nmbug-status.rst (or .1)
> devel/nmbug/nmbug-status-config
> devel/nmbug/nmbug-status-config.rst (or
"W. Trevor King" writes:
> So separate --without-… configure flags for each script, which will
> also control the associated man pages and handle runtime-dependency
> warnings/errors?
Or just have e.g. the nmbug-status install depend on the hypothetical
--without-python flag.
On Fri, Jan 01, 2016 at 01:23:37PM +0200, Tomi Ollila wrote:
> What we could simply have at the time being:
>
> devel/nmbug/nmbug
> devel/nmbug/nmbug.rst (or .1)
> devel/nmbug/nmbug-status
> devel/nmbug/nmbug-status.rst (or .1)
> devel/nmbug/nmbug-status-config
>
Jani Nikula writes:
> On Wed, 30 Dec 2015, "W. Trevor King" wrote:
>> To describe the config file format, so folks don't have to dig through
>> NEWS or the nmbug-status source to get that information.
>
> Overall I approve of the series (though I did not do a
On Thu, Dec 31, 2015 at 06:11:34PM -0400, David Bremner wrote:
> W. Trevor King writes:
> > On Thu, Dec 31, 2015 at 01:39:21PM -0400, David Bremner wrote:
> >> For me it's a bit odd to have a man page for a tool we don't
> >> install by default. Is it maybe time to "promote" nmbug-status to
> >>
"W. Trevor King" writes:
> On Thu, Dec 31, 2015 at 01:39:21PM -0400, David Bremner wrote:
>
>> For me it's a bit odd to have a man page for a tool we don't install
>> by default. Is it maybe time to "promote" nmbug-status to the
>> notmuch- namespace and install it by default?
On Thu, Dec 31, 2015 at 01:39:21PM -0400, David Bremner wrote:
> Jani Nikula writes:
> > I am wondering about the man page though. I find it slightly
> > confusing there would be a man page named after the tool
> > describing just the config, but not the tool itself.
Yeah, a man page about the
To describe the config file format, so folks don't have to dig through
NEWS or the nmbug-status source to get that information.
---
NEWS | 5 ++
devel/nmbug/nmbug-status | 19 ---
doc/conf.py | 6 ++
doc/index.rst | 1 +