Passing command-line arguments, when running whole file like :%SnipRun {args}

[DipeshChouhan]

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[michaelb]

Hmm i'll have to think about that

There is surely a way to capture arguments from the vim command line and pass them to the final script/executable but:

• may be a bit clunky to use. I mean typing ":%SnipRun arg1 arg2 arg3" each time you want to test something?

• relative path (as CLI argument) will be an issue, because sniprun runs in its own location. This won't change but maybe we can hack around with symlinks and stuff

[DipeshChouhan]

Is it possible to toggle the feature on or off. If on then only it will ask for arguments.

[michaelb]

Is it possible to toggle the feature on or off. If on then only it will ask for arguments.

I don't think it is necessary: you'd think when there is no arguments after the SnipRun command, then, no args. Otherwise, copy the extra arguments from the neovim command to the (ex in python) python main.py command sniprun launches

Or maybe I don't understand what you mean by 'ask for argument'

Your feature request is quite feasible and a good suggestion, though I'll need some time to work on implementation details and making the thing work, especially when the argument is a relative path

Anyway, the more we discuss here, the clearer your request will be :-)