Rob

This is a fine approach, but in order to be merged it would need to have some tests written around it so that it doesn't silently start to fail in...

I don't pretend to know details about how npx and tailwind work together, but I ran into this when launching tailwindcss via npx but not when it was installed to...

My experience was that `:set backupcopy=no` resolved the issue. As with a lot of vim configuration docs aren't immediately obvious. This option dovetails with [`set backup`/`set nobackup`](http://vimdoc.sourceforge.net/htmldoc/options.html#'backup'). From the vim...

There are a bunch of things at play here. For example: - what color is your terminal set to? - what do you mean by "dark"? - is your vim...

This just happened to me again, but this time it had nothing to do with a long running instance of vimr. When the update installed today, Vimr opened up with...

Yes, there was no actual crash. Clicking OK dismissed the dialog and no problems moving forward.

@eliasjpr what do you think of putting code / functionality like this in external shards?

I agree, this will be a good feature to have. Here is my current workaround. I have a file at `src/controllers/application/url_helpers.cr` which is included into my application_controller and has code...

@eliasjpr @shobhitic generating the named routes based off of controller and action seems like a fine way to provide a default. As long as there as a way to override...

This is causing some spec failures: ``` crystal spec $TEST_SUITE Error in line 1: while requiring "././spec/amber/cli/templates/migration_spec.cr" in spec/amber/cli/templates/migration_spec.cr:1: while requiring "../../../spec_helper" require "../../../spec_helper" ^ in spec/spec_helper.cr:21: while requiring "../src/amber"...