David Masterson <dsmasterson92...@outlook.com> writes: > Nick Dokos <ndo...@gmail.com> writes: > >> From what I can gather, this does not have much to do with Org mode >> proper, which has no org-agenda-property-list at all. I presume that >> you have >> >> https://github.com/Malabarba/org-agenda-property/blob/master/org-agenda-property.el >> >> installed, which does provide such a variable, but all that one can >> say atm is that that library has a bug *or* is incompatible with >> (current?) Org mode. In either case, I think you should report it as >> an issue to the above site. Once they have figured out what is wrong, >> then maybe an RFE against Org mode *might* be indicated. > > Ah! That makes sense. I'll look into it. >
You might be able to work around the problem by having org-agenda-property put the property on the same line: (setq org-agenda-property-position 'same-line) and adjusting the position on the line with (setq org-agenda-property-column 100) if necessary. If the infinite loop goes away in that case, then you have some confirmation of your theory about two-line agenda entries. -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler
