vdirsyncer VS the_silver_searcher

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.

View on GitHub

If you have trouble finding it among the other stuff happening in the server log, well, so do I! I recommend learning how to programmatically search through your terminal output. Providing a universal method for this is challenging because various tools and terminal emulators implement this functionality differently. Another option would be to use tools like grep or the_silver_searcher (a favorite of mine) to search the file where your dev logs are written to. This file is located at log/development.log in a Rails project.

Some of the examples below use ag, but could just as well use grep or equivalent.

Why guess when [there are installation instructions for various platforms on the README](https://github.com/ggreer/the_silver_searcher#installing)?

Also, although it may not be easy to remember, is this really a problem in practice given the installation count in most contexts is one? If there's a context where it's installed regularly, that's a one-time addition to an install script, Dockerfile, etc. in my experience. Do you have a situation that isn't amenable to that?

The kernel changes a lot, so the books would get outdated quickly. But you can find simple / similar drivers, and read the code. Usually there are some documentation / comments on the headers before the function declarations. The Elixir and the Silver Searcher will help a lot.

URL 🔗 : https://github.com/ggreer/the_silver_searcher

My "vim" way of finding all the places where a function is being used: using visual mode, marking the function, and passing it to :Ag (silversearcher) The problem with this is that it is not 100% accurate, since it will just look for things with the same name, so I was thinking about using the LSP to make things more robust.

We're fans of ag, The Silver Searcher.

Helm-ag is an interface to the ag, silver-searcher, so check the docs for ag. For example, ag automatically ignore some files if there is a .gitignore with some file patterns, or you could use .agignore.