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 18:25:29 -0400 (EDT) [thread overview]
Message-ID: <alpine.LNX.2.01.1204281801310.27115@hp.internal> (raw)
In-Reply-To: <07DD5A5D889944F7B10E983AF5776A6D@gmail.com>
On Sat, 28 Apr 2012, TJ Luoma wrote:
>
>
> On Saturday, April 28, 2012 at 4:54 PM, Benjamin R. Haskell wrote:
>
>> 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).
>
> Ok, now I'm curious:
>
> 1. What are the 19 files? Functions in one, aliases in another,
> variables in another? I can't even imagine that many different files,
> but maybe I'm missing something.
Note that I didn't say my bias was "correct", only "apparent". ;-)
It's mostly from inertia that I still keep my config in that many files,
but here they are (I miscounted -- only 18):
.zsh_aliases - one-liners: aliases, hash -d, some tiny functions
.zsh_checkconfig - alerts me when certain commands/non-zsh configs are missing (e.g. .screenrc)
.zsh_colors - (obsolete) sets some vars to contain VT100 escape sequences
.zsh_completion - completion-system-specific configuration
.zsh_functions - functions of >1 line, simple perl scripts
.zsh_history_setup - history-related options
.zsh_im - sets up X11 Input Method (IM)
.zsh_locale - my locale settings (en_US.UTF-8 except LC_COLLATE=POSIX)
.zsh_make_backups - backs up my .historyfile and a few other files daily
.zsh_math - (rarely used) some small functions/vars relating to math
.zsh_nosefart - small functions for nosefart (an NES sound file player)
.zsh_prompt - sets up my prompt (lots of custom functions)
.zsh_screen - some functions and aliases for using screen/dtach
.zsh_ssh - set up my SSH agent
.zsh_ssh_logip - log my IP if logging in via SSH
.zsh_svn_backup - (obsolete - from when I was using SVN rather than git)
.zshenv - environment variables, paths, etc.
.zshrc - command_not_found_handler, env vars that only make sense
interactively ($LESS, $PAGER, $EDITOR), general Zsh settings, loads the
other files (including things in .zsh.local, if it exists)
> 2. Are you primarily using one computer or several? If several, how
> do you keep this in sync?
I generally have a work PC and a home PC. I keep both of those configs
in git, occasionally cherry-picking things from the work repo into my
home repo. For systems where I won't likely make many modifications, I
generally just rsync to the remote system. Then custom things go in
.zsh.local (e.g. .zsh.local/.zsh_prompt always contains a custom prompt
color). For small synchronization tasks, I use a function that calls
vimdiff on the local and remote files.
> FWIW my ~/.zshenv and ~/.zshenv are links to ~/Dropbox/etc/Zsh/env.sh
> and ~/Dropbox/etc/Zsh/rc.sh but I have some shell accounts which I
> can't sync via Dropbox so I end up syncing them manually (scp) and it
> always seems like one file would be easier there too. OTOH I suppose
> rsync would be easy enough.
Yeah. At the rate I make modifications (infrequently, and usually in
batches), I find it's easy enough to just:
rsync -av ~/.zsh remote-machine:
--
Best,
Ben
next prev parent reply other threads:[~2012-04-28 22:25 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
2012-04-28 21:01 ` Benjamin R. Haskell
2012-04-28 21:57 ` TJ Luoma
2012-04-28 22:25 ` Benjamin R. Haskell [this message]
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.1204281801310.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).