Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: strange behaviour with .zsh and su
- X-seq: zsh-users 811
- From: "Tom Howland" <tomh@xxxxxxxxxxxx>
- To: Stefan Monnier <monnier+/news/lists/zsh/users@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Subject: Re: strange behaviour with .zsh and su
- Date: Mon, 14 Apr 1997 11:42:40 -0700
- Cc: zsh-users@xxxxxxxxxxxxxxx
- In-reply-to: <5lencd5uvc.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- References: <19970414103243.56053@retriever> <Pine.SUN.3.96.970414084219.21724A-100000@kira> <5lencd5uvc.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Reply-to: <tomh@xxxxxxxxxxxx>
Stefan Monnier writes:
> Timothy Luoma <luomat@xxxxxxxx> writes:
> > The zshenv file includes a loop which sources any file found in
> > $HOME/Unix/zsh/source, so I have several files in there:
>
> I don't know why shell writers insist on using several init files.
> The .login/.zshprofile/.zshlogin file isn't sourced every time you'd need it
> (typically, it's not sourced from an XDM login), so you need to move stuff from
> there into zshenv.
I agree. There are already plenty of initialization files for zsh.
> On another hand, a variable indicating whether the shell is a login shell is
> necessary (and sadly missing from tcsh).
Its not all that necessary. The following seems to work
tty -s
[ $? -eq 0 ] && stty -parenb -istrip cs8 erase "^H" intr "^C" susp "^Z" start "^Q" stop "^S" quit "^\\" dsusp "^Y" -ixany echoe
Messages sorted by:
Reverse Date,
Date,
Thread,
Author