From: "Lawrence Velázquez" <firstname.lastname@example.org>
To: "Ray Andrews" <email@example.com>
Subject: Re: key binding not working
Date: Mon, 26 Sep 2022 00:01:31 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On Sun, Sep 25, 2022, at 11:15 PM, Ray Andrews wrote:
> On 2022-09-25 18:58, Lawrence Velázquez wrote:
>> The first command runs a NO_RCS shell and then sources /root/.zshrc
>> *in the calling shell, after the NO_RCS shell exits*. It is not
>> analogous to the second command at all.
> Thanks. I'll find out what NO_RCS is. I thought 'zsh -f' was 'a clean'
> startup, nothing sourced at all.
Not quite; the global zshenv (/etc/zshenv by default) is always run.
> Then I could just feed it the scripts that I choose.
Regardless of what type of shell you launch, the command you suggested
earlier does not do that. Running
executes 'cmd1' and then executes 'cmd2' after 'cmd1' has exited.
This is basic shell behavior that is not affected by whether 'cmd1'
is 'zsh -f' or anything else (alias shenanigans aside).
next prev parent reply other threads:[~2022-09-26 4:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 21:14 Ray Andrews
2022-09-25 22:31 ` Bart Schaefer
2022-09-25 22:46 ` Ray Andrews
2022-09-25 23:14 ` Ray Andrews
2022-09-26 3:48 ` Marc Chantreux
2022-09-27 0:30 ` zkbd (was Re: key binding not working) Bart Schaefer
2022-09-27 1:39 ` Ray Andrews
2022-09-26 1:16 ` key binding not working Ray Andrews
2022-09-26 1:58 ` Lawrence Velázquez
2022-09-26 3:15 ` Ray Andrews
2022-09-26 4:01 ` Lawrence Velázquez [this message]
2022-09-26 6:28 ` Roman Perepelitsa
2022-09-26 13:59 ` key binding not working [SOLVED] Ray Andrews
2022-09-26 18:04 ` Ray Andrews
2022-09-26 18:13 ` Roman Perepelitsa
2022-09-26 19:12 ` Peter Stephenson
2022-09-26 19:43 ` Mikael Magnusson
2022-09-26 21:31 ` Ray Andrews
2022-09-26 22:27 ` Vin Shelton
2022-09-26 22:35 ` Ray Andrews
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).