Hello, I just noticed that adding a local bibliography for use by the
biblatex cite processor gets exported to latex as an absolute path.
`#+bibliography: main.bib` exports to
`\addbibresource{/home/me/etc/main.bib}`
I would like a setting to allow this to be a relative path if possible.
I
I am sending this report at the request of org's built in monitor. org mode
recovered gracefully and did not inconvenience me.
I have attached my configuration state report.
I was able to reproduce the bug twice by repeating the steps I outline below,
but when I went to capture a backtrace I r
Ihor Radchenko writes:
> No extra information for over a month.
> I assume that the problem disappeared.
> Closing.
> Canceled.
Yes, Ihor. I was unable to reproduce the issue despite continued use of
the offending file.
Thanks,
Panos
Hello. I'm very much an elisp amateur, but one of my main motives for
learning has been to make use of emacs' many beautiful UI systems.
Therefore, I'll provide my comments from a designer perspective and
avoid implementation detail.
Ihor Radchenko writes:
> TL;DR: We are in the process of de
Rens Oliemans writes:
> Ah, here we see the exact problem we've both just attested to! The #+RESULTS:
> code block
> got recreated because I was messing around with ':results' headers, and the
> #+ATTR_LATEX:
> line doesn't belong to the correct table anymore.
>
> You will notice that if you mo
While trying to set up a toy example for another thread, I stumbled into
a problem. It's been over a year since I did this, but I recall it was
possible to use multiple :results format values e.g.
:results output file link drawer
Using both link and drawer was acceptable with Emacs 28.2 Org mode
Ihor Radchenko writes:
> I just tried Org 9.5.5 and also Org 9.4.4. It is all the same -
> consistent with Org 9.7.11.
Thanks for the sanity check, Ihor. I must have had some piece of
configuration that enabled this for me -- Super useful, I'll share it if
I find it.
Might as well have been mag
