emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Friendly exchange of thoughts: citations and LaTeX
Date: Mon, 27 Mar 2023 11:02:07 +0200	[thread overview]
Message-ID: <DB11716B-A5D3-438A-88CD-8511E9F91D27@gmail.com> (raw)
In-Reply-To: <87pm8ziy6x.fsf@ucl.ac.uk>

Hi Eric,

\jobname is the shorthand for ‘the file that you are compiling with the latex command’. I use it in my templates for LaTEX presentations and documents I conjunction with \addbibresource{} 
I always have a main.Tex + main.bib file pair.

Recognizing this in org-cite would be nice.

Re the use of absolute vs relative path when exporting to LaTeX, I might want to export to LaTeX and transfer to overleaf.com and relative paths would make more sense there, wouldn’t they?

Thanks for the exchange/PA

Enviado desde mi iPhone

> El 23 mar 2023, a las 11:09, Fraga, Eric <e.fraga@ucl.ac.uk> escribió:
> 
> Pedro,
> 
> maybe start by showing an example of where \jobname does not work with
> org while working with LaTeX directly?  I have never used this LaTeX
> command and know nothing about it.
> 
> Secondly, what is the problem with bibliography file names being
> expanded?
> 
> eric
> -- 
> : Eric S Fraga, with org release_9.6.1-224-g8ae8a8 in Emacs 30.0.50

next prev parent reply	other threads:[~2023-03-27  9:03 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 [this message]
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

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

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DB11716B-A5D3-438A-88CD-8511E9F91D27@gmail.com \
    --to=paaguti@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).