From: Carlos Carvalho <carlos@snfep1.if.usp.br>
To: zsh-workers@math.gatech.edu
Subject: Re: global zlogout and .zlogout
Date: Wed, 18 Oct 1995 16:54:08 -0200 [thread overview]
Message-ID: <199510181854.QAA00335@snfep1.if.usp.br> (raw)
In-Reply-To: <9510180559.AA25070@redwood.skiles.gatech.edu>
Richard Coleman (coleman@math.gatech.edu) wrote on 18 October 1995 01:59:
>> > I've just grabed Zoltan's release, after MANY trials :-( Without
>> > ncftp's nifty appending get I wouldn't have managed...
>> >
>> > I noticed that the global zlogout is not sourced if NORCS is set. I
>> > think this is wrong, it should always be executed, just like the
>> > global zshenv.
>I'm want to know what everyone this is the most usual behavoir.
Is this a local dialect? :-)
>Currently in the zsh baseline, the global zlogout is only
>executed for a login shell if NO_RCS is not set and the shell is
>interactive. This is definitely wrong. My first reaction is to have
>the global zlogout always executed (regardless of NO_RCS) when a login
>shell is exiting.
This is exactly what I said above.
>This is the way the global zlogin file is handled.
No, because you can set NO_RCS in your .zshenv. That's why I say above
"just like the global zshenv", which is the only one that's always
executed.
Anyway, we agree on zlogout.
>Also, I now realize another potential problem. When the init scripts
>are sourced when the shell is starting up, there is a hack (setting the
>sourcelevel to 32768) that prevents an error in these scripts from tripping
>ERREXIT. This same should probably apply to the global zlogout and .zlogout.
Only to the global one. The user's one is his problem.
Carlos
next prev parent reply other threads:[~1995-10-18 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-09-06 15:52 global zlogout Carlos Carvalho
1995-09-06 16:37 ` Zoltan Hidvegi
1995-10-18 5:59 ` global zlogout and .zlogout Richard Coleman
1995-10-18 18:54 ` Carlos Carvalho [this message]
1995-10-18 19:28 ` Richard Coleman
1995-10-20 18:50 ` Zoltan Hidvegi
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=199510181854.QAA00335@snfep1.if.usp.br \
--to=carlos@snfep1.if.usp.br \
--cc=zsh-workers@math.gatech.edu \
/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).