From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: use zsh as login shell
Date: Mon, 01 Dec 2014 13:57:54 +0100 [thread overview]
Message-ID: <87egsjcyst.fsf@gnu.org> (raw)
In-Reply-To: <87vblyy9ia.fsf@gmail.com> ("宋文武"'s message of "Sat, 29 Nov 2014 11:24:13 +0800")
宋文武 <iyzsong@gmail.com> skribis:
> Ludovic Courtès <ludo@gnu.org> writes:
>
>> 宋文武 <iyzsong@gmail.com> skribis:
>>
>>> Ludovic Courtès <ludo@gnu.org> writes:
[...]
>> So, instead of what you suggest, what about having:
>>
>> 1. /etc/profile and /etc/zlogin (?) both source /etc/environment,
>> which uses plain Bourne syntax.
>>
>> 2. PATH is defined in /etc/environment and includes
>> ~/.guix-profile/bin.
> /etc/environment is defined by pam_env to be a simple KEY=VAL file, with no
> support for varibales substitute. If we do not use pam_env (linux specified?),
> I think we should let /etc/zlogin source /etc/profile instead.
Yes, but they would contain almost the same lines, right? To what
extent is zsh Bourne- or Bash-compatible? Does ‘export foo=bar’ work
for zsh?
If it does, let’s just keep /etc/profile, and use it for both zsh and
Bash.
> And we don't want /etc/zlogin when not using zsh at all,
> IIUC while skeletons is configurable at the top os-expr, /etc/zlogin is
> not.
It’s OK to have a 2-KiB /etc/zlogin, even when one doesn’t use zsh.
>> 3. The skeleton for ~/.bash_profile sources /etc/profile, /etc/bashrc,
>> and ~/.bashrc.
>>
>> 4. The definition of PS1 is moved from /etc/profile to /etc/bashrc.
>>
>> 5. The skeleton for ~/.bashrc sources /etc/bashrc.
> It seem too much, what I suggested is:
> for login, su (pam_env): /etc/environment
> for login shell: ~/.bash_profile, ~/.zlogin
> for interactive: ~/.bashrc, ~/.zshrc
> skeletons only installed when needed :)
As a first step, what about always installing the skeletons? Then we
can see whether/how to refine that.
Thanks,
Ludo’.
next prev parent reply other threads:[~2014-12-01 12:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-27 15:58 use zsh as login shell 宋文武
2014-11-27 20:15 ` Ludovic Courtès
2014-11-28 15:06 ` 宋文武
2014-11-28 22:26 ` Ludovic Courtès
2014-11-29 3:24 ` 宋文武
2014-12-01 12:57 ` Ludovic Courtès [this message]
2014-12-02 14:43 ` 宋文武
2014-12-04 23:10 ` Ludovic Courtès
2014-12-05 5:11 ` Mark H Weaver
2014-12-05 18:54 ` Ludovic Courtès
2014-12-05 11:21 ` 宋文武
2014-12-06 8:04 ` use zsh and fish " 宋文武
2014-12-06 15:09 ` Ludovic Courtès
2014-11-28 15:11 ` use zsh " 宋文武
2014-12-05 13:57 ` 宋文武
2014-12-06 22:35 ` /etc/profile and .zshrc skeleton Ludovic Courtès
2014-12-07 4:06 ` 宋文武
2014-12-07 20:35 ` Ludovic Courtès
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=87egsjcyst.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=iyzsong@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).