"Jacob S. Gordon" <[email protected]> writes: > On 2026-08-24 08:36, J.D. Smith wrote: >> For me I don't get any of the invisible properties brought over to >> agenda. Is there a setting to achieve that? > > Nothing beyond ‘org-hide-emphasis-markers’, though there’s a few > existing limitations: > > 1. If the file is loaded by the agenda without visiting it first, > the markers will not be hidden: > > (setopt org-hide-emphasis-markers t > org-agenda-files '("/tmp/agenda.org")) > > M-x org-agenda > > Reloading with ‘g’ after font-lock kicks in will hide them. > > 2. Deadline entries never hide the markers, which I guess has > something to do with ‘org-agenda-deadline-faces’. > > 3. The emphasis appearance is lost. > > If I ever get the courage to change ‘org-agenda’, these are on my > list. > > Best,
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? 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. I wonder what the reason of avoiding font-lock in agenda buffers is?
