vimux with Elixir mix integration
Put the contents of this directory into your pathogen bundle.
Vimix provides a number of available commands for common Mix tasks, so that you never have to leave your Vim session. Key mappings are disabled by default, but can easily be enabled by setting the following in your .vimrc:
let g:vimix_map_keys = 1If you'd like run your tests in the context of IEx or change the way tests are run in other ways, you can customize the mix command like so:
let g:vimix_mix_command = "iex -S mix"The default is just mix.
- Changes Vimux runner directory to your mix project root (looks for the mix.exs file)
- Detects correct test file for elixir source files
Here are the key mappings for your reference:
| Key Map | Vim Command | Mix Command |
|---|---|---|
| <Leader>mT | VimixTestAll | test |
| <Leader>mt | VimixTestCurrentFile | test <test file> |
| <Leader>ml | VimixTestCurrentLine | test <test file>:<test line> |
| <Leader>mc | VimixCompile | compile |
| <Leader>mC | VimixClean | clean |
| <Leader>mdc | VimixDepsCompile | deps.compile |
| <Leader>mdg | VimixDepsGet | deps.get |
| <Leader>mds | VimixDepsStatus | deps |
| <Leader>mdU | VimixDepsUpdate | deps.update |
| <Leader>mL | VimixLocal | local |
| <Leader>mr | VimixPromptRun | <prompt for mix command> |
| <Leader>mm | VimuxRunLastCommand | Run last command again |
- Fork it
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Create new Pull Request