Skip to content

Tags: EvanQuan/vim-executioner

Tags

v1.4.0

Toggle v1.4.0's commit message
executioner 1.4.0

Add ability to execute files with Vim commands

v1.3.1

Toggle v1.3.1's commit message
executioner 1.3.1

Check if g:executioner#full_name and g:executioner#base_name are not equal to
1 to set them to default values

Defaults use defined g:executioner#full_name and g:executioner#base_name values

v1.3.0

Toggle v1.3.0's commit message
executioner.vim 1.3.0

Add input and output redirection support
Add :ExecutionerHorizontalBuffer and :ExecutionerVerticalBuffer
Add java to defaults

v1.2.4

Toggle v1.2.4's commit message
executioner.vim 1.2.4

Fix horizontal and vertical buffers without terminal window support not
working as intended.

v1.2.3

Toggle v1.2.3's commit message
executioner.vim 1.2.3

Remove debug mapping

v1.2.2

Toggle v1.2.2's commit message
executioner.vim 1.2.2

Fix file names in g:executioner#names not being detected correctly if
executed in another directory.

v1.2.1

Toggle v1.2.1's commit message
executioner.vim 1.2.1

Command dictionaries are still created even if load_defaults is disabled
in case user does not define them.

v1.2.0

Toggle v1.2.0's commit message
executioner.vim 1.2.0

Defaults can be individually overridden instead of forcing the user
to define the whole dictionary.
Defaults can be disabled from loading with g:executioner#load_defaults

v1.1.2

Toggle v1.1.2's commit message
executioner.vim 1.1.2

Update defaults
.py executes python
.py2 executes python2

v1.1.1

Toggle v1.1.1's commit message
executioner.vim 1.1.1

Does not horizontally/vertically split if there are multiple commands to
be executed (i.e. there are commands separated by semicolons). This is
due to how Vim's :terminal arguments work.