StreakyCobra

"The Craft of Text Editing" (http://www.finseth.com/craft/) could also interest people who like reading about text editor internals.

Really nice, well explained. I'll know where to point people to when I need to present this techique. Thanks!

Nice thanks. I don't have twitter. Also don't present me as the inventor of this technique because I'm not. I've read this long time ago on some dark corners of the internet :-) I'm just pointing it out.

It's probably better if you do it then :-) I would probably skip some important parts trying to explain because I'm too much used to it already.

There are probably already posts about this: I didn't invented it, I read it somewhere… but it was long time ago, I don't remember where.

It's because we specify to git that the working tree is the home folder. For it the versionning doesn't happen in ".myconf", but directly in the home folder

Because the working tree is already your home folder, you don't need to also have a copy of these files in ".myconf/".

I have a "master" branch, and some "computer" branches. When changes are required for all computer, I do it in "master", and then update each branch by doing a "git merge master".

I use:

    git init --bare $HOME/.myconf
    alias config='/usr/bin/git --git-dir=$HOME/.myconf/ --work-tree=$HOME'
    config config status.showUntrackedFiles no

where my ~/.myconf directory is a git bare repository. Then any file within the home folder can be versioned with normal commands like:

    config status
    config add .vimrc
    config commit -m "Add vimrc"
    config add .config/redshift.conf
    config commit -m "Add redshift config"
    config push

And so one…

No extra tooling, no symlinks, files are tracked on a version control system, you can use different branches for different computers, you can replicate you configuration easily on new installation.

Try `SPC T T`

We know, we have a problem generating links that work both with our new online documentation system and github (syntax incompatibility). For now you have to use http://spacemacs.org/doc/DOCUMENTATION.html :-)

It works probably not as well as vim which is a terminal application. Spacemacs is fully featured on the GUI version, the terminal version works well, but be ready to meet a few bugs in the borders :-)

Come to the dark side of Emacs. We have cookies.

Come to the dark side of Emacs. We have cookies.

«But that would be an extraordinary coincidence, if that happened so recently, only a few millennia before humans developed the tech to loft a telescope into space. That’s a narrow band of time, cosmically speaking.

After all, this light pattern doesn’t show up anywhere else, across 150,000 stars. We know that something strange is going on out there.»

It would also be an extraordinary coincidence if we find another planet with life on it, so quickly after humans started to look for it. 150'000 stars is a narrow band of universe, cosmically speaking.

« As of today, I’ve been using this setup for, err, about 9 months. I started writing this in December last year but never got around to finishing the post. »

<joke>So, it's not a very efficient distraction-free setup...</joke>