unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Peter Wang <novalazy@gmail.com>
To: notmuch@notmuchmail.org
Subject: [announce] Bower 0.10
Date: Sat, 26 Jan 2019 14:10:48 +1100	[thread overview]
Message-ID: <20190126141048.GB16078@kola.localdomain> (raw)

Hi,

Bower is a curses frontend for the Notmuch email system.
I wrote it for me, but you might like it, too.

	https://github.com/wangp/bower

Bower 0.10 (2019-01-26)
=======================

* thread/pager: Add 'W' key to forward message.
* Support BOWER_CONFIG environment variable.
* Document support for XDG Base Directory Specification.
* Support tab expansion for query:.
* Support ~NAME as a shorthand for query:NAME.
* Support Shift-Tab to cycle through completions in reverse.
* Make path completion work more smoothly.
* Minor improvements.

Bower 0.9 (2018-10-07)
======================

* Support conversion of message parts to text using external filters.
* Add ',' key to go to next unread thread/message (synonym for Tab).
* thread/pager: Show pager progress as percentage of current message.
* thread/pager: Periodically poll for new messages.
* config: Replace index.poll_period_secs with ui.poll_period_secs.

Bower 0.8.1 (2018-04-01)
========================

* Save/restore curses mode for any command that might invoke pinentry-curses.
* Add makefile target to produce man page (bower.1).

Bower 0.8 (2017-07-30)
======================
This release requires notmuch 0.21 or above.

* Look up addresses using notmuch address.
* Move add to addressbook to '@' key.
* Add 'a' keys to apply '-inbox -unread' or else '+inbox'.
* Add 'A' key to leave thread view and apply '-inbox -unread' to the thread.
* Bug fixes and minor improvements.

Peter

             reply	other threads:[~2019-01-26  3:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-26  3:10 Peter Wang [this message]
2019-01-26  9:17 ` [announce] Bower 0.10 Ben Oliver
2019-01-26 10:44   ` Peter Wang

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190126141048.GB16078@kola.localdomain \
    --to=novalazy@gmail.com \
    --cc=notmuch@notmuchmail.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://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).