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, -- Bastien
