Closed vivien closed 5 years ago
I'll add completion support for query:
.
As for deprecating bower's search term aliases, perhaps we could make the ~NAME
syntax equivalent to query:NAME
. However, the ~
syntax would not be usable inside of saved queries themselves. It's not a big issue, but I'll continue to use search term aliases myself since the code is already there. If you need to use other notmuch clients as well, you might prefer saved queries instead.
Indeed ~NAME
can look for a bower search term alias, or fallback to config get query.NAME
so that retro-compatibility is maintained. Indeed I share notmuch saved queries between a status line, bower, and notmuch command line.
Yeah, that's probably acceptable. Please test the named-query branch.
Hi @wangp, I've first installed bower with the bower-mail
AUR packages, which install Mercury as a shared library. Thus I don't have /usr/lib/mercury/lib/reg.gc/libmer_{std,rt}.a
. How can I compile bower from source with a shared Mercury?
Disable this line in src/Mercury.options
MCFLAGS-bower += --mercury-linkage static
./bower
works perfectly with query:<Tab>
or ~<Tab>
!
Merged to master, thanks for testing.
Hi there, first of all, thanks for the project, finally a notmuch frontend which feels mature and robust to me. I really like its simplicity and its convention-over-configuration feel as well, no tons of options to learn.
I was looking at the documentation and the search terms aliases which seem to have now an upstream alternative, i.e. the saved queries.
e.g.
notmuch config set query.foo 'tag:foo AND bar'
can be used with e.g.notmuch search query:foo and baz
.Shouldn't bower's search term aliases be deprecated in favor of the user configured
query:
search terms?