zsh-users
 help / color / mirror / code / Atom feed
* what does 'interactive' mean?
@ 2021-08-10  2:58 Roman Neuhauser
  2021-08-10  9:04 ` Thomas Paulsen
  2021-08-10 12:12 ` Peter Stephenson
  0 siblings, 2 replies; 16+ messages in thread
From: Roman Neuhauser @ 2021-08-10  2:58 UTC (permalink / raw)
  To: zsh-users

hello,

i was looking for a way to start zsh with an ad-hoc initialization
file: the shell would would source the file (instead of or after the
usual startup files, does not matter right now) and drop into the
ZLE.  if there's a way i haven't found it, but whatever: i'm here to
complain that the manual never defines "interactive shell".
(solutions to my original problem are welcome too.)

i started from zsh(1):

  -i Force shell to be interactive.  It is still possible to specify
     a script to execute.

noting how it says "execute" as opposed to "read commands from" or
"source" i didn't really expect "zsh -i script" to do what i needed
but, as a naive user equipped with the common-use understanding of
"interactive shell" supported by zsh(1) itself ("Zsh is a UNIX
command interpreter (shell) usable as an interactive login shell"
-- that's the informal use right there), i definitely expected to
get the prompt.  well i wouldn't be here if it worked that way...

so what *is* an "interactive shell"?


here's a few notes about my path through the manual tonight.

zshzle(1) and zshoptions(1) use two different vocabularies to
describe one thing, that's something to avoid.  define your terms
and stick to them!

  DESCRIPTION
    If the ZLE option is set (which it is by default in interactive
    shells) and the shell input is attached to the terminal, the
    user is able to edit command lines.

the description of INTERACTIVE in zshoptions(1) contains
*no mention of its effects*!

  INTERACTIVE (-i, ksh: -i)
    This is an interactive shell.  This option is set upon
    initialisation if the standard input is a tty and commands are
    being read from standard input.  (See the discussion of
    SHIN_STDIN.) This heuristic may be overridden by specifying a
    state for this option on the command line.  The value of this
    option can only be changed via flags supplied at invocation of
    the shell.  It cannot be changed once zsh is running.

  SHIN_STDIN (-s, ksh: -s)
    Commands are being read from the standard input.  Commands are
    read from standard input if no command is specified with -c and
    no file of commands is specified.  If SHIN_STDIN is set [...]

  ZLE (-Z)
    Use the zsh line editor.  Set by default in interactive shells
    connected to a terminal.

as you can see in the snippets below, -i implies -Z *even when stdin
is /dev/null!* which is not what the docs seem to say, and the
independence of ZLE option from ZLE repl is far from obvious.


% :>|s
% zsh -fi s; echo NOPE
NOPE

% cat >|s <<\EOF
> [[ -t 0 ]] && echo input is from terminal
> set -o > >(grep -w -e zle)
> EOF
% zsh -fi s
input is from terminal
zle                   on
% zsh -fi s </dev/null
zle                   on

% cat >|s <<\EOF
> [[ -t 0 ]] && echo input is from terminal
> set -o > >(grep -w -e interactive -e shinstdin -e zle)
> EOF
% zsh -fi s
input is from terminal
interactive           on
shinstdin             off
zle                   on

-- 
roman


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10  2:58 what does 'interactive' mean? Roman Neuhauser
@ 2021-08-10  9:04 ` Thomas Paulsen
  2021-08-10 13:00   ` Roman Neuhauser
  2021-08-10 12:12 ` Peter Stephenson
  1 sibling, 1 reply; 16+ messages in thread
From: Thomas Paulsen @ 2021-08-10  9:04 UTC (permalink / raw)
  To: Roman Neuhauser; +Cc: zsh-users

Hi, 

what *is* an "interactive shell"?
see: https://tldp.org/LDP/abs/html/intandnonint.html




^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10  2:58 what does 'interactive' mean? Roman Neuhauser
  2021-08-10  9:04 ` Thomas Paulsen
@ 2021-08-10 12:12 ` Peter Stephenson
  2021-08-10 13:47   ` Roman Neuhauser
  2021-08-10 15:30   ` Ray Andrews
  1 sibling, 2 replies; 16+ messages in thread
From: Peter Stephenson @ 2021-08-10 12:12 UTC (permalink / raw)
  To: Roman Neuhauser, zsh-users

> On 10 August 2021 at 03:58 Roman Neuhauser <neuhauser@sigpipe.cz> wrote:
> the description of INTERACTIVE in zshoptions(1) contains
> *no mention of its effects*!
> 
>   INTERACTIVE (-i, ksh: -i)
>     This is an interactive shell.  This option is set upon
>     initialisation if the standard input is a tty and commands are
>     being read from standard input.  (See the discussion of
>     SHIN_STDIN.) This heuristic may be overridden by specifying a
>     state for this option on the command line.  The value of this
>     option can only be changed via flags supplied at invocation of
>     the shell.  It cannot be changed once zsh is running.

As you say, the documentation is confusing.  What it's trying to say,
but not making a good job of, is that basically the conditions
here (tty on STDIN with commands coming from it, which cause the
INTERACTIVE option to be set) define an interactive shell --- the
option is the consequence, not the cause.  But then you can
actually force the option on or off (sometimes that's even useful),
so that's just a test by default.

I suppose that paragraph really needs dividing into a bit
(that doesn't necessarily belong here) that explains the logic
the shell uses to decide if it's interactive if you don't override
it, and then this bit saying how the option behaves.

The shell tests the option internally in a great number of places
to see if it's appropriate to output prompts, use the line editor,
etc. etc.  Mostly this is mentioned in the manual, but only
with something like "if the shell is interactive..."
This becomes more useful if you know it's testing the
option when that happens, so somewhere we need a sentence along
the lines of "where the shell needs to decide if it is
interactive at run time, it tests the state of the INTERACTIVE shell
option.  See XXXX for information on this".

In summary, the information to get across in some form is the following:

- At run time the shell tests the option INTERACTIVE to decide if it is
interactive.  This is to be understood anywhere in the manual where
"an interactive shell" is mentioned.
- This option may be set or unset at shell initialisation by passing
appropriate options in the command line that invokes the shell.
- If the option is not explicitly set or unset in this way, it is
initialised to "set" if standard input is a terminal and is being used
for command input, and to "unset" otherwise.
- The option may not be altered after shell initialisation.

Of course, there may still be something I'm missing.

pws


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10  9:04 ` Thomas Paulsen
@ 2021-08-10 13:00   ` Roman Neuhauser
  0 siblings, 0 replies; 16+ messages in thread
From: Roman Neuhauser @ 2021-08-10 13:00 UTC (permalink / raw)
  To: Thomas Paulsen; +Cc: zsh-users

# 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


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  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
  1 sibling, 1 reply; 16+ messages in thread
From: Roman Neuhauser @ 2021-08-10 13:47 UTC (permalink / raw)
  To: Peter Stephenson; +Cc: zsh-users

# p.w.stephenson@ntlworld.com / 2021-08-10 13:12:02 +0100:
> > On 10 August 2021 at 03:58 Roman Neuhauser <neuhauser@sigpipe.cz> wrote:
> > the description of INTERACTIVE in zshoptions(1) contains
> > *no mention of its effects*!
> > 
> >   INTERACTIVE (-i, ksh: -i)
> >     This is an interactive shell.  This option is set upon
> >     initialisation if the standard input is a tty and commands are
> >     being read from standard input.  (See the discussion of
> >     SHIN_STDIN.) This heuristic may be overridden by specifying a
> >     state for this option on the command line.  The value of this
> >     option can only be changed via flags supplied at invocation of
> >     the shell.  It cannot be changed once zsh is running.
> 
> As you say, the documentation is confusing.  What it's trying to say,
> but not making a good job of, is that basically the conditions
> here (tty on STDIN with commands coming from it, which cause the
> INTERACTIVE option to be set) define an interactive shell

you're on the right track here.  one thing i tried to convey was
that the manual overloads the meaning of "interactive shell"
(the colloquial use in the blurb vs. the should-be-precise technical
one basically everywhere else), and that "interactive shell" is too
entrenched as an informal coin to be useful in a technical reference,
that ship has sailed.

with that in mind, i don't think the proposed definition is useful,
or rather, the conditions should be called something other than
"interactive shell" because that is usually understood to include
some kind of online editing facility a la ZLE.  you could strip
zsh down so much its interactive mode would behave like '>>(zsh)'
and it would still fit the definition you offered here.
nobody would accept that as an "interactive login shell".

i think we already have a name for that set of conditions, it's
called "the INTERACTIVE option is set"!

> The shell tests the option internally in a great number of places
> to see if it's appropriate to output prompts, use the line editor,
> etc. etc.  Mostly this is mentioned in the manual, but only
> with something like "if the shell is interactive..."
> This becomes more useful if you know it's testing the
> option when that happens, so somewhere we need a sentence along
> the lines of "where the shell needs to decide if it is
> interactive at run time, it tests the state of the INTERACTIVE shell
> option.  See XXXX for information on this".

i disagree, this is an unnecessary indirection.  i propose

  s/if the shell is interactive/if the INTERACTIVE option is set/g

it's longer by a negligible margin and needs no further cross-reference.

aaand then there's the smaller fish i mentioned, like the text about
the ZLE option being misleading at the very least.  i'll get back to
you later about that.

while i love back-seat driving this is not meant that way.
i'd like to have a patch for this ready by the weekend and then
continue with other parts of the manual that in my opinion don't work
as well as they should and could.  there'll be no ambushes though,
you can always expect a rant first so we can discuss the issue and
see where we meet.

-- 
roman


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 13:47   ` Roman Neuhauser
@ 2021-08-10 13:54     ` Peter Stephenson
  0 siblings, 0 replies; 16+ messages in thread
From: Peter Stephenson @ 2021-08-10 13:54 UTC (permalink / raw)
  To: zsh-users

> On 10 August 2021 at 14:47 Roman Neuhauser <neuhauser@sigpipe.cz> wrote:
> i disagree, this is an unnecessary indirection.  i propose
> 
>   s/if the shell is interactive/if the INTERACTIVE option is set/g
> 
> it's longer by a negligible margin and needs no further cross-reference.

You're right, that's perfectly reasonable.

pws


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 12:12 ` Peter Stephenson
  2021-08-10 13:47   ` Roman Neuhauser
@ 2021-08-10 15:30   ` Ray Andrews
  2021-08-10 16:34     ` Peter Stephenson
  1 sibling, 1 reply; 16+ messages in thread
From: Ray Andrews @ 2021-08-10 15:30 UTC (permalink / raw)
  To: zsh-users

On 2021-08-10 5:12 a.m., Peter Stephenson wrote:
>
> Of course, there may still be something I'm missing.

I had my panic attack the first time I came across this 'interactive' 
business  and like Thomas I was at a loss to figure out what this came 
down to in practice.  Naturally some scripts don't ask for input and 
some do, but it seemed to me that -- well, if they do they do and if 
they don't they don't but why do I have to 'set' anything?  What do I 
break if I get it wrong?

" to see if it's appropriate to output prompts, use the line editor,
etc. etc. "

There's the start of an answer.  But if I put a 'read' or an 'echo' in my script, then surely it must be interactive?  It just is.  How could that be made non interactive?  I remember just deciding to ignore INTERACTIVE and hope for the best and AFAICT it never bothered me not knowing.  My scripts and functions interact whenever I ask them to.  What would it mean if I asked them not to interact?  Dunno, I now sorta get the idea that before my prompt shows up, I might be asking zsh to do all sorts of setup stuff in the background and I don't want a prompt from that stuff so by commanding it to be non interactive I leave my interactive prompt alone.  Sorta?  interactive ~= background?

  





^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 15:30   ` Ray Andrews
@ 2021-08-10 16:34     ` Peter Stephenson
  2021-08-10 16:48       ` Ray Andrews
  0 siblings, 1 reply; 16+ messages in thread
From: Peter Stephenson @ 2021-08-10 16:34 UTC (permalink / raw)
  To: zsh-users

> On 10 August 2021 at 16:30 Ray Andrews <rayandrews@eastlink.ca> wrote:
> Sorta?  interactive ~= background?

Very very very very very roughly, "interactive" in this sense means it's
showing you prompts and bringing up a line editor to edit the command line.
(To be less rough, go back to Roman's original question, but I think we're
off at a tangent here.)

Being "non-interactive" doesn't mean you can't interact with the shell.
There's still probably a standard input and output.  It just means it's not
giving you the bit of extra help you get at a terminal to make things easy.
Well, not necessarily easy, but...

pws


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 16:34     ` Peter Stephenson
@ 2021-08-10 16:48       ` Ray Andrews
  2021-08-10 19:00         ` Bart Schaefer
  2021-08-10 19:30         ` Lawrence Velázquez
  0 siblings, 2 replies; 16+ messages in thread
From: Ray Andrews @ 2021-08-10 16:48 UTC (permalink / raw)
  To: zsh-users

On 2021-08-10 9:34 a.m., Peter Stephenson wrote:
>
> Very very very very very roughly, "interactive" in this sense means it's
> showing you prompts and bringing up a line editor to edit the command line.
>
Well that's the thing.  Thomas can be forgiven for being a bit unclear 
about what it all means.  The docs basically assume you already know.  
But that's very roughly how I understand it -- no prompts if not 
interactive.
> Being "non-interactive" doesn't mean you can't interact with the shell.
> There's still probably a standard input and output.
Just when I thought I understood it :-(  So 'non-interactive' might be 
interactive after all?  It would take some writing skill to really 
elucidate this.




^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  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
  1 sibling, 1 reply; 16+ messages in thread
From: Bart Schaefer @ 2021-08-10 19:00 UTC (permalink / raw)
  To: Ray Andrews; +Cc: Zsh Users

On Tue, Aug 10, 2021 at 9:48 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> Just when I thought I understood it :-(  So 'non-interactive' might be
> interactive after all?  It would take some writing skill to really
> elucidate this.

You're WAY over-thinking this.

Computer operations are called "interactive" when they in some way
respond to user input, be that via keyboard, mouse, voice command,
electrodes on the skull, etc. as part of normal operation.

A shell is a command interpreter.  When the shell is described as
"interactive", that is intended to mean that the interpreter itself
responds to user input, for example by printing a prompt and waiting
in between interpreted commands or when a command is incomplete.
That's distinct from any of the commands executed BY the interpreter
doing something similar; that is, just because you can write a script
that invokes the "read" builtin with consequentially a prompt and a
wait for input, doesn't make the interpreter interactive, it just
makes your script interactive.

There are two ways this can get muddied:
(1)  Shell options such as INTERACTIVE and SHIN_STDIN can be forced on
at the command line, which may cause the interpreter to behave AS IF
it is receiving user input even when it is not.
(2) The design of the file descriptor system is such that a device
that interacts with the user can be substituted for almost any other
input, so the interpreter can be caused to receive user input even
when it does not "expect" to behave in an interactive manner.
"Interactions" such as exiting on a keyboard interrupt are a special
case of this: it's not the shell but instead the interactive device
(terminal) that receives the keyboard input, and translates it into a
signal which is delivered by the operating system.  This does NOT make
for an "interactive shell".

Roman is making an effort to quash the documentary imprecision when
describing the cases in which the interpreter behaves (or not) as if
it is receiving user input (no matter whether it actually is, or it
has been forced into that behavior).  There's really no useful way to
explain (2) within the documentation of the shell.


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 16:48       ` Ray Andrews
  2021-08-10 19:00         ` Bart Schaefer
@ 2021-08-10 19:30         ` Lawrence Velázquez
  2021-08-10 22:38           ` Ray Andrews
  1 sibling, 1 reply; 16+ messages in thread
From: Lawrence Velázquez @ 2021-08-10 19:30 UTC (permalink / raw)
  To: zsh-users

On Tue, Aug 10, 2021, at 12:48 PM, Ray Andrews wrote:
> On 2021-08-10 9:34 a.m., Peter Stephenson wrote:
> >
> > Very very very very very roughly, "interactive" in this sense means it's
> > showing you prompts and bringing up a line editor to edit the command line.
> >
> Well that's the thing.  Thomas can be forgiven for being a bit unclear 
> about what it all means.  The docs basically assume you already know.  
> But that's very roughly how I understand it -- no prompts if not 
> interactive.
> > Being "non-interactive" doesn't mean you can't interact with the shell.
> > There's still probably a standard input and output.
> Just when I thought I understood it :-(  So 'non-interactive' might be 
> interactive after all?  It would take some writing skill to really 
> elucidate this.

While I empathize with the desire to concisely define terms like
"interactive shell", I've always found that approach unhelpful,
both practically and pedagogically.  Same with "login shell".  In
a very real sense, a shell is an interactive shell and/or a login
shell if it thinks it is.  The important things are how the shell
comes to think that and how it consequently changes its behavior.
The former is described in zshoptions(1) and a little in zsh(1).
The latter is distributed throughout the documentation because
there's a great deal of behavior to describe.

(Even POSIX doesn't rigorously define "interactive shell" [*].)

I understand that this approach might be intellectually unsatisfying,
but it avoids ontological hangups.  Rather than thinking very hard
about what "interactive" means, ask "how does [behavior X] change
in an interactive shell?"

  [*]: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_198

-- 
vq


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 19:00         ` Bart Schaefer
@ 2021-08-10 22:33           ` Ray Andrews
  0 siblings, 0 replies; 16+ messages in thread
From: Ray Andrews @ 2021-08-10 22:33 UTC (permalink / raw)
  To: zsh-users

On 2021-08-10 12:00 p.m., Bart Schaefer wrote:
> On Tue, Aug 10, 2021 at 9:48 AM Ray Andrews <rayandrews@eastlink.ca> wrote:
>>
>> You're WAY over-thinking this.
>>
>>
>> Roman is making an effort to quash the documentary imprecision when
>> describing the cases in which the interpreter behaves (or not) as if
>> it is receiving user input (no matter whether it actually is, or it
>> has been forced into that behavior).  There's really no useful way to
>> explain (2) within the documentation of the shell.
All I can say is that I wish him luck.  As I said, I myself have never 
noticed that I need anything to do with this issue, I just wanted to 
back Thomas up in terms of not being clear about it.  It would seem to 
be anything but simple. Nuff said.




^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 19:30         ` Lawrence Velázquez
@ 2021-08-10 22:38           ` Ray Andrews
  2021-08-10 23:08             ` Bart Schaefer
  0 siblings, 1 reply; 16+ messages in thread
From: Ray Andrews @ 2021-08-10 22:38 UTC (permalink / raw)
  To: zsh-users

On 2021-08-10 12:30 p.m., Lawrence Velázquez wrote:
>  Rather than thinking very hard
> about what "interactive" means, ask "how does [behavior X] change
> in an interactive shell?"
>
>
Exactly.  The only thing I'd  even want to know is how when where and 
why I'd ever want to get involved with the issue with very practical 
examples.  Definitions are often fraught.



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 22:38           ` Ray Andrews
@ 2021-08-10 23:08             ` Bart Schaefer
  2021-08-10 23:26               ` Ray Andrews
  0 siblings, 1 reply; 16+ messages in thread
From: Bart Schaefer @ 2021-08-10 23:08 UTC (permalink / raw)
  To: Ray Andrews; +Cc: Zsh Users

On Tue, Aug 10, 2021 at 3:38 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> The only thing I'd  even want to know is how when where and
> why I'd ever want to get involved with the issue with very practical
> examples.

There are only two reasons I can think of why you would care:
(1a) The /etc/zshenv file is read in all shells, and you're a system
administrator who wants to do (or not do) something only in shells
that are also (or are not) going to read the zshrc files.  The classic
example would be some adjustment to $PATH.
(1b) You're a user with the same go/no-go concern about something in
your .zshenv file.
(2) As (1ab) except for zlogin/zlogout files (yes, there are
circumstances in which a login shell might not be interactive, mostly
with remote shells).  The example here would be to modify any of the
history-related variables.

I suppose a third case would be that you're intending to forcibly
create one of the foregoing circumstances by turning the INTERACTIVE
option explicitly on or off.  Examples of why you're doing that would
be pretty obscure.


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 23:08             ` Bart Schaefer
@ 2021-08-10 23:26               ` Ray Andrews
  2021-08-10 23:30                 ` Bart Schaefer
  0 siblings, 1 reply; 16+ messages in thread
From: Ray Andrews @ 2021-08-10 23:26 UTC (permalink / raw)
  To: zsh-users

On 2021-08-10 4:08 p.m., Bart Schaefer wrote:
> On Tue, Aug 10, 2021 at 3:38 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>>   to do (or not do) something only in shells
>> that are also (or are not) going to read the zshrc files
Curious:  I know there's quite a hierarchy of config files and several 
might be involved.  If one had some problem to diagnose, is there some 
way of asking the shell to document all the files it's executed while 
firing up?



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: what does 'interactive' mean?
  2021-08-10 23:26               ` Ray Andrews
@ 2021-08-10 23:30                 ` Bart Schaefer
  0 siblings, 0 replies; 16+ messages in thread
From: Bart Schaefer @ 2021-08-10 23:30 UTC (permalink / raw)
  To: Ray Andrews; +Cc: Zsh Users

On Tue, Aug 10, 2021 at 4:26 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> asking the shell to document all the files it's executed while
> firing up?

zsh -o sourcetrace


^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~2021-08-10 23:31 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-10  2:58 what does 'interactive' mean? Roman Neuhauser
2021-08-10  9:04 ` Thomas Paulsen
2021-08-10 13:00   ` Roman Neuhauser
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

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).