Kristoffer Bjärkefur

I have been thinking about this too, and one idea that border hubris but would be really great, would be to use GitHub's API and build that package manager to...

But for them to be package manager where different versions of the command can be used in different projects, or even different parts of the projects (although that risks being...

In the regard of functionality, yes. But not sure if that is the way we want to implement it tho. Not saying there is a better way that would work,...

That is really cool! The only thing I missing is to install something in current memory only, so that I can run your project and have your setup and then...

I am convinced that this is better. How should we deal with backward compatibility?

Another related thing that I often have received as feedback was that is should be `second_group - first_group` instead of `first_group - second_group` as control is often the first group...

code will still run, but results are no longer replicable...

It would be nice to have it work with **syv** so that people that is already using it does not have to define weights etc. again. I haven't used **syv**...

**iebaltab** is in need of a major re-write anyways. Since most (maybe even all?) of the functionality of **syv** already exists as options to **iebaltab**, we do not think it...

@MRuzzante , thanks for this! Here are my reactions to your suggestions: **Things I agree that we should implement** - I like the vct_type abbreviation, that should be possible to...