[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: |
Sun, 01 Sep 2024 09:02:55 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
Leo Stein <leo.stein@gmail.com> writes:
> The last article I was on had 13 figures. Putting everything in one
> directory is very disorganized. Writing all the figures into one big
> PDF just adds unneeded complications. Using \graphicspath and just the
> individual file names (with no paths or extensions) works great!
Just to avoid misunderstandings: I believe there is a market for
\graphicspath, and it is an official macro provided by the graphics
bundle, I'm not arguing against it. I wanted to show workarounds for
the fact that the macro isn't supported in AUCTeX, and I have currently
no idea how to support it within AUCTeX. But as always, patches are
welcome to change the situation.
Best, Arash
- Re: Provide advice to ffap (find-file-at-point) from \input@path?,
Arash Esbati <=
- Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?], Leo Stein, 2024/09/16
- Re: Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?], Ikumi Keita, 2024/09/18
- Re: Parse graphicspath for searching [, Arash Esbati, 2024/09/18
- Re: Parse graphicspath for searching [, Ikumi Keita, 2024/09/18
- Re: Parse graphicspath for searching [, Arash Esbati, 2024/09/18
- Re: Parse graphicspath for searching [, Leo Stein, 2024/09/18
- Re: Parse graphicspath for searching [, Arash Esbati, 2024/09/18
- Re: Parse graphicspath for searching [, Leo Stein, 2024/09/18
- Re: Parse graphicspath for searching, Arash Esbati, 2024/09/19
- Re: Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?], Leo Stein, 2024/09/18