Re: [BUG] export blocks no longer fontifying [9.7.10 (release_9.7.10 @ /Users/ben/Scripts/emacs/lisp/org/)]

2024-11-04 Thread Benjamin McMillan
Yes, that seems to work. It returns: "The operation couldn’t be completed. Unable to locate a Java Runtime. Please visit http://www.java.com for information on installing Java. no" On Tue, Nov 5, 2024 at 5:11 AM Ihor Radchenko wrote: > Benjamin McMillan writes: > > > A c

Re: [BUG] export blocks no longer fontifying [9.7.10 (release_9.7.10 @ /Users/ben/Scripts/emacs/lisp/org/)]

2024-11-04 Thread Benjamin McMillan
ssible that the test suite takes this response to mean that java is available, even though it is not? On Mon, Nov 4, 2024 at 2:58 AM Ihor Radchenko wrote: > Benjamin McMillan writes: > > > Thank you! > > And you are right, I haven't installed java on this computer, and a &g

Re: [BUG] A call of (org-end-of-meta-data t) goes too far in a heading with only whitespace

2024-10-22 Thread Benjamin McMillan
Sure, here is the patch. On Sun, Oct 20, 2024 at 6:03 PM Ihor Radchenko wrote: > Benjamin McMillan writes: > > > Granted that it is not worth changing behavior of the function, would it > be > > reasonable to update the docstring? Something like > > "When option

Re: [BUG] A call of (org-end-of-meta-data t) goes too far in a heading with only whitespace

2024-10-19 Thread Benjamin McMillan
I confused the issue in my response, and want to clear it up. As you say, when the heading has no contents, "after metadata" is the next headline. However, my problem is if heading 1 contains several blank lines: * Heading 1 :PROPERTIES: :ID: 11 :END: * Heading 2 In this example, a call of

Re: [BUG] A call of (org-end-of-meta-data t) goes too far in a heading with only whitespace

2024-10-17 Thread Benjamin McMillan
d use of end-of-meta-data is an important part of that. (And apologies Ihor for resending this to you, I managed to not click reply-all the first time around.) On Sat, Oct 12, 2024 at 8:43 PM Ihor Radchenko wrote: > Benjamin McMillan writes: > > > Specifically, a call to (org-end-o

[BUG] A call of (org-end-of-meta-data t) goes too far in a heading with only whitespace

2024-10-04 Thread Benjamin McMillan
Specifically, a call to (org-end-of-meta-data t) with point at the > on the following tree will go all the way to the next heading. In contrast, a call to just (org-end-of-meta-data), without the FULL flag, will go to the beginning of heading content, as expected. * >heading * another heading T

Re: [BUG] export blocks no longer fontifying [9.7.10 (release_9.7.10 @ /Users/ben/Scripts/emacs/lisp/org/)]

2024-09-23 Thread Benjamin McMillan
t; [ Adding Org mailing list back to CC to keep the conversation public ] > > Benjamin McMillan writes: > > > Dear Ihor, > > I am happy to make the changes. > > I am not sure what exactly made the last commit message read like a new > > feature, but hopefully the fo

Re: [BUG] export blocks no longer fontifying [9.7.10 (release_9.7.10 @ /Users/ben/Scripts/emacs/lisp/org/)]

2024-09-17 Thread Benjamin McMillan
happy to submit a further patch. Thanks, Ben On Mon, Sep 16, 2024 at 11:27 PM Benjamin McMillan wrote: > Ok, I am happy to submit a patch. It would be my first, so I will have to > find time to make the commit properly. > > On Wed, Sep 11, 2024 at 1:59 AM Ihor Radchenko > wrote:

Re: [BUG] export blocks no longer fontifying [9.7.10 (release_9.7.10 @ /Users/ben/Scripts/emacs/lisp/org/)]

2024-09-16 Thread Benjamin McMillan
Ok, I am happy to submit a patch. It would be my first, so I will have to find time to make the commit properly. On Wed, Sep 11, 2024 at 1:59 AM Ihor Radchenko wrote: > Benjamin McMillan writes: > > > At some point in the last few months, org mode stopped fontifying my > > l

[BUG] export blocks no longer fontifying [9.7.10 (release_9.7.10 @ /Users/ben/Scripts/emacs/lisp/org/)]

2024-09-04 Thread Benjamin McMillan
At some point in the last few months, org mode stopped fontifying my latex export blocks. However, an older version of emacs on my computer still does fontify. (The difference is seen even opening emacs with the -q flag) It seems that there was a change to the function org-fontify-meta-lines-and-bl