Nicolas Goaziou <m...@nicolasgoaziou.fr> writes: > Hello, > > Rainer Stengele <rainer.steng...@online.de> writes: > >> These posts which stay unanswered - either they are too stupid or too >> complicated?! > > AFAIC, questions about the Agenda tend to belong to the second > category.
Indeed! :) >> Anybody an idea, a hint? > > It may help to know what you have tried so far. For example, how is your > block configuration, including the settings part (see > `org-agenda-custom-commands' docstring)? > > Note that it might not be possible to achieve what you want. Probably the way to do it would be to wrap the agenda code which operates on certain files, and let-bind the org-agenda-done face around that code depending on which file it is. That would probably require copying the function in question and overriding it with advice. Certainly doable (on first glance, anyway), but not easy for someone unfamiliar with elisp or the agenda code. I would guess that a more general solution, which could bind certain variables to certain values depending on which file the agenda is being constructed from, could be useful in other ways as well. It might be possible to integrate this with org-agenda-custom-commands, or in a customizeable variable mapping files to lists of variables, to make it fairly straightforward to use.
