Hi Tim, > My recommendation would be to confirm if the problem exists in the org > bundled with Emacs 26 (9.1.1) and if it is, report this on the emacs > devel list, making it clear the issue does not exist with emacs > 25.3. This will at least allow Emacs devel to note that something which > it is changing is either buggy and needs more work or is an incompatible > change for org (and possibly other modes) which will need to be > added to the changes/News file and addressed by mode authors prior to 26 > being released.
This bug does indeed exist in the org bundled with emacs. Reporting this to emacs-devel sounds like a good plan, and I'll do so in a couple days to let anyone on the org mailing list have a chance to correct me if I'm doing anything wrong on the org side. But I do agree this looks like a bug in emacs core (even though I wansn't able to find the cause). -Jay
