Hacker News Reader

Comment by yewenjie | Hacker News Reader

Yes. Org mode is fantastic.

However, some limitations/ drawbacks.

- org-agenda is slow and completely unusable if you have hundreds of org files.

- despite multiple half-baked efforts there is still no easy-to-use parser and pretty printer for the lanuguage. I'm not even asking for 100% of the syntax, 20% capability of t he built-in org-element API with good documentatiom will accomplish 80% of the requirements.

- no easy way to integrate calendars and org-agenda with something like a calDav server.

View on HN

> no easy way to integrate calendars and org-agenda with something like a calDav server.

It would be great to have something like this.

I have a system which can at least handle invitations to events by means of a python script that convert iCal files to Org-style headers. It is triggered automatically via inotify so that every time a new iCal file appears into a specific folder it is appended automatically to an Org file. Now I simply save the .ics that comes attached to event invitation emails to have the time slot booked in my Org agenda automatically.

That last point is what gets me. I very much want my org-agenda to be linked to the calendar app on my phone. No easy way to do this, so far.

Agenda slowness is killing me. I need a solution, but honestly I feel like my next band-aid is probably an upgraded computer.

I create a new org file for each client, plus a few extras, and so at this point I have (ls -al | grep org$ | wc -l) 86 such files.

I could speed it up by doing more archiving, but it's useful to have history for long-running engagements in the main file vs the _archive files.

I may decide to move moribund/closed engagement files to a subfolder for cold-storage, but then there's the out-of-sight, out-of-mind problem.

OTOH, I never ever print from Org, and I use Exchange for calendaring, so the other two points aren't a problem for me, at least.

By the way, when ls isn’t printing to a terminal it defaults to one file name a line, so 'ls -a' would work fine here (and arguably be a bit more correct).

Good tip, but these days I'm so long removed from daily terminal incantations that I mostly take a "kitchen sink and just make it work" approach.

I've only recently started using org and haven't yet tried this, but I did research CalDav interop ahead of time and found https://github.com/dengste/org-caldav

JFYI, there's an excellent package org-ql which works quite nice with many org files. It has org-ql-view built in, which works like org-agenda.

(https://github.com/alphapapa/org-ql)

Reply on news.ycombinator.com