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

cannot have closed parentheses in inline function argument #13

Open
youbitchoc opened this issue Oct 25, 2022 · 0 comments
Open

cannot have closed parentheses in inline function argument #13

youbitchoc opened this issue Oct 25, 2022 · 0 comments

Comments

@youbitchoc
Copy link

youbitchoc commented Oct 25, 2022

The first ) after the start of an inline command is interpreted as the end.

For example,
^ca(1, echo "$(tty)" > randomfile)
is interpreted as
^ca( 1, echo "$(tty )
and the remaining " > randomfile) is printed as plaintext.

I haven't looked too deeply into how dzen handles this, probably with something like ^), but that'll burden the parser with more complexity than I'm comfortable with.

Maybe at this point I should be using a shellscript (that doesn't have ) in its name).

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

No branches or pull requests

1 participant