Re: [O] Regression in #+include behavior [master]

On Tue, Mar 20, 2018 at 3:53 AM Nicolas Goaziou wrote: > > The code was fixing links in the whole document, not only in the subtree > you were including. > > The problem lay somewhere else in the file, in the "* Hey! I have a link > [[https://example.org][here]]

Re: [O] Regression in #+include behavior [master]

Hello, Kaushal Modi writes: > Though I didn't understand why it failed when exporting from the large > file, but not when moving the relevant subtrees (where the #+include was > called, and the included) to a separate file.. The code was fixing links in the whole

Re: [O] Regression in #+include behavior [master]

On Mon, Mar 19, 2018 at 6:52 PM Nicolas Goaziou wrote: > > Fixed. Thank you. > Hello, Thank you for quickly fixing this. Though I didn't understand why it failed when exporting from the large file, but not when moving the relevant subtrees (where the #+include was

Re: [O] Regression in #+include behavior [master]

Hello, Kaushal Modi writes: > I believe a regression was introduced in > https://code.orgmode.org/bzg/org-mode/commit/d81a1d088c74e605c99e90a2835c55df5144f43e > > I am unable to come with a minimal example, but I can link to the actual > Org file that causes the

Re: [O] Regression in #+include behavior [master]

On Mon, Mar 19, 2018 at 4:00 PM Kaushal Modi wrote: > Hello, > > I believe a regression was introduced in > https://code.orgmode.org/bzg/org-mode/commit/d81a1d088c74e605c99e90a2835c55df5144f43e > Actually the commit before that would have been the breaking commit as I

[O] Regression in #+include behavior [master]

Hello, I believe a regression was introduced in https://code.orgmode.org/bzg/org-mode/commit/d81a1d088c74e605c99e90a2835c55df5144f43e I am unable to come with a minimal example, but I can link to the actual Org file that causes the failure. If I try to move that subtree along with the "included"