| bashrcd | vcsh | |
|---|---|---|
| 1 | 7 | |
| 0 | 2,151 | |
| - | - | |
| 2.5 | 7.6 | |
| 3 months ago | 23 days ago | |
| Shell | Shell | |
| Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bashrcd
-
Using GNU Stow to manage your dotfiles (2012)
I moved to splitting my bashrc into multiple files and having my main bashrc source them from a ~/.bashrcd directory.
At heart it's a short snippet that just checks for existence and sources each file in the directory:
https://github.com/targaryen/bashrcd/blob/master/install/ins...
I added aliases to list/edit/remove entries from the .bashrcd directory and resource it. And a script I can call with a one-liner to edit bashrc on a new machine to add the sourcing and the helper aliases.
It'll load alphabetically so I can prefix entries with a number to specify load order (defaulting to 0100 so I don't need to specify this in the commands unless I explicitly changed them).
So the end result is that I can quickly edit or create a new bashrc entry by running 'ebrc entryname'. This opens ~/.bashrcd/0100--entryname in vi, and when it's saved it'll re-source so the add/change takes effect immediately.
Or 'lbrc' to list contents of the directory, or 'rbrc entryname' to remove ~/.bashrcd/0100--entryname
It's fairly simplistic but takes away most of the cognitive load of managing a complex bashrc.
vcsh
-
Managing my dot files: Git bare or Stow ?
I'm pretty happy with vcsh. I've used a lot of options over the years, and this is the only one I've never been motivated to replace.
-
GitHub Does Dotfiles
weirdly, nobody mentioned vcsh[1] yet. it's a git-based tool that gives all git goodies. I use it and a couple of bash micro scripts to pull/push the latest changes upon logging in/out into shell (again bash, but seeking for POSIX or fish-based version)
[1] https://github.com/RichiH/vcsh
- Vcsh – multiple Git repositories in $HOME
-
Git ignores .gitignore with .gitignore in .gitignore
I feel obligated to point out vcsh [1], which is likely already packaged for your operating system.
[1] https://github.com/RichiH/vcsh
The main selling point is that you can set up various git repos for different things. I have one for SSH keys (and no, that does not get pushed anywhere except to my own private server), VIM, neovim, bash, and 'other' (for misc config files like .dir_colors, .gitconfig, etc.).
-
How to move dotfiles from $home?
All you need is https://github.com/RichiH/vcsh
-
How do you manage your dotfiles?
I'm using vcsh which is basically a small wrapper around git. The resulting repository is this in my case.
-
Using GNU Stow to manage your dotfiles (2012)
It’s over-engineered, but I’ve been using https://github.com/RichiH/vcsh for this for years.
What are some alternatives?
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
GNU Stow - GNU Stow - mirror of savannah git repository occasionally with more bleeding-edge branches
nix - my nix modules, overlays, host configurations, and more!
yadm - Yet Another Dotfiles Manager
zinit - Flexible and fast Zsh plugin manager with clean fpath, reports, completion management, Turbo, annexes, services, packages.
dotbare - Manage dotfiles and any git directories interactively with fzf
dotfiles - Settings for various tools I use.
dot.me - me dot files
bashdot - Minimalist dotfile management framework.
rcm - rc file (dotfile) management
dotbot - A tool that bootstraps your dotfiles ⚡️