Skip to content
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

TUI flavor of gcalcli edit? #764

Open
dbarnett opened this issue Sep 17, 2024 · 2 comments
Open

TUI flavor of gcalcli edit? #764

dbarnett opened this issue Sep 17, 2024 · 2 comments

Comments

@dbarnett
Copy link
Collaborator

dbarnett commented Sep 17, 2024

When editing a long list of events, it feels clunky to go through per-event prompting to modify and save events one at a time. What if instead it supported an interactive TUI (text-based UI) where you could browse the entire list of events, stage edits to them, and then commit them to save all changes at once.

In other words, this would be like editing the set of events visually in vi vs. ed.

That kind of TUI interface would offer a few advantages over the current line-based interface:

  1. More forgiving experience if you e.g. started editing a few, changed your mind, and wanted to abort and start the whole edit over with different parameters
  2. More convenient if you want to only edit a couple individual fields without going through prompts for all the others
  3. Could offer more intuitive controls for batch operations like "add reminder xyz on just these 7 events in the list"
  4. Could allow for better ad hoc searching/filtering within the TUI, for a richer browsing+editing experience across your events
@michaelmhoffman
Copy link
Collaborator

michaelmhoffman commented Sep 18, 2024

I use gcalcli agenda --tsv, open the result in Microsoft Excel, make bulk changes, and then use gcalcli agendaupdate to write it back.

@dbarnett
Copy link
Collaborator Author

Neat, I didn't realize that's what the agendaupdate command did!

Still some advantages of doing edits completely inline in something like a TUI w/o separate intermediate files, like having a more convenient flow for exploring and updating very large sets of event data interactively w/o having to craft cli args upfront to filter the data down manually.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants