From: Meiyo Peng <meiyo.peng@gmail.com>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: move "source /etc/profile" from .zlogin to .zprofile
Date: Sun, 14 Oct 2018 07:58:31 +0000 [thread overview]
Message-ID: <CADCc2gHmZ7LcUErdctBdx+bgJ8JbwFxk010iQwi_=fKN5dz=Yw@mail.gmail.com> (raw)
In-Reply-To: <8736t96nwt.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 974 bytes --]
Hi Chris,
On Sun, Oct 14, 2018 at 6:30 AM Chris Marusich wrote:
> I haven't tested it, though. Would you like to test it and
> let me know if it works for you?
Guix is still new to me, and I don't know how to apply the patch and
build guix. But I moved "source /etc/profile" from my .zlogin to
.zprofile and I have no problem.
> I see that zsh also sources files like /etc/zprofile when they exist. I
> don't have a strong preference for putting this into /etc/zprofile
> vs. putting it into ~/.zprofile (via /etc/skel). What do you think
> about that?
Usually I prefer to put less dot files in my $HOME directory. But I'm OK
with guix's solution.
> I've always found the relationship between shell start-up scripts to be
> confusing; everyone seems to want to configure them differently.
I agree. So I prefer to use fish shell, which is simpler. But I have to
temporarily switch to zsh until this bug is fixed:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30265
[-- Attachment #2: Type: text/html, Size: 1203 bytes --]
next prev parent reply other threads:[~2018-10-14 7:58 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
2018-10-14 1:56 ` Leo Famulari
2018-10-14 6:30 ` Chris Marusich
2018-10-14 7:58 ` Meiyo Peng [this message]
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='CADCc2gHmZ7LcUErdctBdx+bgJ8JbwFxk010iQwi_=fKN5dz=Yw@mail.gmail.com' \
--to=meiyo.peng@gmail.com \
--cc=cmmarusich@gmail.com \
--cc=guix-devel@gnu.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.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).