3 ms·
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
by ubermonkey 5y ago
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.
- gnubison 5y agoBy 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).
- ubermonkey 5y agoGood 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.