I think I fixed the problem, but in reading up on how to contribute I haven't gotten git setup yet or the FSF contribution form done. Should I do that first before sharing the patch with the group?
Meanwhile is there some sort of test suite to ensure contributions don't break existing features? ~>Bill On Thu, Apr 19, 2012 at 9:08 PM, Nick Dokos <nicholas.do...@hp.com> wrote: > Eric Schulte (cc:ed) implemented accumulating properties with commit > 3af89e696a32afcc39f2e3bdb6132ac588d530ae. The commit adds a function > org-update-property-plist which takes care of the '+' case in property > names. But as you observed, it does not seem to work. I don't really > understand what should be happening: what I do know is that when > org-entry-get calls the above function, the props parameter is nil, > whereas the function expects it to contain the inherited sestting. So it > may be that the function is expecting something that is not going to > happen or org-entry-get passes it the wrong thing somehow. I don't know > which > one of these two is correct (or perhaps some other thing is wrong), but > in any case there does seem to be a disconnect. > > Nick >
