Tim Pope

I can only assume that I meant a single *type*, not a single projection key. I don't really understand your example. It sounds like you are saying you decide if...

* Ditch `projectionist#list_project_files()`. I'm not convinced of its value and it's easy to roll yourself if you need it. * Rename `list_files_for_type` to `files_for_type`. * Inline `get_projection_from_variant` into `get_projections_from_variants` and...

I don't think so, but it would be nice, as I would need something similar before I can unify Projectionist with rails.vim.

"Should" is reaaaally presumptuous. You could maybe argue for this under a liberal interpretation of DWIM but I'm not sure I'm convinced.

The proper event would be after writing the file, not after editing it, as that's when it actually becomes a valid project. But this event is tricky to tap into.

That eliminates the ability to tell where the root of your project is so I don't recommend it. I think the solution in this case would be to install a.vim...

I have always found that approach to be naive and limiting. Not all projects use vcs, and not all vcs repositories are projects. But if you're okay with that limitation,...

You can maybe start vim as `vim -V99` to see a dump of everything that's happening on startup, in order to narrow down the precise trigger. Other than that, you...

Probably possible, but super tricky. The first challenge is to add it to the runtime path. What position does it belong in? The OCD part of me wants to inject...

Off the top of my head, this will have unintended consequences for unnamed buffers, URLs (ranging from `http://` to `fugitive://`), and all things Windows. My larger thoughts are that auto-mkdir...