Hello all,
can anybody suggest what may be causing an error of the form:
org-odt-export-to-odt: OpenDocument export failed: FIXME: Unable to resolve
[...]
The very long error message gives no actual detail as to what actually
failed to resolve.
I will try with emacs -Q etc. but challenging due
Ignore please. I was trying to export an image which was in PDF; I
thought I had changed to reference to a PNG but missed one. Mind you,
the error message could be a little more informative?
Sorry for the noise.
--
: Eric S Fraga, with org release_9.6.7-661-g34ee6f in Emacs 30.0.50
When on an empty line before a source block, org-in-src-block-p
correctly returns nil.
However, when on an empty line after a source block, it returns t.
This is reproducible on my end with both the built-in version of
Org and 9.7-pre.
Yodel[1] Report 2023-11-27 10:42:54
==
No Wayman writes:
> When on an empty line before a source block, org-in-src-block-p
> correctly returns nil.
> However, when on an empty line after a source block, it returns t.
> This is reproducible on my end with both the built-in version of
> Org and 9.7-pre.
This is not a bug - Org consi
"Fraga, Eric" writes:
> Ignore please. I was trying to export an image which was in PDF; I
> thought I had changed to reference to a PNG but missed one. Mind you,
> the error message could be a little more informative?
AFAIU, that message is for fuzzy and id links that do not point to
heading
[ Adding Org mailing list back to CC ]
No Wayman writes:
>> This is not a bug - Org considers blank lines after element as a
>> part of
>> it. This includes source blocks.
>
> I would've reversed the semantics of the INSIDE argument.
> e.g.
>
> (defun org-in-src-block-p (&optional lax element)
[Apologies for the duplicate message, Ihor. mu4e recently changed it's default
reply behavior without my noticing]
Ihor Radchenko writes:
> This is very different from LAX argument in `org-at-timestamp-p' -
> timestamp-like text may not be proper syntactically correct Org markup
> element, but
No Wayman writes:
>> What about the attached patch?
>
> That is much clearer. Thank you.
Applied, onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=bd7fab212
>> If you want to check if point is inside source block code, use INSIDE
>> argument.
>
> Using the INSIDE argum
Triggered by a recent question here on `org-in-src-block-p' and a
current need: Is there a function already available that returns
the *inner* boundaries of an arbitrary block element?
For the element corresponding to the block below:
#+begin_verse
^A foo
bar
baz^B
#+end_verse
that function
Ihor Radchenko writes:
point on trailing blank line: FAIL
Fixed, on main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=6d7c7917a
Confirmed on my end by adding `:packages* org` to the previous
test:
Yodel[1] Report 2023-11-27 15:34:45
===
Jens Schmidt writes:
> Triggered by a recent question here on `org-in-src-block-p' and a
> current need: Is there a function already available that returns
> the *inner* boundaries of an arbitrary block element?
Nope. There is `org-src--contents-area', but it is not guaranteed to
work as it is a
I'm trying citations with the basic processor, and have found what seems to be a
problem with the "nb" (numeric) style: the citation has a number, but it's not
matched to anything in the bibliography.
Try this as Basic.bib:
@book{chassellIntro,
title = {An Introduction to Programming in {{Em
Hi there,
I have been trying to configure mbsync to download email from MS Outlook.
Unfortunately, the new oauth2 authentication makes things difficult, especially
since my institution has disabled the Azure App permission.
Does anybody have a workaround? I just want the email message to be l
Ignore this. To make the numbering appear in the bibliography, use this:
#+cite_export: basic numeric
I'm working my way through all the combinations and will submit some patches for
the documentation when I have it figured out more.
Bill
On 27 November 2023, William Denton wrote:
I'm try
Hi Ihor,
On Monday, 27 Nov 2023 at 19:49, Ihor Radchenko wrote:
> AFAIU, that message is for fuzzy and id links that do not point to
> heading or target - such links are not supported.
I've had this before when the target (i.e. the label within the org
file) did not exist. I have never seen this
15 matches
Mail list logo
