iquest parses queries with tabs in the where clause incorrectly. about irods_client_icommands

[tedgin]

How long have you known me, Terrell? By now you should know that my joy in life is passing insane crap to programs to see how they fail! ;-)

In seriousness, the use case is formatting iquest command calls in scripts so that they are more readable. When a iquest query gets too long, it improves readability to split the query over multiple lines. The second and subsequent lines are usually indented to show that they are continuations of the previous lines. Spaces could be used, but using tabs to indent benefits visually impaired readers. Please see https://dev.to/alexandersandberg/why-we-should-default-to-tabs-instead-of-spaces-for-an-accessible-first-environment-101f.

[trel]

We can probably coax the new parser in to handling this scenario.

I don't think we'll spend the time to get the old/current parser to learn new tricks.

[trel]

Interesting. Is the current behavior incorrect?

Or is it just that iquest could interpret a tab as a space?

How did you 'find' this? What is the use case for supporting tabs as a space?

[mcast]

I wish I had found this one! It's a bug that's discoverable by someone else changing your code in an editor that auto-tabifies...