Re: Introducing vcsh - manage config files in $HOME via fake bare git repositories

From: Richard Hartmann <richih.mailinglist@gmail.com>
Date: Dec 20, 2011, 11:05 UTC
Message-ID: <CAD77+gSGeE=nKy=LFAHMv3r0=Lpab8T+0vou_OWXN=ir8C55Vg@mail.gmail.com>
In-Reply-To: <CAMK1S_hc4H7rUSY=SSR0EZwgBLy9CGa7b5H44eP6=fw+YC-inw@mail.gmail.com>

On Tue, Dec 20, 2011 at 03:25, Sitaram Chamarty <sitaramc@gmail.com> wrote:

> My reasoning is that nothing is an island.  I am a heavy user of vim,
> fugitive (git plugin for vim), tig, and ranger, and at least these 4
> are linked to each other.  You could argue that I should use
> submodules or gitslave or something but I keep it simple.

Or mr[1]. That's _exactly_ what mr is for.

>  Even my
> "irssi" settings are tied into that, because of certain macros I use
> to reply quickly to queries.

I doubt you want to keep your IRC passwords on a work machine, for example. If you need repos to be together, check them out together. But I doubt you want _everything_ _everywhere_.

> There's a piece of my ".additional.bashrc" that automatically symlinks
> everything that are best left in $HOME (like ~/.gitconfig) and sets up
> environment variables for everything else (like TIGRC_USER) that can
> get along without.

Symlinks are unclean, imo.

Personally, I like to use .zshrc.$HOSTNAME for local stuff. This sorts more nicely than .$HOSTNAME.zshrc .

> There are 2 helper scripts.  One packs all of this into a tarball so I
> can easily untar it on any machine on which I have to work
> temporarily, and the other cleans up the unpacked directory and
> symlinks when I leave.

Cloning from public repos seems to make more sense, especially if you make local changes.

> Just offering a different perspective.

Appreciated. It's always great to know how others are approaching this.

Richard