Michael Hoffman

Upon reflection I think `--config=other.toml` is the best option as it makes it easiest for the uninitiated to understand what is going on, and enables config files outside the standard...

The `packages.config` file can only be used to install, not upgrade, and I don't see a way to get it to specify things like pins either.

There is now a repo at [michaelmhoffman/gcaledit](https://github.com/michaelmhoffman/gcaledit) showing how one can set up gcalcli `agenda` → `agendaupdate` workflows.

Renaming the subcommand is probably a good idea. I think reorganizing the list of subcommands to have several sets of commands, one for reading, one for writing, one for other,...

Yes, this would definitely be possible. I would love to see this! The workflow in (michaelmhoffman/gcaledit)[https://github.com/michaelmhoffman/gcaledit] does this with a desktop spreadsheet application instead, but doing it with Google Sheets...

In `gcalcli.gcal` there are a number of functions that are long repeats of conditional statements converting various details of events between the Google API format and a human-readable text format...

My suggestion for priority of refactoring is: 1. Refactor other cases where events are edited or patched (`edit`, `quick`, `add`) event to use `Handler.patch()` instead. This is the most compelling...