From: "Benjamin R. Haskell" <zsh@benizi.com>
To: TJ Luoma <luomat@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: do you use separate .zshenv and .zshrc files?
Date: Sat, 28 Apr 2012 16:54:15 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1204281633070.27115@hp.internal> (raw)
In-Reply-To: <4B2741961D3F4053AD4A3F6A195E2371@gmail.com>
On Sat, 28 Apr 2012, TJ Luoma wrote:
> I keep vacillating between wanting to separate my config files into
> two separate files or keep them in one.
My config currently spans 19 files, so my bias should be apparent. I
keep everything in ~/.zsh/, except for machine-specific settings, which
I put in ~/.zsh.local/. And ~/.zshenv is a symlink to ~/.zsh/.zshenv,
which sets ZDOTDIR to ~/.zsh. My ~/.zsh/.zshrc sources the other files
in ~/.zsh/, most of which have some guard at the top (e.g.
~/.zsh/.zsh_screen returns if the `screen` command isn't installed).
> If I understand ZSH correctly, I could use one file (.zshenv) and put
> the settings which *would* have been in .zshrc into a block like this:
>
> if [[ -o login ]]
You want 'interactive' here, not 'login':
if [[ -o interactive ]]
> then
> # do stuff which would have been in .zshrc here
> fi
[[ -o login ]] would catch things that would be done in .zprofile and
.zlogin, not those that are done in .zshrc.
> The reason for doing this is that I tend to forget which file has
> whatever thing it is that I want to tweak/edit/change/add, and so I
> end up having to open one, search for what I'm looking for, realize
> it's in the other file, and then open the other file.
>
> ISTM that it would be easier to just keep everything in one file and
> separate the login stuff using the `if` statement above.
As pointed out above .zshenv vs .zshrc isn't a difference of "login" vs.
not. It's "interactive" vs. not.
Here's the order of the standard four files, and the condition under
which they run:
.zshenv: (always)
.zprofile: [[ -o login ]]
.zshrc: [[ -o interactive ]]
.zlogin: [[ -o login ]]
To disable all of them, there is the 'NO_RCS' option.
Personally, I don't use .zprofile or .zlogin, because all of my
customization outside of .zshenv is only applicable to interactive
shells.
> Are there any drawbacks to that method?
None that I know of. If that's how you prefer to organize it, it should
work fine.
--
Best,
Ben
next prev parent reply other threads:[~2012-04-28 21:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-28 19:07 TJ Luoma
2012-04-28 20:54 ` Benjamin R. Haskell [this message]
2012-04-28 21:01 ` Benjamin R. Haskell
2012-04-28 21:57 ` TJ Luoma
2012-04-28 22:25 ` Benjamin R. Haskell
2012-04-28 23:03 ` Bart Schaefer
2012-04-28 23:19 ` TJ Luoma
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=alpine.LNX.2.01.1204281633070.27115@hp.internal \
--to=zsh@benizi.com \
--cc=luomat@gmail.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).