zsh-workers
 help / color / mirror / code / Atom feed
From: Vincent Lefevre <vincent@vinc17.org>
To: zsh-workers@sunsite.dk
Subject: Re: environment settings
Date: Mon, 23 Jun 2008 18:16:48 +0200	[thread overview]
Message-ID: <20080623161648.GI10734@prunille.vinc17.org> (raw)
In-Reply-To: <20080623152431.GM4961@sc.homeunix.net>

On 2008-06-23 16:24:31 +0100, Stephane Chazelas wrote:
> Note that $SHELL is called for that purpose in a number of
> places such as vi's :!, ftp's !,

In those cases, sourcing the .zshenv doesn't hurt. On the contrary,
it allows to define some aliases or whatever the user wishes.

> ssh host 'cmd line'... not only gdb.

ssh runs the user's default login shell on the remote host, which can
be different from $SHELL. And this was the problem I was mentioning
with bash: there's no way to set up some environment variables. So,
with bash, "ssh -t host some_program" won't work if some_program is
in the user's $HOME/bin directory, even though the user always has
this directory in his $PATH.

> It's true it would be nice to be able to distinguish between zsh
> instances that are meant to be user shells that is that are
> meant to parse command lines given by the user and instances
> that are meant to run canonical zsh code where the user is not
> meant to alter the zsh behavior (as in zsh scripts, zsh -c ...) 

Yes, but I doubt this would solve all the problems. When I use
"zsh -c", I want .zshenv to be sourced (the reason is that I
sometimes do "ssh [-t] host zsh -c ..." and the .zshenv is the
*only* way to set up environment variables -- but I could also
source my .zshenv at the beginning of the command string).

> csh solves that with the -f option without which every csh
> instance is sourcing .cshrc (so csh scripts have #! /bin/csh
> -f).

But this solution needs to hardcode the csh path in the script.
Something like "#!/usr/bin/env csh -f" doesn't work everywhere.

> With zsh, you could solve that by having $SHELL be
> /path/to/user-zsh, user-zsh being a link to zsh and ~/.zshenv
> having something like:
> 
> [[ $0 != (*/|)user-zsh || -o interactive ]] ||
>   . "${ZDOTDIR:-$HOME}/.zshrc"
> 
> (not tested but you get the idea).

Yes, nice idea.

Concerning gdb (which is an exception), I could write a wrapper that
sets some environment variable, which could be tested in the .zshenv
to do what I want exactly.

-- 
Vincent Lefèvre <vincent@vinc17.org> - Web: <http://www.vinc17.org/>
100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/>
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)


  reply	other threads:[~2008-06-23 16:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080616074651.GB26165@marcus>
     [not found] ` <20080616080556.GA5091@sc.homeunix.net>
     [not found]   ` <20080616123045.GC26165@marcus>
     [not found]     ` <20080616124450.GC5091@sc.homeunix.net>
2008-06-17  8:33       ` Jörg Sommer
2008-06-17  9:39         ` Stephane Chazelas
2008-06-17 10:41           ` Vincent Lefevre
2008-06-17 12:58             ` Stephane Chazelas
2008-06-17 13:11               ` Vincent Lefevre
2008-06-17 13:26                 ` Stephane Chazelas
2008-06-17 13:28                   ` Mikael Magnusson
2008-06-17 14:25                     ` Stephane Chazelas
2008-06-17 15:54                       ` Vincent Lefevre
2008-06-17 16:00                         ` Stephane Chazelas
2008-06-17 19:50                           ` Vincent Lefevre
2008-06-17 20:32                             ` Stephane Chazelas
2008-06-18 10:38                               ` Vincent Lefevre
2008-06-18 11:52                                 ` Stephane Chazelas
2008-06-18 17:11                                   ` Bart Schaefer
2008-06-17 14:55                     ` Vincent Lefevre
2008-06-17 14:45                   ` Vincent Lefevre
2008-06-18  8:49           ` Jörg Sommer
2008-06-18  9:33             ` Stephane Chazelas
2008-06-21  6:26         ` Wayne Davison
2008-06-21 11:36           ` Vincent Lefevre
2008-06-21 12:30             ` Stephane Chazelas
2008-06-22  8:41               ` Vincent Lefevre
2008-06-23 15:24                 ` Stephane Chazelas
2008-06-23 16:16                   ` Vincent Lefevre [this message]
2008-06-23 16:20                   ` Bart Schaefer
2008-06-23 16:29                     ` Stephane Chazelas

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=20080623161648.GI10734@prunille.vinc17.org \
    --to=vincent@vinc17.org \
    --cc=zsh-workers@sunsite.dk \
    /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).