From: Richard Coleman <coleman@math.gatech.edu>
To: zsh-workers@math.gatech.edu
Subject: global zlogout and .zlogout
Date: Wed, 18 Oct 1995 01:59:14 -0400 [thread overview]
Message-ID: <9510180559.AA25070@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Wed, 06 Sep 1995 18:37:31 +0200." <199509061637.SAA02444@bolyai.cs.elte.hu>
> > 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 think that the same holds for the vanilla beta10. zlogout should be
> executed if zlogin (or zprofile) executed on login. Currently zlogout
> executed only on exit from login shells if NO_RCS is not set.
I'm going back through old mail, so I was looking at this problem
again. I'm want to know what everyone this is the most usual
behavoir.
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 the way the global zlogin file is handled.
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.
What does everyone think?
rc
next prev parent reply other threads:[~1995-10-18 6:07 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 ` Richard Coleman [this message]
1995-10-18 18:54 ` global zlogout and .zlogout Carlos Carvalho
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=9510180559.AA25070@redwood.skiles.gatech.edu \
--to=coleman@math.gatech.edu \
--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).