From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Friendly exchange of thoughts: citations and LaTeX
Date: Wed, 3 May 2023 07:00:04 +0200 [thread overview]
Message-ID: <BCC1769F-8B90-4E91-8EDB-F9C02CEDE0DA@gmail.com> (raw)
In-Reply-To: <87ednyew0z.fsf@localhost>
Hi Ihor,
sorry for being so silent, but I'm currently at 300% occupation. And statistical mux doesn't work well on human beings...
Marking this as TODO...
thx,/pa
Enviado desde mi iPad
> El 2 may 2023, a las 14:51, Ihor Radchenko <yantar92@posteo.net> escribió:
>
> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> One reasonable option could be keeping relative paths relative iff the
>> #+BIBLIOGRAPHY is derived from a file inside the same directory with the
>> exported file.
>>
>> Tentative patch attached.
>
> I applied an alternative patch that uses the approach from
> `org-export--update-included-link' - relative paths are resolved against
> top-level file dir and absolute paths are kept absolute.
>
> Handled.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=5ec364a1a
>
> --
> Ihor Radchenko // yantar92,
> Org mode contributor,
> Learn more about Org mode at <https://orgmode.org/>.
> Support Org development at <https://liberapay.com/org-mode>,
> or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2023-05-03 5:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 6:52 Friendly exchange of thoughts: citations and LaTeX Pedro Andres Aranda Gutierrez
2023-03-23 10:09 ` Fraga, Eric
2023-03-27 9:02 ` Pedro Andres Aranda Gutierrez
2023-03-27 9:34 ` Fraga, Eric
2023-03-27 14:37 ` Pedro Andres Aranda Gutierrez
2023-03-29 14:14 ` Ihor Radchenko
2023-03-29 16:50 ` Pedro Andres Aranda Gutierrez
2023-05-02 12:51 ` Ihor Radchenko
2023-05-03 5:00 ` Pedro Andres Aranda Gutierrez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BCC1769F-8B90-4E91-8EDB-F9C02CEDE0DA@gmail.com \
--to=paaguti@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.