On 2026-08-26 11:45, J.D. Smith wrote: > Ahah, interesting. So it just copies the properties over from a live > buffer if present? I don't myself see that behavior. Even if a > buffer is live and loaded, and `org-hide-emphasis-markers=t`, > emphasis markers are not hidden with TODO-based agendas. I wonder > what the difference could be?
Hmm, if it’s not one of those cases then I’m not sure why. Anyone else seeing this? > But even if it did work, this is of course not ideal. Even if a > buffer is loaded, font-lock may be deferred for large parts. > Performing font-lock "just in time" works great. `consult-line` > (which can pull 10's of thousands of lines from dozens of buffers) > switched to that approach, and it dramatically reduced the startup > penalty. Oh that’s interesting, I didn’t know you could fontify selectively with ‘jit-lock-fontify-now’. I have some local patches which keep text properties in the ‘imenu’ indexes, but suffers from the same issue, so this will help (or maybe I should just use ‘consult’!). -- Jacob S. Gordon [email protected] Please don’t send me HTML emails or MS Office/Apple iWork documents. https://useplaintext.email/#etiquette https://www.fsf.org/campaigns/opendocument
