[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Provide advice to ffap (find-file-at-point) from \input@path?
From: |
Arash Esbati |
Subject: |
Re: Provide advice to ffap (find-file-at-point) from \input@path? |
Date: |
Sat, 31 Aug 2024 18:41:23 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Leo Stein <leo.stein@gmail.com> writes:
> This is the first time I've seen that recommendation in epslatex.pdf
> (the most recent version on the CTAN is from 2006, and I don't think
> I've used an eps since around that time!).
I'd say epslatex.pdf is a good read for including graphics into .tex
files in general; the specifics about the EPS file format are not that
relevant anymore, probably.
> I find the recommendation of preferring to modify the environment
> variable TEXINPUTS pretty bizarre: when we submit latex sources to
> journals or the arXiv, we have no control over the environment
> variables of their build systems. Using \graphicspath is, AFAIK, the
> most robust way to keep your sources portable.
Or you could simply hardcode the path to the file inside
\includegraphics for this kind of rather small documents. Personally, I
think all this is relevant only if you're using the good old latex-dvips
route. With the advent of pdflatex, you can plonk all your graphics
into a single file and then use the 'page=X' key-val inside the optional
arg of \includegraphics; then you can have your single file with the
graphics in the same directory of your main-file.tex and all the
path-searching stuff isn't really necessary.
> This thread actually made me realize something I hadn't noticed
> before. I thought that AUCTeX had been parsing the contents of
> \graphicspath to search for files when you insert \includegraphics,
> but now looking at the source, I can't find this... did I imagine it?
> Did this ever happen in the past?
See Keita's answer.
Best, Arash