From: Roman Neuhauser <neuhauser@sigpipe.cz>
To: Thomas Paulsen <thomas.paulsen@firemail.de>
Cc: zsh-users@zsh.org
Subject: Re: what does 'interactive' mean?
Date: Tue, 10 Aug 2021 15:00:21 +0200 [thread overview]
Message-ID: <YRJ4ZRJKj2fMxShd@isis.sigpipe.cz> (raw)
In-Reply-To: <7d9a64367548846adafd9c8e9fb66d63@firemail.de>
# thomas.paulsen@firemail.de / 2021-08-10 11:04:03 +0200:
> Hi,
>
> what *is* an "interactive shell"?
> see: https://tldp.org/LDP/abs/html/intandnonint.html
let's assume you read and understood my email for a bit.
the answer to "what is an interactive shell" then is
"one with the 'interactive' option set". let's ignore for
a moment that zsh -i is where the email kicks off. this is your
definition.
then you're saying that the first complete sentence in the zsh(1)
man page aka '(zsh)Introduction' info node which currently reads
Zsh is a UNIX command interpreter (shell) usable as an interactive
login shell [...]
can be replaced with
Zsh is a UNIX command interpreter (shell) usable as a login shell
in which the 'interactive' option is on
i think you'll agree that this is not true, because while everyone
knows that "interactive shell" means the REPL you get in your xterm
or whatever, while the latter carries no such connotation.
i showed in the email you replied to that -i can be freely set or
unset without any impact on the shell presenting the REPL (or not),
same goes for the [[ -t 0 ]] test which i also included in my email.
no, i don't think you read the email you replied to.
while i'm at it, the articly is so wrong it's not even wrong:
as you surely know, options set or unset in a shell have no
influence on options set or unset in a script *executed* by said
shell, the same is true for parameters (shell parameters do not
equal the environment), mutatis mutandis. here's a demonstration
in bash:
$ cat ./demo
#!/usr/bin/bash
echo $- PS1=$PS1
$ . ./demo
himBHs PS1=\$
$ ./demo
hB PS1=
the only bits in the article that make any sense are attributed to
other people including zsh's SChazelas, and clearly were included
well after the article / book was published. the author had *no
clue* about the subject matter.
you may want to reconsider paying any attention to that publication.
--
roman
next prev parent reply other threads:[~2021-08-10 13:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 2:58 Roman Neuhauser
2021-08-10 9:04 ` Thomas Paulsen
2021-08-10 13:00 ` Roman Neuhauser [this message]
2021-08-10 12:12 ` Peter Stephenson
2021-08-10 13:47 ` Roman Neuhauser
2021-08-10 13:54 ` Peter Stephenson
2021-08-10 15:30 ` Ray Andrews
2021-08-10 16:34 ` Peter Stephenson
2021-08-10 16:48 ` Ray Andrews
2021-08-10 19:00 ` Bart Schaefer
2021-08-10 22:33 ` Ray Andrews
2021-08-10 19:30 ` Lawrence Velázquez
2021-08-10 22:38 ` Ray Andrews
2021-08-10 23:08 ` Bart Schaefer
2021-08-10 23:26 ` Ray Andrews
2021-08-10 23:30 ` Bart Schaefer
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=YRJ4ZRJKj2fMxShd@isis.sigpipe.cz \
--to=neuhauser@sigpipe.cz \
--cc=thomas.paulsen@firemail.de \
--cc=zsh-users@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).