From: Bart Schaefer <schaefer@brasslantern.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Rewrite of zsh-newuser-install (Mikael's subthread)
Date: Fri, 9 Apr 2021 16:08:24 -0700 [thread overview]
Message-ID: <CAH+w=7bDtE5gPONTbDzEF-0nVwt5ptkwZJy36nVsY7Mh-fKE0g@mail.gmail.com> (raw)
In-Reply-To: <85321-1618005842.162070@01py.d8bG.-OTF>
On Fri, Apr 9, 2021 at 3:04 PM Oliver Kiddle <opk@zsh.org> wrote:
>
> Marlon wrote:
> >
> > The problem is that many new users have learned from OMZ and other
> > sources that they should do `source ~/.zshrc` to apply changes.
Which is somewhat cringey for a number of out-of-scope reasons.
> > 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.
>
> Would it be better if we put the zrestart function in Functions/Misc
That doesn't address whether we should employ $- or a conditional to
find flags to pass to the restarted shell, nor does it address
Arseny's concern about a shell in the "chain" having a nonzero exit
status. (If use of the PID space is really an issue, the user is
restarting WAY too often.)
I somewhat hesitantly suggest (because I don't have a clear
implementation in mind yet) that perhaps the .zshrc should set a
variable to record that it has been run, and employ some conditional
test(s) to deal with being source'd a second+ time?
next prev parent reply other threads:[~2021-04-09 23:08 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
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 [this message]
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=7bDtE5gPONTbDzEF-0nVwt5ptkwZJy36nVsY7Mh-fKE0g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=opk@zsh.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).