Re: [PATCH] completion: remove "setup" from the list of possible completions
* Tomi Ollila: > imo.the completions should primarily provide convenience to the > interactive user, to see all possible options (also those > seldomly.used) one can use help and namual pages... "Can use" being the operative term, not "should have to use". I would not want completion to omit certain commands, based on somebody else's notion of what is convenient, which in turn forces me to use other means of figuring out a seldom-used command I may or may not be aware of. If this means entering three characters instead of two, then three characters it is. Alternatively, make it a configurable option, with "convenient=false" being the default. I vote against the change. First world problems... ;-) -Ralph ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: crypto test failures on Fedora and OpenSUSE
I poked at this a bit more in gdb. I don't really know the code well,
but it seems like whatever is happening is happening inside gmime. On
the other hand both Fedora32 and my current Debian testing are running
libgmime 3.2.7 and gpgme 1.13
Looking at the sigstatus output, I think it is just a transcription of
what gmime returns.
"encstatus": [
{
"status": "good"
}
],
"sigstatus": [
{
"status": "error",
"keyid": "6D92612D94E46381",
"errors": {
"key-missing": true
}
}
],
I did notice that node->decrypt_success ends up being true, so it
suggests maybe bad reporting by gmime-on-fedora.
___
notmuch mailing list
notmuch@notmuchmail.org
https://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] completion: remove "setup" from the list of possible completions
On Sat, Jun 20 2020, reto@labrat.space wrote: > On Fri, Jun 19, 2020 at 12:40:49PM +0200, Łukasz Stelmach wrote: >> Having "setup" in the set requires entering three instad of two characters >> for "search". Since "setup" is rearly used it makes little sense to have >> it in the set and cripple UX for much more frequently used "search". > > I very much disagree with this patch. > The completions should contain all possible values, saving a single keystroke > is > certainly not a valid reason to remove a valid option from the completions. I disagree your disagreement, and would.be very much favorable to this change. imo.the completions should primarily provide convenience to the interactive user, to see all possible options (also those seldomly.used) one can use help and namual pages... Tomi > > Writeuu an alias into your bashrc if that bothers you so much... Then you > can save > much more keystrokes. > ___ > notmuch mailing list > notmuch@notmuchmail.org > https://notmuchmail.org/mailman/listinfo/notmuch ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
Re: [PATCH] completion: remove "setup" from the list of possible completions
On Fri, Jun 19, 2020 at 12:40:49PM +0200, Łukasz Stelmach wrote: > Having "setup" in the set requires entering three instad of two characters > for "search". Since "setup" is rearly used it makes little sense to have > it in the set and cripple UX for much more frequently used "search". I very much disagree with this patch. The completions should contain all possible values, saving a single keystroke is certainly not a valid reason to remove a valid option from the completions. Write an alias into your bashrc if that bothers you so much... Then you can save much more keystrokes. ___ notmuch mailing list notmuch@notmuchmail.org https://notmuchmail.org/mailman/listinfo/notmuch
