aboutsummaryrefslogtreecommitdiffhomepage
path: root/man/man1/notmuch-reply.1
Commit message (Collapse)AuthorAge
* doc: remove preformatted nroff pagesGravatar David Bremner2014-03-09
| | | | From now on, we should edit the rst source.
* version: bump to 0.17Gravatar David Bremner2013-12-30
|
* version: bump to 0.17~rc4Gravatar David Bremner2013-12-28
| | | | | Unfortunately release-checks.sh will whine a bit because it has not caught up with the renaming of the version macros.
* version: bump versionGravatar David Bremner2013-12-07
| | | | | | | | 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.
* version: bump to 0.17~rc2Gravatar David Bremner2013-11-28
|
* version: bump to 0.17~rc1Gravatar David Bremner2013-11-23
| | | | | Various other files are synched using "make update-versions". NEWS has to be hand edited.
* reply: Use RFC 2822/MIME wholly for text format templateGravatar Austin Clements2013-08-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.)
* release: synchronize datesGravatar David Bremner2013-08-03
| | | | | man pages, NEWS, and debian changelog all hardcode date. Make them hardcode the same date.
* version: set new version and release dateGravatar David Bremner2013-07-28
| | | | | These are manually set in version and NEWS, and propagate to the other files via "make update-versions"
* man: reference notmuch-insert.1Gravatar Peter Wang2013-06-29
| | | | Add references to notmuch-insert.1 from other man pages.
* man: show and reply --decrypt option requires gpg-agentGravatar Jani Nikula2013-03-02
|
* bump versions to 0.15.2Gravatar David Bremner2013-02-17
|
* version: bump to 0.15.1Gravatar David Bremner2013-01-24
| | | | A simple bugfix release, no user visible changes
* version: update to 0.15Gravatar David Bremner2013-01-18
| | | | Bump the version in-place in NEWS.
* version: set version to 0.15~rc1Gravatar David Bremner2013-01-16
| | | | | This is in some sense a rollback, but it makes all the automation happier if the Debian and upstream versions match.
* version: bump to 0.15Gravatar David Bremner2013-01-07
| | | | "Atomically" update the python bindings and man page versions.
* reply: Support --format-versionGravatar Austin Clements2012-12-16
|
* Updating man pages for new S-Expression output format.Gravatar Peter Feigl2012-12-08
| | | | | Add sections about the new S-Expression output format (--format=sexp) to the notmuch-search, notmuch-reply and notmuch-show man pages.
* version: propagate version changesGravatar David Bremner2012-08-21
| | | | These are the result of running "make update-versions"
* manpages: consistent "format" for NAME sectionGravatar Tomi Ollila2012-07-09
| | | | | | The NAME section in manpages generally doesn't start with capital letter (unless the word is 'proper noun') and doesn't end with period. Notmuch manual pages now matches that "format".
* version: update to 0.13.2Gravatar David Bremner2012-06-02
|
* version: bump to 0.13.1Gravatar David Bremner2012-05-25
|
* version: bump to 0.13Gravatar David Bremner2012-05-15
|
* bump version to 0.13~rc1Gravatar David Bremner2012-05-08
|
* Merge branch 'release'Gravatar David Bremner2012-03-19
|\ | | | | | | | | | | | | Conflicts: NEWS Conflicts resolved by hand for date of 0.12 release.
| * update version to 0.12Gravatar David Bremner2012-03-19
| | | | | | | | There may be a few NEWS changes after this, but no code (hopefully).
* | man: Add --decrypt to reply flagsGravatar Adam Wolfe Gordon2012-03-19
| |
* | man: Update notmuch-reply man page for JSON format.Gravatar Adam Wolfe Gordon2012-03-19
|/
* bump version to 0.12~rc2Gravatar David Bremner2012-03-18
|
* man: update SEE ALSO references in man pagesGravatar Jani Nikula2012-03-13
| | | | | Drop references to notmuch-part(1). Reference all man pages. Fix man page section of notmuch-dump(1).
* bump version to 0.12~rc1Gravatar David Bremner2012-03-01
| | | | | As usual, only `version' is edited by hand. The rest of the changes I blame on the machine.
* cli: add support for replying just to the sender in "notmuch reply"Gravatar Jani Nikula2012-01-14
| | | | | | | | | | | | Add new option --reply-to=(all|sender) to "notmuch reply" to select whether to reply to all (sender and all recipients), or just sender. Reply to all remains the default. Credits to Mark Walters <markwalters1009@gmail.com> for his similar earlier work where I picked up the basic idea of handling reply-to-sender in add_recipients_from_message(). All bugs are mine, though. Signed-off-by: Jani Nikula <jani@nikula.org>
* man: add missing SEE ALSO header to notmuch reply man pageGravatar Jani Nikula2012-01-10
| | | | Signed-off-by: Jani Nikula <jani@nikula.org>
* man/*: fixup page referencesGravatar David Bremner2011-12-31
| | | | | | | - Replace references to section X below with page refences. - Add SEE ALSO to each page. This is a bit error prone, because each SEE ALSO section is different, i.e. a page does not refer to itself.
* man/*: formatting cleanupGravatar David Bremner2011-12-31
| | | | | | | | | | | | | | | | | | | | | | | | | | Fix some problems with indentation (controlled by markup) and whitespace. - notmuch.1: reformat Use .SS macro to make "notmuch setup" a subsection. Introduce another subsection for the remaining commands. - notmuch-config.1: reformat Put all the syntax in the synopsis. Supposedly this is the the UNIX way. - notmuch-reply.1: fix formatting issues. Give nicer formatting for synopsis. Insert missing SEE ALSO header. - notmuch-dump.1: reformat using subsections These seems more natural, although, as mentioned, it does require referring back to the synopsis. Or maybe copying parts of the synopsis
* initial splitting of notmuch.1Gravatar David Bremner2011-12-31
We mostly just cut and paste the command descriptions into individual files, with a short header added to each one. The splitting into subdirectories is to support the use of ./man as an element in MANPATH, e.g. for testing.
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-12 22:01:12 +0000