zsh-workers
 help / color / mirror / code / Atom feed
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Cc: 844710@bugs.debian.org
Subject: Re: Bug#844710: Fwd: Re: [Pkg-zsh-devel] Bug#844710: autocorrection suggested rm for typing mr without typing "y"
Date: Sat, 19 Nov 2016 21:54:05 +0000	[thread overview]
Message-ID: <20161119215405.GA24755@fujitsu.shahaf.local2> (raw)
In-Reply-To: <161119100023.ZM13994@torch.brasslantern.com>

Bart Schaefer wrote on Sat, Nov 19, 2016 at 10:00:23 -0800:
> On Nov 19,  7:55am, Daniel Shahaf wrote:
> } Subject: Re: Bug#844710: Fwd: Re: [Pkg-zsh-devel] Bug#844710: autocorrecti
> }
> } Martin Steigerwald wrote on Fri, Nov 18, 2016 at 14:15:51 +0100:
> } > So two fixes to consider:
> } > 
> } > 1) Don't confirm on space, as thats to easy to trigger accidentally. :)
> } 
> } The code confirms on both tabs (since commit 7f1ce570) and spaces (since
> } before CVS).  Does anyone know a reason for doing this?
> 
> If you have a look at the zsh-workers article referenced by 7f1ce570,
> you'll see that both space and tab date from time immemorial; the patch
> in 7f1ce570 actually REMOVES the interpretation of tab as "yes" from
> the NO_RM_STAR_SILENT option, it didn't change CORRECT handling.
> 

I had looked at it, but missummarized it.  Mea culpa.

> Why it's this way probably has more to do with Paul Falstad's typing
> habits than anything else.  If you're used to hitting space or tab at
> a completion, and most of the time you believe the correction, then
> you probably want space and tab to mean "go ahead" anytime the shell
> is waiting for something.
> 
> Notice the RM_STAR_WAIT option for a similar situation.
> 
> While I don't use CORRECT and therefore personally don't much care
> what this prompt does, I question whether one person remarking about
> this after 25+ years of it being the way it has been, is a sufficient
> reason for us to immediately change it.

I didn't write the patch because a guy on the internet suggested it.
I wrote the patch because the semantics of tab and space at that point
are undocumented and I had been convinced by the argument that using
space to accept a correction violates the principle of least surprise.

If we do keep space and tab then we should document them.  

Daniel


  reply	other threads:[~2016-11-19 22:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-18 13:15 Martin Steigerwald
2016-11-19  7:55 ` Bug#844710: " Daniel Shahaf
2016-11-19 11:27   ` Martin Steigerwald
2016-11-19 11:46     ` Frank Terbeck
2016-11-19 12:21       ` Daniel Shahaf
2016-11-19 18:00   ` Bart Schaefer
2016-11-19 21:54     ` Daniel Shahaf [this message]
2016-11-20 19:22       ` Peter Stephenson

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161119215405.GA24755@fujitsu.shahaf.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=844710@bugs.debian.org \
    --cc=zsh-workers@zsh.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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).