https://github.com/jgillman/dotfiles

jgillman's special collection of configs
https://github.com/jgillman/dotfiles

bash dotfiles shell tweaks zsh

Last synced: about 1 month ago
JSON representation

jgillman's special collection of configs

• Host: GitHub
• URL: https://github.com/jgillman/dotfiles
• Owner: jgillman
• Created: 2012-04-10T17:20:39.000Z (over 12 years ago)
• Default Branch: main
• Last Pushed: 2024-01-25T22:45:34.000Z (8 months ago)
• Last Synced: 2024-06-17T21:52:28.078Z (3 months ago)
• Topics: bash, dotfiles, shell, tweaks, zsh
• Language: Shell
• Homepage:
• Size: 775 KB
• Stars: 17
• Watchers: 1
• Forks: 3
• Open Issues: 1
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

• jimsghstars - jgillman/dotfiles - jgillman's special collection of configs (Shell)

README

        
# jgillman's sepcial dotfiles

## Shoutout

The real core of these dotfiles are from [holman's

dotfiles](https://github.com/holman/dotfiles). I had been holding off using

GitHub for my dotfiles simply because I wasn't aware of a good way of

automatically symlinking them and keeping them organized. holman's use of topic

folders and a Rakefile to automate symlinking has made it too easy not to. All

credit goes to him.

## dotfiles

Dotfiles essentially what makes your environment *yours*. All your unique little

tweaks and settings that make your computer completely unusable and foreign to

others. I had originally kept all my dotfiles in Dropbox which worked really

nicely for a long time. Two big issues I had with my Dropbox setup is that 1) I

would manually have to symlink new files/folder and 2) I couldn't use them on

remote development machines (where I often work).

Also, to steal directly from [holman](https://github.com/holman):

> I was a little tired of having long alias files and everything strewn about

> (which is extremely common on other dotfiles projects, too). That led to this

> project being much more topic-centric. I realized I could split a lot of

> things up into the main areas I used (Ruby, git, system libraries, and so on),

> so I structured the project accordingly.

> 

> If you're interested in the philosophy behind why projects like these are

> awesome, you might want to [read my post on the

> subject](http://zachholman.com/2010/08/dotfiles-are-meant-to-be-forked/).

## install

- `git clone [email protected]:jgillman/dotfiles.git ~/.dotfiles`

- `cd ~/.dotfiles`

- `rake install`

The install rake task will symlink the appropriate files in `.dotfiles` to your

home directory. Everything is configured and tweaked within `~/.dotfiles`,

though.

## topical

Everything's built around topic areas. If you're adding a new area to your

forked dotfiles — say, "Java" — you can simply add a `java` directory and put

files in there. Anything with an extension of `.zsh` will get automatically

included into your shell. Anything with an extension of `.symlink` will get

symlinked without extension into `$HOME` when you run `rake install`.

## components

There's a few special files in the hierarchy.

- **bin/**: Anything in `bin/` will get added to your `$PATH` and be made

  available everywhere.

- **topic/\*.zsh**: Any files ending in `.zsh` get loaded into your

  environment.

- **topic/\*.symlink**: Any files ending in `*.symlink` get symlinked into

  your `$HOME`. This is so you can keep all of those versioned in your dotfiles

  but still keep those autoloaded files in your home directory. These get

  symlinked in when you run `rake install`.

- **topic/\*.completion.sh**: Any files ending in `completion.sh` get loaded

  last so that they get loaded after we set up zsh autocomplete functions.