unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Lukasz Stelmach <l.stelmach@samsung.com>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] completion: remove "setup" from the list of possible completions
Date: Mon, 22 Jun 2020 12:22:50 +0200	[thread overview]
Message-ID: <dleftjv9jjiemd.fsf%l.stelmach@samsung.com> (raw)
In-Reply-To: <20200620105310.6ttlssp6rv6bqm2u@feather.localdomain> (Reto's message of "Sat, 20 Jun 2020 12:53:10 +0200")


[-- Attachment #1.1: Type: text/plain, Size: 1020 bytes --]

It was <2020-06-20 sob 12:53>, when Reto 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.
>
> Write an alias into your bashrc if that bothers you so much... Then you can save
> much more keystrokes.

I already have several aliases covering most of my use cases, however, I
still use "notmuch search" from time to time and I came to a conclusion
expressed in this patch. Of course, as a random user, I can only suggest
and by no means insist on applying it.

Kind regards,
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  parent reply	other threads:[~2020-06-22 21:31 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 ` [PATCH] completion: remove "setup" from the list of possible completions Łukasz Stelmach
2020-06-20 10:53   ` 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 [this message]
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=dleftjv9jjiemd.fsf%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).