| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
From now on, we should edit the rst source.
|
| |
|
|
|
|
|
|
| |
The python script mkdocdeps.py is used to import the list of man pages
from the sphinx configuration to make.
This will delete the (release only) target update-man-versions. This
will be replaced in a followup commit.
|
| |
|
|
|
|
|
|
| |
The example was originally intended to have a literal backslash in it, but
'\ ' is interpreted by nroff as a non-breaking space.
It doesn't make much difference to the example, but the non-breaking
space triggers a bug in doclifter.
|
| |
|
|
| |
Fix for Debian bug 739556
|
| | |
|
| |
|
|
|
|
| |
Actually the previous default was not documented explicitely. I moved
the batch-tag section first because it seemed that the formats were
previously documented in order default, other.
|
| | |
|
| |
|
|
|
| |
Unfortunately release-checks.sh will whine a bit because it has not
caught up with the renaming of the version macros.
|
| |
|
|
|
|
|
|
| |
Roll (one last?) release candidate because of Austin's
LIBNOTMUCH_VERSION changes.
Atomically bump the manually (NEWS, debian/changelog) and
automatically (everywhere else) updated places version is mentioned.
|
| | |
|
| |
|
|
|
| |
Various other files are synched using "make update-versions". NEWS
has to be hand edited.
|
| | |
|
| |
|
|
| |
Signed-off-by: Ben Gamari <bgamari.foss@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
For my client, the largest bottleneck for displaying large threads is
exporting each html part individually since by default notmuch will not
show the json parts. For large threads there can be quite a few parts and
each must be exported and decoded one by one. Also, I then have to deal
with all the crazy charsets which I can do through a library but is a
pain.
Therefore, this patch adds an --include-html option that causes the
text/html parts to be included as part of the output of show.
diff man/man1/notmuch-show.1
|
| |
|
|
| |
The results for folder: prefix are a source of recurring confusion.
|
| |
|
|
| |
Document the notmuch count --output=files option.
|
| |
|
|
| |
Document the notmuch search --duplicate=N option.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, reply's default text format used an odd mix of RFC 2045
MIME encoding for the reply template's body and some made-up RFC
2822-like UTF-8 format for the headers. The intent was to present the
headers to the user in a nice, un-encoded format, but this assumed
that whatever ultimately sent the email would RFC 2047-encode the
headers, while at the same time the body was already RFC 2045 encoded,
so it assumed that whatever sent the email would *not* re-encode the
body.
This can be fixed by either producing a fully decoded UTF-8 reply
template, or a fully encoded MIME-compliant RFC 2822 message. This
patch does the latter because it is
a) Well-defined by RFC 2822 and MIME (while any UTF-8 format would be
ad hoc).
b) Ready to be piped to sendmail. The point of the text format is to
be minimal, so a user should be able to pop up the template in
whatever editor they want, edit it, and push it to sendmail.
c) Consistent with frontend capabilities. If a frontend has the
smarts to RFC 2047 encode the headers before sending the mail, it
probably has the smarts to RFC 2047 decode them before presenting
the template to a user for editing.
Also, as far as I know, nothing automated consumes the reply text
format, so changing this should not cause serious problems. (And if
anything does still consume this format, it probably gets these
encoding issues wrong anyway.)
|
| |
|
|
|
| |
man pages, NEWS, and debian changelog all hardcode date. Make them
hardcode the same date.
|
| |
|
|
|
| |
These are manually set in version and NEWS, and propagate to the other files via
"make update-versions"
|
| |
|
|
| |
Add documentation for notmuch insert --create-folder option.
|
| |
|
|
| |
Add documentation for notmuch insert --folder option.
|
| |
|
|
| |
Add references to notmuch-insert.1 from other man pages.
|
| |
|
|
| |
Add initial documentation for notmuch insert command.
|
| |
|
|
|
|
|
| |
While looked good on paper, its attempted use caused confusion, complexity,
and potential for information leak when passed through wrapper scripts.
For slimmer code and to lessen demand for maintenance/support the set of
commits which added top level --stderr= option is now reverted.
|
| | |
|
| |
|
|
| |
Document the new search --exclude=all option.
|
| |
|
|
|
| |
Improve the description of the search --exclude=flag option,
using text taken from the commit that introduced the option.
|
| |
|
|
|
|
|
|
| |
Highlight "excluded messages" as a term with a meaning that
may not be obvious.
Be explicit about the effects of search --exclude=true and
--exclude=false.
|
| |
|
|
|
| |
This is is really functionality of the library, but CLI users might
not look at library docs even if they existed beyond notmuch.h
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
add in NEWS from 0.15.2
Conflicts:
NEWS
|
| | | |
|
| | | |
|
| |\|
| |
| |
| |
| |
| |
| | |
Conflicts:
NEWS
Inserted news from 0.15.1
|
| | |
| |
| |
| | |
A simple bugfix release, no user visible changes
|
| |/
|
|
|
|
| |
The options --help and --version were not documented before. One
could quibble about how useful that documentation is, but we will soon
add more options.
|
| |
|
|
| |
Bump the version in-place in NEWS.
|
| |
|
|
|
| |
This is in some sense a rollback, but it makes all the automation
happier if the Debian and upstream versions match.
|
| | |
|
| |
|
|
| |
"Atomically" update the python bindings and man page versions.
|
| | |
|
| |
|
|
|
| |
Describe the new batch-tag format. For notmuch-restore, rather than
half-heartedly duplicating the description, we now cite notmuch-dump.
|
| |
|
|
| |
Consistently use [...]; one less space. Use singular <search-term>
|
| | |
|
| | |
|
| | |
|
David Bremner
Jani Nikula
Ben Gamari
John Lenz
Austin Clements
David Bremner
Peter Wang
Tomi Ollila
David Bremner