alxhnr / build.vim Goto Github PK

Hello,
In order to implement properly #1 I need the Build command to do be able to use different command templates depending on its parameters.
For example if I add the following to the s:build_systems dict:

  \   'Dune':
  \   {
  \     'file'    : 'dune',
  \     'command' : 'dune',
  \   },

Basically nothing work as expected:

• Build command produce the dune help message
• Build run initialize the build directory but do nothing more
• Build build actually build the project
• Build exec ./%:r.exe would actually run the current file if it is defined in a dune file as an executable to be buit and the only dune file is in the current working directory of vim.

So for a retro compatible fix of this I would propose that the 'command' item of a build system could be either a string, in which case nothing changes, or a dictionary of specific commands.
This dictionary would be similar to s:language_cmds items:

• keys would correspond to the first argument from the Build command, and 'build' would be used by default
• the commands themselves would be templates (using s:prepare_cmd_for_shell) and ran from the location of the first build system file found

Also, a new magic should be added to s:prepare_cmd_for_shell: %RELPATH% being the relative path directory where the command will be ran to the current file.

This way I could implement my previous example as:

  \   'Dune':
  \   {
  \     'file'    : 'dune',
  \     'command' : {
  \       'build' : 'dune build',
  \       'clean' : 'dune clean',
  \       'run'   : 'dune exec %RELPATH%/%HEAD%.exe',
 \      },
  \   },

Eventually, a 'base' key could be added to the 'command' dict (in this case the value would be 'dune') which would allow handling unknown arguments to Build (:Build runtest would expand to dune runtest using 'base').

I would happily implement all of this but I do not want to take over your project @AlxHnr so what do you think ?
Does this conform to what you want for this plugin ?