-
Notifications
You must be signed in to change notification settings - Fork 101
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
files list field separator does not allow tab character #52
Comments
NO '\t' => ' = meaning not include any variables and schemes skipp all and print |
I expect the output to be separated by tabs.
Output:
|
|
Unfortunately, It still doesn't work.
|
Please try this command
or
|
This command can work. However, it just workaround. Because '|||' is a valid filename. I think the safest approach is to use tab-separated TSV or comma-separated CSV (with quotes around strings when necessary). These are the most commonly used formats. |
You right. I just tried to find a quick and easy solution. |
I'm using version 3.9.0 on Debian Linux, executing
gdrive files list --full-name --skip-header
The output fields are separated by spaces, which I checked with "od". To eliminate the terminal as a potential complicating factor, I redirected to a file and then did a "od -c -t x1" on the file and it continued to show spaces between fields.
I tried
gdrive files list --full-name --skip-header --field-separator $'\t'
to force the separator to a tab but this did not change the behavior and spaces were still inserted between fields. Note that it is not a single space but it appears there is some calculation going on that is turning tabs into the appropriate number of spaces for display.
I tried specifying other field separators such as ';' and ' ' (single space) and 'Z'. These all resulted in output with a single instance of the specified separator being output between fields, as expected. Based on that, I am using a semi-colon as a workaround.
Am I doing something wrong or is this a bug?
The text was updated successfully, but these errors were encountered: