Michael Hoffman

I hope that before it stops working, there will be a simple and accepted way to solve this! Google's documentation is, as usual, relatively impenetrable.

@gopromaster Thanks for the tip on google-auth! If anyone can verify that switching will fix this, that information would be greatly appreciated. As would a pull request.

Would support XDG used by default for new installations. The [xdg](https://pypi.org/project/xdg/) Python package makes it easy to use the XDG standard.

@ewen-lbh I'm not familiar with the Google Tasks API (or even Tasks as an end-user at all) unfortunately. Skimming the API it does not seem like there is a lot...

I don't have time to get familiar with that part of the codebase and review but I agree with your description of the desired behavior. Basically I think this should...

@jcrowgey Could you let me know what you think of this design?

To get the TSV output of `gcalcli agenda` to work automatically in Microsoft Excel with non-ASCII characters, it is necessary to set `PYTHONIOENCODING=utf_16`. Things that don't work `utf_16_le` (no BOM)...

The easiest way to use a UTF-16 `file.tsv` is to use input redirection with the `PYTHONIOENCODING` environment variable set. There's no user-accessible way to change the encoding of what's read...

The output of `PYTHONIOENCODING=utf_16 gcalcli agenda` isn't easy to use some other Unix tools like grep with. Instead you can use `iconv --to-code=utf-16` as part of a pipeline. For example:...

Thanks, making a `tox.local.ini` with added dependency on `pypandoc` and using `tox -c tox.local.ini` fixes the first problem. Your solution to problem 2 looks good to me.