Matus Goljer

The help output is not really great for machine consumption, which the `-v` strings sometimes try to be (not always though)

Oh I see, so it is basically a "filesystem" dump of the database, indexed by the tags, where if a file is under say 3 tags it will be symlinked...

Heh, I don't actually remember how I migrated the data, but I have the repository working so I suppose I've used this method :D It's been some time.

I think the analysis is as follows: since buttercup relies on lexical scoping, the `let` form generated by `:var` is placed as parent to all the "gathering functions" (`buttercup-before-each`, `buttercup-it`...

Re separate file, yep, definitely a good idea. I remember ecukes also had tons of these "topic" files with predicates/matchers for all sorts of things (buffer related, strings, filesystem etc.)...

@jorgenschaefer Problem with `setq` is that it corrupts the global state. It would not be a problem if buttercup run each test case in a separate Emacs instance but that...

What you described is a common idiom in javascript but remember that there the scoping works different ```js describe('getProductValue', () => { let edsnDown describe('when edsn is up', () =>...

@jorgenschaefer That is actually really cool idea. You were doing some ruby lately heh? :D Yea I think that could work if implemented properly. I'll try to take a look...

I probably won't work on this in any reasonably close future.

Using uds as a backend for `git-annex` would be also a pretty easy way to achieve this. But it comes with all the complexity of that tool attached.