From: Ralph Seichter <ralph@ml.seichter.de>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] completion: remove "setup" from the list of possible completions
Date: Sat, 20 Jun 2020 21:09:24 +0200 [thread overview]
Message-ID: <87a70xzh97.fsf@wedjat.horus-it.com> (raw)
In-Reply-To: <m21rm9j0js.fsf@guru.guru-group.fi>
* 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
next prev parent reply other threads:[~2020-06-20 19:18 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 [this message]
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=87a70xzh97.fsf@wedjat.horus-it.com \
--to=ralph@ml.seichter.de \
--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).