proper shell parsing or something to not be confused by > and |

[Dieterbe]

> and | are used in influx-cli to redirect to file, and pipe to an external command, just like a shell does.
the way this is currently parsed, is a bit clunky though, and bugs arise when people have bigger-then conditions in their query or | as part of a regex.
we need something more robust to separate the query/command from the redirect/pipe stuff.
while we're add it, it would be great if we could do something like cmd | grep | sed | whatever > bar.txt
to make stuff like this possible, we should probably look at shell libraries and such things.

[abh]

One work-around would be to have an option to disable the "shell redirect" features. I never use them and I often have to not use influx-cli because I can't have multiple "> conditions".

[abh]

Actually, better just remove those features. I don't understand the value. If I want to use the shell I should just run influx-cli from the shell and use my shell's features for those things.

[Dieterbe]

fair point, iam sometimes in the middle of a session when i want to use these features and it's annoying to go out, run a shell command and then go back in . but they are causing too much brokenness right now.. maybe we should use different characters as long as we don't have a proper parser

[abh]

I think the MySQL client uses the comment terminator (“;”, “\G”, etc) to specify output options like that.=

[Dieterbe]

aha that seems like a nice and simple fix

[Dieterbe]

now it's only activated on ; | and ; > :)