Erik Hollensbe
Erik Hollensbe
Spitting out that long URL is pretty annoying to cut and paste, so maybe we should just make it try to launch the default browser.
Gonna keep a running tally of perf issues to resolve. Most of this revolves around google calendar: - [ ] tokio/thread/sit function is very expensive; maybe some use of channels...
Without coming across as too frustrated, most of the issues with sui are related to the TUI toolkit not supporting async operation and all the workarounds I have had to...
If you add more than one notification period to a google calendar item, it will result in `400 Bad Request`. Probably a bug in the RRULE generator.
Not sure what is causing this yet; I'm pretty sure something that's handling errors isn't doing it right, though.
Not sure why this is, we're doing all the RRULE stuff so I need to look at the event information.
- attendees (#44 covers this already with some extra) - URLs - Locations - Maybe strip markup from extended descriptions and put them in here too
Several users have requested it.
`saturn next` would only output the next task in the list, regardless of time. If provided an integer (maybe a switch?) it will show the next N tasks.