From: Tino Calancha <tino.calancha@gmail.com>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 27979@debbugs.gnu.org, Tino Calancha <tino.calancha@gmail.com>
Subject: bug#27979: tab completion for "(yes or no)?"
Date: Sun, 6 Aug 2017 22:02:39 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1708062157100.2084@calancha-pc> (raw)
In-Reply-To: <87r2won9jc.fsf@jidanni.org>
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
On Sun, 6 Aug 2017, 積丹尼 Dan Jacobson wrote:
>>>>>> "TC" == Tino Calancha <tino.calancha@gmail.com> writes:
> TC> offering TAB completion would somehow contradict this idiom.
>
> Well I discovered for a second and subsequent yes, one can just hit the up arrow.
What?? Oh noo!
> (But I hope that is not now going to be removed too, now that I revealed it.)
You should keep your secrets better :-). I already canceled the auto
completion in the recursive deletion or dirs: now the full word is
required. I must thank your this report, it opened my eyes about my
previous mistake ;-)
I really prefer that users input the full word when they are about to
run such kind of commands: commands that might destroy months-years of
someones work.
next prev parent reply other threads:[~2017-08-06 13:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-06 0:33 bug#27979: tab completion for "(yes or no)?" 積丹尼 Dan Jacobson
2017-08-06 6:59 ` Tino Calancha
2017-08-06 15:07 ` Drew Adams
2017-08-06 15:20 ` Tino Calancha
2017-08-06 15:46 ` Drew Adams
2017-08-06 16:05 ` Tino Calancha
2017-08-06 16:48 ` Drew Adams
2017-08-06 20:34 ` Drew Adams
2017-08-06 16:49 ` Eli Zaretskii
2017-08-06 12:52 ` 積丹尼 Dan Jacobson
2017-08-06 13:02 ` Tino Calancha [this message]
2017-08-06 13:59 ` Tino Calancha
2017-08-06 16:15 ` 積丹尼 Dan Jacobson
2017-08-06 17:08 ` Eli Zaretskii
2017-08-06 16:58 ` 積丹尼 Dan Jacobson
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.20.1708062157100.2084@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=27979@debbugs.gnu.org \
--cc=jidanni@jidanni.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://git.savannah.gnu.org/cgit/emacs.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).