Gollum VS Guard

(Gollum)[https://github.com/gollum/gollum] can do that but that's a wiki.

Fun to see this on HN! I originally created Gollum to power GitHub's wiki system and wanted to see if we could use Git to make our wikis more powerful AND more open. I thought it would be cool if you could just clone your GitHub wiki and modify it locally or export it to some other system if you needed, or have it all locally for an airplane trip without wifi.

Another interesting thing is that I used my Readme Driven Development method to develop it, which you can see in the Readme of the first commit: https://github.com/gollum/gollum/commit/c7875704971be998a539.... I wrote it before writing a single line of code and found it worked nicely to figure out the API and feel out the ergonomics of the text format. More on that approach here: https://tom.preston-werner.com/2010/08/23/readme-driven-deve...

Glad to see the project alive and well!

Instead of SQLite I would prefer if you stored the snippets in a git repo like Gollum or Gitit.

I use Gollum for my note-taking and planning, and that lets me edit everything in Vim, use git for version control, and use any of a number of standard markup languages that have good Vim support.

This might be up your street: https://github.com/gollum/gollum

TL;DR - Gollum wiki using Vimwiki's home directory.

You should definitely use something more polished like Guard but you could also experiment with a "simpler" approach.

Check out https://github.com/guard/guard and https://github.com/guard/guard-rspec (if you're using rspec)

Probably https://github.com/guard/guard

Installation guide for guard

Guard is a gem I have some prior experience with; it can be configured so that when a change is made to a file (for example: models/user.rb) it will autorun the associated test file (in this example: user_test.rb). As you can imagine, this significantly cuts down on the time until seeing either red or green tests which is super helpful for TDD and a necessary first part of TCR.

Now, consider this a mea culpa, as I know there are many ways this could go wrong. The guard documentation was also kind enough to warn me as such. This is, for better or for worse, my first attempt at building out a way to TCR in Rails. I’m excited to be able to follow up as I spend more time with my monstrous guardfile and this workflow so I can let you know how it goes.

Two key pieces of guard documentation, one on creating an inline guard and the other on hooks and callbacks. All of the docs were very helpful though!