---
NEWS | 26 ++
1 file changed, 26 insertions(+)
diff --git a/NEWS b/NEWS
index 6681699..3535614 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,29 @@
+Notmuch 0.22 (UNRELEASED)
+=
+
+Documentation
+-
+
+New `notmuch-report(1)` and `notmuch-re
This script generates reports based on notmuch queries, and doesn't
really have anything to do with nmbug, except for sharing the NMBGIT
environment variable.
---
devel/nmbug/nmbug-status | 419 -
devel/nmbug/notmuch-report | 419 ++
status-config.json wasn't obviously associated with the old
nmubg-status, now notmuch-report. The new name is
${CONFIGURED_SCRIPT}.json, so the association should be clear.
---
devel/nmbug/notmuch-report | 2 +-
devel/nmbug/notmuch-report.json | 70 +
Spun off from discussion here [1]. I've just shifted nmbug-status in
this series, and left nmbug alone for now. If/when this series lands,
it will be easy to handle a nmbug rename in a subsequent series.
Note that while I think the renames from nmbug-status to
notmuch-report and status-config.js
These are now added by nmbug-status.
---
devel/nmbug/status-config.json | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/devel/nmbug/status-config.json b/devel/nmbug/status-config.json
index b926946..48b6f19 100644
--- a/devel/nmbug/status-config.json
+++ b/devel/nmbug/status-co
We already have a 'filename' variable with the name, so stay DRY and
use that variable here.
Also fix a missing-whitespace error from bed8b674 (nmbug-status:
Clarify errors for illegible configs, 2014-05-10), wrapping on the
sentence to match similar error-generation earlier in this function.
---
To describe the script and config file format, so folks don't have to
dig through NEWS or the script's source to get that information.
The Makefile and conf.py are excerpted from the main doc/ directory
with minor simplifications and adjustments. The devel/nmbug/ scripts
are largely independent o
So you can link to archives other than Gmane. For example, I'm doing
this in [1].
[1]: https://github.com/wking/nmbug-oci
---
NEWS | 20
devel/nmbug/nmbug-status | 13 ++---
2 files changed, 30 insertions(+), 3 deletions(-)
diff --git a/NEWS b/NE
For example:
"query": ["tag:a", "tag:b or tag:c"]
is now converted to:
( tag:a ) and ( tag:b or tag:c )
instead of the old:
tag:a and tag:b or tag:c
This helps us avoid confusion due to Xapian's higher-precedence AND
[1], where the old query would be interpreted as:
( tag:a and tag:b
Changes since v1 [1]:
* [4/5, v2 3/4] Added parentheses handling for ‘nmbug-status
--get-query VIEW’ too [2].
* [3/5] Dropped the man page, and will file a separate series that
adds man pages to the script directory [3].
Cheers,
Trevor
[1]: id:cover.1451502495.git.wk...@tremily.us
http:
That closing brace is the end of the config JSON; there won't be
anything coming after it.
---
NEWS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/NEWS b/NEWS
index 6681699..0a7a0e0 100644
--- a/NEWS
+++ b/NEWS
@@ -409,7 +409,7 @@ from the config file. Use something like:
On Fri, Jan 01 2016, "W. Trevor King" wrote:
> On Fri, Jan 01, 2016 at 01:30:57PM +0200, Tomi Ollila wrote:
>> yes, I have old tidy (20091203), and the complaints were about
>> utf8-characters (being invalid) in output and
>
> UTF-8 should be valid, because we declare the charset in:
>
>
>
>
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
> devel/nmbug/nmbug-stat
On Fri, Jan 01, 2016 at 01:30:57PM +0200, Tomi Ollila wrote:
> yes, I have old tidy (20091203), and the complaints were about
> utf8-characters (being invalid) in output and
UTF-8 should be valid, because we declare the charset in:
If you feel like the UTF-8 complaints are valid, can you pos
David Bremner writes:
> Michal Sojka writes:
>
>> This commit fixes these problems by replacing a call to message-mail
>> with notmuch-specific code that is (hopefully) equivalent to
>> message-mail functionality before introduction of
>> notmuch-message-mode.
>
> pushed to master
It seems to h
Michal Sojka writes:
> This commit fixes these problems by replacing a call to message-mail
> with notmuch-specific code that is (hopefully) equivalent to
> message-mail functionality before introduction of
> notmuch-message-mode.
pushed to master
d
_
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 .5)
>
> (and if .rst
"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.
>
> Looking over
On Thu, Dec 31 2015, "W. Trevor King" wrote:
> On Thu, Dec 31, 2015 at 03:46:50PM +0200, Tomi Ollila wrote:
>> This series LGTM. (html) tidy complains about imo irrelevant things
>> -- or I just did not know how to use it correctly -- as `| tidy
>> -eq`.
>
> That doesn't complain about anything w
From: Janos Farkas
Subject: [PATCH] cli/insert: do not lose the SMTP envelope
Make sure we store the envelope sender/recipient if provided by
qmail-command(8) in $RPLINE and $DTLINE.
---
I just realised that the messages delivered directly into maildir don't have
the usual envelope addresses tha
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 information.
>>
>> Overall I approve of the series (though
21 matches
Mail list logo