vdirsyncer VS miller

Have a look at vdirsyncer. Sync calendars to a local directory and then use eMacs to read them.

I found vdirsyncer which seems like a nice and promising idea similar to maildir which I already use with notmuch, even though it seems too opinionated and the support for Google calender seems largely untested/unsupported.

For getting ics files, have you seen vdirsyncer ?

On another topic, I maintain a tool to synchronise calendars (e.g.: events and todos) using CalDav (a standard HTTP-based protocol which a lot of calendar servers implement). I'm actually rewriting this in Rust full-time these days.

I used https://github.com/pimutils/vdirsyncer and made a cronjob for it on my host. The configuration is pretty simple - but always do a backup before testing! :)

Whatever CalDAV type calendar you go with (NextCloud and Radicale have been suggested here, Sabre/DAV, DAViCal and Baikal are other options), in case you need to sync calendars to it, you might want to look at vdirsyncer. This way, everyone can keep using his favorite app and you can still gather everything in once central place and have it all synced. Or you get everyone to set up DAVx5.

I have recently started organizing my calendars using `vdirsyncer` [vdirsyncer](https://github.com/pimutils/vdirsyncer)

Hm. Generally for folks who are familiar with the command line I suggest using vdirsyncer, a nifty little python program that lets you keep remote calendars in sync.

jq and miller[1] are essential parts of my toolbelt, right up there with awk and vim.

[1]: https://github.com/johnkerl/miller

> This works really well if your problem can be solved in one or two liners.

My personal comfort threshold is around the 100-line mark. It's even possible to write maintainable shell scripts up to 500 lines, but it mostly depends on the problem you're trying to solve, and the discipline of the programmer to follow best practices (use sane defaults, ShellCheck, etc.).

> It go bad very quickly when, say, you have two CSV files and want to join them the sql-way.

In that case we're talking about structured data, and, yeah, Perl or Python would be easier to work with. That said, depending on the complexity of the CSV, you can still go a long way with plain Bash with IFS/read(1) or tr(1) to split CSV columns. This wouldn't be very robust, but there are tools that handle CSV specifically[1], which can be composed in a shell script just fine.

So it's always a balancing act of being productive quickly with a shell script, or reaching out for a programming language once the tools aren't a good fit, or maintenance becomes an issue.

[1]: https://miller.readthedocs.io/

where mlr is from https://github.com/johnkerl/miller

if this class of problems (i.e., csv/tsv data) is your main target you may find miller (https://github.com/johnkerl/miller) much more useful in the long run

That said, you may be interested in Miller (https://github.com/johnkerl/miller) which provides similar capabilities for CSV, JSON, and XML files. It doesn't use a SQL grammar, but that's just the proverbial lipstick on the thing. I'm not the author, but I have used it and I see some parallels in use cases at the very least.

worth giving Miller a shot

CSV utilities (still haven't pick a favorite one...): https://github.com/harelba/q https://github.com/BurntSushi/xsv https://github.com/wireservice/csvkit https://github.com/johnkerl/miller