Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Param input and output rendering incorrectly #91

Closed
johnhayesio opened this issue Nov 21, 2020 · 1 comment · Fixed by #92
Closed

Param input and output rendering incorrectly #91

johnhayesio opened this issue Nov 21, 2020 · 1 comment · Fixed by #92

Comments

@johnhayesio
Copy link

johnhayesio commented Nov 21, 2020

A couple of things I have noticed with a couple of snippets I have made. When using a snippet with a <param> and sending it to /dev/null 2>&1 & (background job), the param is not being captured correctly or sending to output correctly. For example, when using this specific snippet: aria2c --on-download-complete="/tmp/notify.sh" -s16 -x16 <download-link> > /tmp/aria.log 2>&1 &

The input renders as: ? download-link> > /tmp/aria.log 2 and the output as: aria2c --on-download-complete="/tmp/notify.sh" -s16 -x16 <download-link>&1 &

Last, it also seems that only works with the-way cmd and not when using the default editor to create a snippet. Is that intended? If not, then is there a way to allow this? I can create the command prior to adding it as a snippet cmd, but it kind of seems like it would defeat the purpose for some. Not such a big deal though.

@Ninjani
Copy link
Member

Ninjani commented Nov 22, 2020

Oops looks like I messed up the regex. Pushing a fix now and should be working fine in the next version, thanks!

(Should be fixed in v0.12.1)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants