Hi Bastien I feel that your proposal to first create the agenda using the standard `org-agenda-format-item' function and then to replace all lines again, by calling a suitable function added to `org-agenda-finalize-hook' is not very efficient.
but, since you agree that when `org-agenda-property-list' is nil no harm is done, and if your objection mostly is about the name, then how about `org-agenda-overriding-format-item-function' Best, Thomas ps: I would volunteer to assist users who copy stuff from the web and of course also deliver documentation and examples for `org-agenda-property-list'. Bastien <b...@altern.org> writes: > Hi Thomas, > > Thomas Alexander Gerds <t...@biostat.ku.dk> writes: > >> thanks for looking into this! I understand your general point of >> view. however, the proposed changes would only slow down agenda creating >> if org-agenda-property-list is set, right? > > Right. > >> also, it certainly requires some insights to write >> org-agenda-overriding-agenda-format which could display non-special > > (`org-agenda-overriding-agenda-format' is a confusing name IMHO.) > >> properties. hence only a user who knows what she/he is doing would run >> into this problem. > > Many users just copy stuff from the web, and some are not really > knowing what they do. > >> anyway, could you propose a different approach to get this >> extension? > > You can write a function for `org-agenda-finalize-hook' which would go > through the agenda lines, get the properties and display them. > > That's a far better approach. > >> ps: one limitation of org-agenda-columns seems to be that columns >> cannot be activated in two different agenda buffers simulaneously. > > Yes, we can work on this. > > Best, -- Thomas A. Gerds -- Assoc. Prof. Department of Biostatistics University of Copenhagen, Øster Farimagsgade 5, 1014 Copenhagen, Denmark Office: CSS-15.2.07 (Gamle Kommunehospital) tel: 35327914 (sec: 35327901)
