unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Meiyo Peng <meiyo.peng@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: move "source /etc/profile" from .zlogin to .zprofile
Date: Sat, 13 Oct 2018 18:33:59 -0700	[thread overview]
Message-ID: <87sh198g6w.fsf@gmail.com> (raw)
In-Reply-To: <87o9bxj1fy.fsf@gmail.com> (Meiyo Peng's message of "Sat, 13 Oct 2018 23:44:49 +0800")

[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]

Hi Meiyo,

Meiyo Peng <meiyo.peng@gmail.com> writes:

> Guix's default skeletons put "source /etc/profile" into ~/.zlogin. But
> /etc/profile resets the PATH environment variable, exports many other
> environment variables, and source /etc/bashrc. According to
> http://zsh.sourceforge.net/Intro/intro_3.html .zlogin is sourced after
> .zshrc and should not be used for alias definitions, options,
> environment variable settings, etc. Especially "as a general rule, it
> should not change the shell environment at all". I think it's better to
> source /etc/profile from ~/.zprofile.

The same documentation you linked says:

    `.zprofile' is meant as an alternative to `.zlogin' for ksh fans;
    the two are not intended to be used together, although this could
    certainly be done if desired.

Is the intended use of .zprofile any different from the intended use of
.zlogin?  If .zprofile and .zlogin are both meant to serve the same
purpose, then I'm not sure why one would be preferable over the other.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-10-14  1:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-13 15:44 move "source /etc/profile" from .zlogin to .zprofile Meiyo Peng
2018-10-14  1:33 ` Chris Marusich [this message]
2018-10-14  1:56   ` Leo Famulari
2018-10-14  6:30     ` Chris Marusich
2018-10-14  7:58       ` Meiyo Peng
2018-10-15  9:48       ` Ludovic Courtès
2018-10-16  4:59         ` Leo Famulari
2018-10-16 11:55           ` Ludovic Courtès
2018-10-19  7:47             ` Chris Marusich
2018-10-14  3:14   ` Meiyo Peng

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sh198g6w.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=meiyo.peng@gmail.com \
    /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.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).