zsh-workers
 help / color / mirror / code / Atom feed
From: Richard Coleman <coleman@math.gatech.edu>
To: zsh-workers@math.gatech.edu
Subject: Re: global zlogout and .zlogout
Date: Wed, 18 Oct 1995 15:28:02 -0400	[thread overview]
Message-ID: <9510181928.AA01846@redwood.skiles.gatech.edu> (raw)
In-Reply-To: Your message of "Wed, 18 Oct 1995 16:54:08 -0200." <199510181854.QAA00335@snfep1.if.usp.br>

>  >> > 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? :-)

That's what I get for writing e-mail at 2am.  I meant to say I want to know
what everyone thinks is the preferred behavior.

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

Yes, I know.  Just repeating it for emphasis (I like to hear myself talk :-)

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

I meant to say the global zshenv, not the global zlogin.  But the more I
think about it, I'm no longer happy with this idea.  There should be
someway to suppress the sourcing of the global zlogout.  But you don't
want users to be able to do this.  I believe it was Zoltan who mentioned
sourcing the global zlogout only if the global zlogin was sourced.  That is
easy to do.  Before anything is changed, I would like to know for what
purposes are people using the global zlogout file.

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

ERREXIT is suppressed for all the init script (both global and personal).
Seems like the same should be the case for the global zlogout and .zlogout.

rc



  reply	other threads:[~1995-10-18 19:33 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
1995-10-18 19:28       ` Richard Coleman [this message]
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=9510181928.AA01846@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).