zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@sunsite.dk
Subject: Re: syncing .zsh* files
Date: Sat, 7 Aug 2004 15:07:37 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.61.0408061226140.13293@toltec.zanshin.com> (raw)
In-Reply-To: <20040806182550.GC7244@ay.vinc17.org>

I have all my zsh configurations stored in CVS on a host I can access with 
CVS_RSH=ssh.  They're designed to be checked out into a directory ~/.zsh 
on each host, and then I have a little installer script that sets up a 
~/.zshenv file which does nothing more than assign ZDOTDIR=~/.zsh and then 
source the ~/.zsh/.zshenv file.  (If ZDOTDIR is already set, the ~/.zshenv
is never seen, so there's no reason to e.g. guard this with an "if".)

There can be a subdirectory named "local" in the .zsh directory from which 
host-specific files, if they exist, are sourced by the ~/.zsh/.zshrc 
(etc.) files.  I keep a set of subdirectories named for the host or domain 
(e.g. all hosts at work use the same one); those are checked into CVS and 
then I symlink the name "local" to the correct one for each install.

At first I tried organizing everything by host architecture or OS, but I 
ended up dividing it by, for lack of a better term, purpose -- things 
needed in all shells, in interactive shells, just once when starting a new 
session (e.g., before X11 startup), etc., and then sometimes subdividing 
into options, bindings, completion, terminal handling, etc. There's one 
file that sets up aliases or functions to mask differences in default 
behavior of ps, ls, df, etc. on different architectures, but most of the 
case-statements on $HOSTTYPE are scattered in various files because I 
could never find a common place in the startup sequence to do all of that 
at once.


  reply	other threads:[~2004-08-07 22:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-06 16:17 Timothy Luoma
2004-08-06 16:39 ` Björn Lindström
2004-08-06 16:49 ` Matt Pharr
2004-08-06 18:25 ` Vincent Lefevre
2004-08-07 22:07   ` Bart Schaefer [this message]
2004-08-07  8:06 ` Michael Prokop

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=Pine.LNX.4.61.0408061226140.13293@toltec.zanshin.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /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).