zsh-workers
 help / color / mirror / code / Atom feed
From: Marlon <marlon.richert@gmail.com>
To: Mikael Magnusson <mikachu@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Rewrite of zsh-newuser-install (Mikael's subthread)
Date: Fri, 9 Apr 2021 23:07:10 +0300	[thread overview]
Message-ID: <F9A77ABF-D672-40F4-90DC-985DE26D1A90@gmail.com> (raw)
In-Reply-To: <CAHYJk3RUX6MyFB7o2WFE=P0-=QQ=gv49Z3VTyu+9Zm9fzmoB4A@mail.gmail.com>


> On 7 Apr 2021, at 21:15, Mikael Magnusson <mikachu@gmail.com> wrote:
> You could also just have a comment saying something to the effect of
> "changes to this file will only take effect in new shells, you can
> either open a new terminal or type "zsh" in an existing terminal". I
> guess I don't care too much either way after all.

The problem is that many new users have learned from OMZ and other sources that they should do `source ~/.zshrc` to apply changes. I originally had a note that said you should instead either restart your terminal or type `exec zsh`, but then Oliver & Bart came up with the current solution.


>> Personally, I would’ve preferred `setopt HIST_IGNORE_ALL_DUPS
>> SHARE_HISTORY`, but there were several votes against that earlier in this
>> thread.
> 
> I'm glad, those are even worse :).

Why? What’s so bad about those?


> tab will insert the unambiguous part, and then start cycling
> (depending on your setopts, this takes anywhere from 0 to 4 or so tab
> presses).

Nope, in `interactive` mode, it just inserts the unambiguous part and that’s it.


> Well, I'd have the same objection to either of them, that it's quite a
> huge departure from the standard mode of operation which is typing
> normally and pressing tab to complete words.

I think it’s a great feature that very people actually know about. Besides that, even when using `interactive`, you’re still typing normally and pressing Tab to complete words. It doesn’t change that. Have you tried the feature?


>>>> bindkey -M menuselect -s "$key[Backtab]" "$key[Return]$key[Tab]"
>>> 
>>> How is this different from ^[a (eg, accept-and-hold) in menu selection?
>> 
>> accept-and-hold doesn’t work correctly with, for example, directory
>> completions. To see this for yourself, try `cd /` + Tab + ^[a. Then try `cd
>> /` + Tab + Backtab. Notice the difference. The first one makes no sense.
> 
> In that particular use case I think you would use accept-and-infer-next-history.

Nope, doesn’t work either. It inserts the selection but does not advance to the next completion.




  parent reply	other threads:[~2021-04-09 20:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-05 19:44 Mikael Magnusson
2021-04-05 21:01 ` Mikael Magnusson
2021-04-05 21:44 ` Bart Schaefer
2021-04-07 13:44   ` Marlon
2021-04-07 16:24     ` Daniel Shahaf
2021-04-10 11:23       ` Marlon
2021-04-10 20:46         ` dana
2021-04-10 21:41           ` Bart Schaefer
2021-04-10 22:03             ` Roman Perepelitsa
2021-04-11 11:38               ` Marlon Richert
2021-04-13 14:49               ` Daniel Shahaf
2021-04-13 14:55           ` Daniel Shahaf
2021-04-07 14:28 ` Marlon
2021-04-07 15:14   ` Daniel Shahaf
2021-04-07 16:36   ` Bart Schaefer
2021-04-07 18:15   ` Mikael Magnusson
2021-04-07 18:50     ` Daniel Shahaf
2021-04-07 20:08     ` Arseny Maslennikov
2021-04-09 20:07     ` Marlon [this message]
2021-04-09 22:04       ` Oliver Kiddle
2021-04-09 23:04         ` Daniel Shahaf
2021-04-09 23:55           ` Bart Schaefer
2021-04-13 15:00             ` Daniel Shahaf
2021-04-09 23:08         ` Bart Schaefer
2021-04-10  7:44           ` Roman Perepelitsa
2021-04-09 23:23       ` Mikael Magnusson
2021-04-10  7:45         ` Marlon Richert
2021-04-09 15:29   ` Marlon

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=F9A77ABF-D672-40F4-90DC-985DE26D1A90@gmail.com \
    --to=marlon.richert@gmail.com \
    --cc=mikachu@gmail.com \
    --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).