zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Marlon <marlon.richert@gmail.com>
Cc: Mikael Magnusson <mikachu@gmail.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Rewrite of zsh-newuser-install (Mikael's subthread)
Date: Wed, 7 Apr 2021 09:36:46 -0700	[thread overview]
Message-ID: <CAH+w=7aq0ttu_6Utc-CmEHOKBsfbdaQH3GOiYqVedrVteigv7Q@mail.gmail.com> (raw)
In-Reply-To: <E9B97A4D-3406-449E-86FD-6CC5DFC21935@gmail.com>

On Wed, Apr 7, 2021 at 7:29 AM Marlon <marlon.richert@gmail.com> wrote:
>
> [...] that’s why I added Backtab to do what, since that actually doesn’t have any function by default [...]

It doesn't have a function because (formerly, at least) a lot of
keyboards didn't recognize Shift-Tab as different from Tab.

> Sadly, without using _generic, it’s not possible to enable or disable menu selection on an individual widget basis.

zstyle -e ':completion::*:default' menu \
  '[[ $WIDGET = (|reverse-)menu-complete ]] && reply=(yes select interactive)'

> >> # On startup, initialize dir stack from file.
> >
> > Does this start zsh in some other directory than it inherited from the
> > terminal? If so, nak from me on that, way too surprising.
>
> It makes the shell pick up in the same dir as where you left off last time. I would hardly call that surprising. In fact, I would pretty much call that _expected_ for most applications nowadays.

That would drive me insane unless the directory were somehow bound to
the window position (which we've already debated and concluded is
impossible in all but some very specific circumstances).  I definitely
DO NOT want every new shell starting in whatever directory I last had
a shell in, particularly for remote shells.   A shell is not like
"most applications".


  parent reply	other threads:[~2021-04-07 16:37 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 [this message]
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
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='CAH+w=7aq0ttu_6Utc-CmEHOKBsfbdaQH3GOiYqVedrVteigv7Q@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=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).