zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-users@zsh.org
Subject: Re: Gentoo startup bug
Date: Fri, 26 Oct 2012 09:42:11 +0100	[thread overview]
Message-ID: <CAECNH1RjZKYpcBJLkv1Gu4xaQh=tCRL57yUOmK7gj7TECJfRdg@mail.gmail.com> (raw)
In-Reply-To: <50897049.9040708@bernd-steinhauser.de>

On 25 October 2012 18:00, Bernd Steinhauser <linux@bernd-steinhauser.de> wrote:
> I didn't look at Gentoo's zprofile in a few years, but even if (for whatever
> reason), they would reset $path after ~/.zshenv has run I highly doubt that
> your solution is desirable (Actually, it might be desirable to reset $path,
> because it affects `zsh -f`, but I didn't invest a lot of thought into that
> one.).
> Most likely, you misunderstood or misinterpreted what zshenv is for. There
> have been discussions about that topic zshenv vs. zshrc vs. zprofile on the
> zsh lists, you might want to search the archives for that (also look at
> zsh's manpage).
> Or mind if I ask why you set your user changes of $path in ~/.zshenv rather
> than ~/.zshrc (where it should be set, since you want it in interactive
> shells).

Without going into the details, there are perfectly good reasons for
putting your path in .zshenv, such as having the same path in all
instances of the shell.

The main point is there's really no good argument for a distribution to trash
a user's path.  You simply can't guess how the many users of many different
types are going to use the shell. I agree this bit is definitely
wrong. It's a very
different argument from, say, a specific site where you expect users to
conform to a certain way of doing things.

pws


  reply	other threads:[~2012-10-26  8:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-24 14:25 ☈king
2012-10-24 15:00 ` Damien Thébault
2012-10-24 15:08   ` ☈king
2012-10-25 17:00     ` Bernd Steinhauser
2012-10-26  8:42       ` Peter Stephenson [this message]
2012-10-27 15:29         ` Bernd Steinhauser

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='CAECNH1RjZKYpcBJLkv1Gu4xaQh=tCRL57yUOmK7gj7TECJfRdg@mail.gmail.com' \
    --to=p.w.stephenson@ntlworld.com \
    --cc=zsh-users@zsh.org \
    /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).