Re: Parse graphicspath for searching

2024-10-15 Thread Leo Stein
Brilliant, thank you, Ikumi Keita! On Tue, Oct 15, 2024 at 4:19 AM Ikumi Keita wrote: > Hi Leo, > > OK, I committed your patch to the git repository with minimal > modification. Thank you again for your contribution! > > Regards, > Ikumi Keita > #StandWithUkraine #StopWarInUkraine > #Gaza #StopM

Re: Parse graphicspath for searching

2024-10-15 Thread Ikumi Keita
Hi Leo, OK, I committed your patch to the git repository with minimal modification. Thank you again for your contribution! Regards, Ikumi Keita #StandWithUkraine #StopWarInUkraine #Gaza #StopMassiveKilling #CeasefireNOW > Leo Stein writes: > Yes, just received yesterday! > On Tue, Oct 15, 2

Re: Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?]

2024-10-15 Thread Leo Stein
Yes, just received yesterday! On Tue, Oct 15, 2024, 00:16 Ikumi Keita wrote: > Hi Leo, > > Thank you for your cooperation. Have you received the reply from FSF > that tells your assignment process is complete? If not, please wait it > patiently; According to my experience, FSF copyright assignme

Re: Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?]

2024-10-14 Thread Ikumi Keita
Hi Leo, Thank you for your cooperation. Have you received the reply from FSF that tells your assignment process is complete? If not, please wait it patiently; According to my experience, FSF copyright assignment process can take several months. Regards, Ikumi Keita #StandWithUkraine #StopWarInUkr

Re: Parse graphicspath for searching

2024-09-19 Thread Arash Esbati
Leo Stein writes: > I saw multiple style files using `TeX-auto-add-regexp', but sorry, I > don't understand how this is related to multi-file documents. It is related because AUCTeX applies parsed information in a multi-file setup to all involved files. Suppose you have something like this: --

Re: Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?]

2024-09-18 Thread Leo Stein
I agree with you :) I won't let attempting to be perfect stand in the way of being useful. On Thu, Sep 19, 2024, 01:00 Ikumi Keita wrote: > Hi Leo, > > > Leo Stein writes: > > Probably not, but I didn't want to make any assumptions. One example > might > > be that a user includes a comment

Re: Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?]

2024-09-18 Thread Ikumi Keita
Hi Leo, > Leo Stein writes: > Probably not, but I didn't want to make any assumptions. One example might > be that a user includes a comment just before/after their > \graphicspath{...} command, reminding themselves of the syntax, e.g. > % The syntax for \graphicspath is \graphicspath{{path1

Re: Parse graphicspath for searching [

2024-09-18 Thread Leo Stein
I saw multiple style files using `TeX-auto-add-regexp', but sorry, I don't understand how this is related to multi-file documents. If this is explained clearly somewhere in the documentation, please let me know, but I haven't found it yet. On Wed, Sep 18, 2024 at 1:56 PM Arash Esbati wrote: > Le

Re: Parse graphicspath for searching [

2024-09-18 Thread Arash Esbati
Leo Stein writes: > Regarding multifile documents, do I understand correctly that this is > the job of reftex? No, this has nothing to do with RefTeX, it's exclusively AUCTeX's business to cater for completion candidates of graphics files. > It would indeed be nice to avoid regexing the whole d

Re: Parse graphicspath for searching [

2024-09-18 Thread Leo Stein
Hi all, Right, I was actually using the code in the patch I submitted, so it worked. Regarding multifile documents, do I understand correctly that this is the job of reftex? I know about its internals at all... do you have a recommended style/*.el files which plugs into reftex that I should look a

Re: Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?]

2024-09-18 Thread Leo Stein
Dear Ikumi, On Wed, Sep 18, 2024 at 1:37 AM Ikumi Keita wrote: > Hi Leo, > > > Leo Stein writes: > > Changing the subject of this thread because I went off on the tangent of > > making graphicx.el parse \graphicspath commands, so that extra paths > could > > be searched when prompting for \

Re: Parse graphicspath for searching [

2024-09-18 Thread Arash Esbati
Hi Keita, Ikumi Keita writes: >> Arash Esbati writes: >> I had a brief look at the patch. I think the change will not work in a >> .tex file when used like this: > >> \graphicspath{{eps/}{tiff/}} > > Hmm, is that so? The proposed function `LaTeX-parse-graphicspath' > returns expected res

Re: Parse graphicspath for searching [

2024-09-18 Thread Ikumi Keita
Hi Arash, > Arash Esbati writes: > I had a brief look at the patch. I think the change will not work in a > .tex file when used like this: > \graphicspath{{eps/}{tiff/}} Hmm, is that so? The proposed function `LaTeX-parse-graphicspath' returns expected result such as (#("eps/" 0 4 (face

Re: Parse graphicspath for searching [

2024-09-18 Thread Arash Esbati
Hi Keita, Ikumi Keita writes: > It basically looks good to me. I'd like to ask one question. It searches > for \graphicspath{...} repeatedly by > (while (re-search-forward graphicspath-regex nil t) > loop. Is it expected that \graphicspath{...} appears multiple times in a > document? I had a br

Re: Parse graphicspath for searching [was: Provide advice to ffap (find-file-at-point) from \input@path?]

2024-09-17 Thread Ikumi Keita
Hi Leo, > Leo Stein writes: > Changing the subject of this thread because I went off on the tangent of > making graphicx.el parse \graphicspath commands, so that extra paths could > be searched when prompting for \includegraphics. The patch is attached. I > assume there are things that I did