luckman212 Posted November 22, 2019 Share Posted November 22, 2019 I'm trying to split my {query} into separate vars based on the [TAB] delimiter (usually represented in regex by "\t") I want to use the new Split Argument to Variables Utility workflow object for this: It doesn't seem to work. Works fine with other delims such as comma and pipe("|") Is there a way to do this, is this a bug, or am I "doing it wrong" ? Thanks Link to comment Share on other sites More sharing options...
Andrew Posted November 22, 2019 Share Posted November 22, 2019 @luckman212 try pasting a tab character into the Delimiter box, then it should work as expected Link to comment Share on other sites More sharing options...
luckman212 Posted November 22, 2019 Author Share Posted November 22, 2019 Thanks @Andrew I ended up using a pipe instead but — since this tab char would be invisible, wouldn't it be more sensible to use things like \t or \n for readability? deanishe 1 Link to comment Share on other sites More sharing options...
Terminal Posted December 29, 2019 Share Posted December 29, 2019 On 11/22/2019 at 4:11 PM, luckman212 said: Thanks @Andrew I ended up using a pipe instead but — since this tab char would be invisible, wouldn't it be more sensible to use things like \t or \n for readability? @Andrew I second this, I’d put this low on the “to-do” list. But I think it would be more intuitive. Link to comment Share on other sites More sharing options...
deanishe Posted December 29, 2019 Share Posted December 29, 2019 7 hours ago, Terminal said: But I think it would be more intuitive. Agree. \t and \n are what you'd typically expect to work. They're also a lot clearer than invisible whitespace. Link to comment Share on other sites More sharing options...
Andrew Posted December 30, 2019 Share Posted December 30, 2019 I'll add a note to think about this, as I agree, \t and \n are much more clear. Terminal and luckman212 2 Link to comment Share on other sites More sharing options...
vitor Posted March 27, 2020 Share Posted March 27, 2020 Moving this to Feature Requests, as it seems more fitting there and is being considered. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now