unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Łukasz Stelmach" <l.stelmach@samsung.com>
To: notmuch@notmuchmail.org
Cc: "Łukasz Stelmach" <l.stelmach@samsung.com>
Subject: [PATCH] completion: remove "setup" from the list of possible completions
Date: Fri, 19 Jun 2020 12:40:49 +0200	[thread overview]
Message-ID: <20200619104049.8028-1-l.stelmach@samsung.com> (raw)
In-Reply-To: CGME20200619104051eucas1p1d5d63105518817bc80b55cfc9158ce2f@eucas1p1.samsung.com

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".
---
 completion/notmuch-completion.bash | 2 +-
 completion/zsh/_notmuch            | 1 -
 2 files changed, 1 insertion(+), 2 deletions(-)

diff --git a/completion/notmuch-completion.bash b/completion/notmuch-completion.bash
index 15425697..c3654a73 100644
--- a/completion/notmuch-completion.bash
+++ b/completion/notmuch-completion.bash
@@ -579,7 +579,7 @@ _notmuch_tag()
 
 _notmuch()
 {
-    local _notmuch_commands="compact config count dump help insert new reply restore reindex search address setup show tag emacs-mua"
+    local _notmuch_commands="compact config count dump help insert new reply restore reindex search address show tag emacs-mua"
     local arg cur prev words cword split
 
     # require bash-completion with _init_completion
diff --git a/completion/zsh/_notmuch b/completion/zsh/_notmuch
index e920f10b..6c0344cc 100644
--- a/completion/zsh/_notmuch
+++ b/completion/zsh/_notmuch
@@ -7,7 +7,6 @@ _notmuch_command() {
   local -a notmuch_commands
   notmuch_commands=(
     'help:display documentation for a subcommand'
-    'setup:interactively configure notmuch'
 
     'address:output addresses from matching messages'
     'compact:compact the notmuch database'
-- 
2.26.2

       reply	other threads:[~2020-06-19 17:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200619104051eucas1p1d5d63105518817bc80b55cfc9158ce2f@eucas1p1.samsung.com>
2020-06-19 10:40 ` Łukasz Stelmach [this message]
2020-06-20 10:53   ` [PATCH] completion: remove "setup" from the list of possible completions Reto
2020-06-20 14:04     ` Tomi Ollila
2020-06-20 19:09       ` Ralph Seichter
2020-06-23 21:04         ` Tomi Ollila
2020-06-23 22:46           ` Ralph Seichter
     [not found]     ` <CGME20200622102303eucas1p2121610b68b1d23705237632706cb06ab@eucas1p2.samsung.com>
2020-06-22 10:22       ` Lukasz Stelmach
2020-06-24 11:44         ` Peter Wang
2020-07-02 19:55           ` Daniel Kahn Gillmor
     [not found]             ` <CGME20200708151938eucas1p26c111da083d7e8248f6d59593ed40fa7@eucas1p2.samsung.com>
2020-07-08 15:19               ` Lukasz Stelmach
2021-06-05 11:42             ` David Bremner
2021-06-05 13:59             ` Felipe Contreras

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=20200619104049.8028-1-l.stelmach@samsung.com \
    --to=l.stelmach@samsung.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).