Find files in subdirectories to use with input The 2019 Stack Overflow Developer Survey Results Are InCan LaTeX automatically search directories and include discovered files?Processing input filesFilehook, with more included filesLoop to include multiple filesCan filecontents write an external file in a parent directory?Modular Documents, including image from other LaTeX-Projecthow to have an easily transferable LaTeX environment?Does LaTeX support including a specific part of an input, like a specific environment and ignoring everything else?What's Happening With My Path After Upgrade to El Capitan?Include standalone files in subdirectories which read other files

Protecting Dualbooting Windows from dangerous code (like rm -rf)

Can we generate random numbers using irrational numbers like π and e?

Origin of "cooter" meaning "vagina"

Reference request: Oldest number theory books with (unsolved) exercises?

How to deal with speedster characters?

Is flight data recorder erased after every flight?

Why hard-Brexiteers don't insist on a hard border to prevent illegal immigration after Brexit?

A poker game description that does not feel gimmicky

Falsification in Math vs Science

Why didn't the Event Horizon Telescope team mention Sagittarius A*?

Is there a symbol for a right arrow with a square in the middle?

Apparent duplicates between Haynes service instructions and MOT

How to answer pointed "are you quitting" questioning when I don't want them to suspect

FPGA - DIY Programming

Delete all lines which don't have n characters before delimiter

If a Druid sees an animal’s corpse, can they Wild Shape into that animal?

How can I autofill dates in Excel excluding Sunday?

Pokemon Turn Based battle (Python)

Can a flute soloist sit?

Why is the maximum length of OpenWrt’s root password 8 characters?

Is an up-to-date browser secure on an out-of-date OS?

How are circuits which use complex ICs normally simulated?

Deal with toxic manager when you can't quit

Identify boardgame from Big movie



Find files in subdirectories to use with input



The 2019 Stack Overflow Developer Survey Results Are InCan LaTeX automatically search directories and include discovered files?Processing input filesFilehook, with more included filesLoop to include multiple filesCan filecontents write an external file in a parent directory?Modular Documents, including image from other LaTeX-Projecthow to have an easily transferable LaTeX environment?Does LaTeX support including a specific part of an input, like a specific environment and ignoring everything else?What's Happening With My Path After Upgrade to El Capitan?Include standalone files in subdirectories which read other files










1















Is there a way to have TeX find all files ending on .tex in subdirectories of a certain directory to be used as input?



In my document I would like to include a large number of files from a directory-tree which looks like this:



/transcripts/2013-05/2013-05-12/2013-05-12-transcript1/2013-05-12-transcript1.tex
/2013-05-12-transcript2/2013-05-12-transcript2.tex
/2013-05-14/2013-05-14-transcript1/2013-05-14-transcript1.tex
/2013-06/2013-06-07/2013-06-07-transcript1/2013-06-07-transcript1.tex


I know I can define specific directories with



makeatletter
definput@path./transcripts/./transcripts/2013-05
makeatother


but it would be nice to be able to tell it something like



./transcripts/*/*/*/


Is there any way how to achieve this?



I know that this question addresses a similar issue. However, I don't want to automatically include the files, they will still be specified by `inputfilename:



documentclassarticle 
begindocument

input2013-05-12-transcript1.tex
...
input2013-05-12-transcript2.tex

enddocument


What I'd like to achieve is to be able to only type the name and not have to type the entire filepath every time.



EDIT: As per the suggestion below I have tried to edit /usr/local/texlive/2015/texmf.cnf by adding TEXINPUTS = /path/to/folder//: so that it would search my folders recursively, but clearly I am missing some basic knowledge about how to do that. Anyone able to help me with this?



EDIT2 (2019):
I'm coming back to this question from a while ago:



(a) I haven't been able to get David's answer below to work. Any further help would be appreciated.
(b) I would also still like to find a portable solution, to be specified in the preamble of the document itself. Any ideas?










share|improve this question




























    1















    Is there a way to have TeX find all files ending on .tex in subdirectories of a certain directory to be used as input?



    In my document I would like to include a large number of files from a directory-tree which looks like this:



    /transcripts/2013-05/2013-05-12/2013-05-12-transcript1/2013-05-12-transcript1.tex
    /2013-05-12-transcript2/2013-05-12-transcript2.tex
    /2013-05-14/2013-05-14-transcript1/2013-05-14-transcript1.tex
    /2013-06/2013-06-07/2013-06-07-transcript1/2013-06-07-transcript1.tex


    I know I can define specific directories with



    makeatletter
    definput@path./transcripts/./transcripts/2013-05
    makeatother


    but it would be nice to be able to tell it something like



    ./transcripts/*/*/*/


    Is there any way how to achieve this?



    I know that this question addresses a similar issue. However, I don't want to automatically include the files, they will still be specified by `inputfilename:



    documentclassarticle 
    begindocument

    input2013-05-12-transcript1.tex
    ...
    input2013-05-12-transcript2.tex

    enddocument


    What I'd like to achieve is to be able to only type the name and not have to type the entire filepath every time.



    EDIT: As per the suggestion below I have tried to edit /usr/local/texlive/2015/texmf.cnf by adding TEXINPUTS = /path/to/folder//: so that it would search my folders recursively, but clearly I am missing some basic knowledge about how to do that. Anyone able to help me with this?



    EDIT2 (2019):
    I'm coming back to this question from a while ago:



    (a) I haven't been able to get David's answer below to work. Any further help would be appreciated.
    (b) I would also still like to find a portable solution, to be specified in the preamble of the document itself. Any ideas?










    share|improve this question


























      1












      1








      1


      2






      Is there a way to have TeX find all files ending on .tex in subdirectories of a certain directory to be used as input?



      In my document I would like to include a large number of files from a directory-tree which looks like this:



      /transcripts/2013-05/2013-05-12/2013-05-12-transcript1/2013-05-12-transcript1.tex
      /2013-05-12-transcript2/2013-05-12-transcript2.tex
      /2013-05-14/2013-05-14-transcript1/2013-05-14-transcript1.tex
      /2013-06/2013-06-07/2013-06-07-transcript1/2013-06-07-transcript1.tex


      I know I can define specific directories with



      makeatletter
      definput@path./transcripts/./transcripts/2013-05
      makeatother


      but it would be nice to be able to tell it something like



      ./transcripts/*/*/*/


      Is there any way how to achieve this?



      I know that this question addresses a similar issue. However, I don't want to automatically include the files, they will still be specified by `inputfilename:



      documentclassarticle 
      begindocument

      input2013-05-12-transcript1.tex
      ...
      input2013-05-12-transcript2.tex

      enddocument


      What I'd like to achieve is to be able to only type the name and not have to type the entire filepath every time.



      EDIT: As per the suggestion below I have tried to edit /usr/local/texlive/2015/texmf.cnf by adding TEXINPUTS = /path/to/folder//: so that it would search my folders recursively, but clearly I am missing some basic knowledge about how to do that. Anyone able to help me with this?



      EDIT2 (2019):
      I'm coming back to this question from a while ago:



      (a) I haven't been able to get David's answer below to work. Any further help would be appreciated.
      (b) I would also still like to find a portable solution, to be specified in the preamble of the document itself. Any ideas?










      share|improve this question
















      Is there a way to have TeX find all files ending on .tex in subdirectories of a certain directory to be used as input?



      In my document I would like to include a large number of files from a directory-tree which looks like this:



      /transcripts/2013-05/2013-05-12/2013-05-12-transcript1/2013-05-12-transcript1.tex
      /2013-05-12-transcript2/2013-05-12-transcript2.tex
      /2013-05-14/2013-05-14-transcript1/2013-05-14-transcript1.tex
      /2013-06/2013-06-07/2013-06-07-transcript1/2013-06-07-transcript1.tex


      I know I can define specific directories with



      makeatletter
      definput@path./transcripts/./transcripts/2013-05
      makeatother


      but it would be nice to be able to tell it something like



      ./transcripts/*/*/*/


      Is there any way how to achieve this?



      I know that this question addresses a similar issue. However, I don't want to automatically include the files, they will still be specified by `inputfilename:



      documentclassarticle 
      begindocument

      input2013-05-12-transcript1.tex
      ...
      input2013-05-12-transcript2.tex

      enddocument


      What I'd like to achieve is to be able to only type the name and not have to type the entire filepath every time.



      EDIT: As per the suggestion below I have tried to edit /usr/local/texlive/2015/texmf.cnf by adding TEXINPUTS = /path/to/folder//: so that it would search my folders recursively, but clearly I am missing some basic knowledge about how to do that. Anyone able to help me with this?



      EDIT2 (2019):
      I'm coming back to this question from a while ago:



      (a) I haven't been able to get David's answer below to work. Any further help would be appreciated.
      (b) I would also still like to find a portable solution, to be specified in the preamble of the document itself. Any ideas?







      external-files filesystem-access






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jan 6 at 19:17







      jan

















      asked Apr 28 '16 at 7:55









      janjan

      1,0681519




      1,0681519




















          2 Answers
          2






          active

          oldest

          votes


















          2














          Don't bother with input@path just set the texmf.cnf or environment variable TEXINPUTS to be



          input/transcripts//:


          the trailing // means to recursively search subdirectories and the : (or ; on windows) means just prepend this search path to the existing default, so all the standard places are still searched.






          share|improve this answer























          • Would you mind expanding on how exactly to change texmf.cnf? I tried to add TEXINPUTS = ~/path/to/input//: to the users texmf.cnf in /usr/local/texlive/2015/ but it still won't find the files. What am I doing wrong?

            – jan
            Apr 28 '16 at 9:03












          • Sorry, I still couldn't get it to work. Is changing texmf.cnf in /usr/local/texlive/2015/ what you meant?

            – jan
            Apr 29 '16 at 4:08











          • @jan if you set it in texmf.cnf you need to set the whole thing rather than just .//: as that is where it's set, in the file returned by kpsewhich texmf.cnf or on the command line (with a shell such as bash) you can simply do TEXINPUTS=.//: pdflatex yourfile.tex also kpsexpand '$TEXINPUTS' will show the currently active setting

            – David Carlisle
            Apr 29 '16 at 8:28












          • Hmm, I still don't seem to get it. kpsewhich texmf.cnf gives me /usr/local/texlive/2015/texmf.cnf as expected. Now I've added TEXINPUTS = /path/to/folder//: to that file. kpsexpand '$TEXINPUTS' gives me exactly that path. But when compiling it still doesn't find it.

            – jan
            Apr 29 '16 at 9:06


















          0














          I've recreated your file structure and this works for me:



          transcripts/
          ├── 2013-05
          │   ├── 2013-05-12
          │   │   ├── 2013-05-12-transcript1
          │   │   │   └── 2013-05-12-transcript1.tex
          │   │   └── 2013-05-12-transcript2
          │   │   └── 2013-05-12-transcript2.tex
          │   └── 2013-05-14
          │   └── 2013-05-14-transcript1
          │   └── 2013-05-14-transcript1.tex
          └── 2013-06
          └── 2013-06-07
          └── 2013-06-07-transcript1
          └── 2013-06-07-transcript1.tex


          The file 2013-05-12-transcript1.tex is textbfFirst, file 2013-05-12-transcript2.tex is textbfSecond, file 2013-05-14-transcript1.tex is textbfThird, file 2013-05-14-transcript1.tex is textbfFourth, and the example file is as follows:



          % arara: pdflatex
          documentclassarticle
          begindocument

          input2013-05-12-transcript1.tex
          ...
          input2013-05-12-transcript2.tex
          ...
          input2013-05-14-transcript1.tex
          ...
          input2013-06-07-transcript1.tex

          enddocument


          Windows



          I've saved it in D:transcripts



          Temporary configuration



          Open a command line cmd (you do not need administrator privileges) and you execute:



          set TEXINPUTS=D:/transcripts//;
          pdflatex sampleforum.tex


          this will work until you close the command line, that is, you must execute the line every
          time after close a command line ... tedious ... yes.



          Permanent configuration



          Open a command line cmd (you do not need administrator privileges) and execute:



          setx TEXINPUTS D:/transcripts//;


          close command line and open a new and execute:



          reg query HKEY_CURRENT_USEREnvironment
          pdflatex sampleforum.tex


          In this way we have configured the environment variable and now it is permeating.



          And to delete TEXINPUTS from environment variable, just use:



          reg delete HKEY_CURRENT_USEREnvironment /v TEXINPUTS /f


          Alternatively this can be done in a graphical mode adjusting your environment variable .



          Linux



          I've saved it in ~/transcripts



          Add to our file .bashrc the line:



          export TEXINPUTS='~/transcripts//:'


          Another option would be to use tlmgr conf auxtrees, but the directory would have in TDS form.



          Saludos





          share























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "85"
            ;
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function()
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled)
            StackExchange.using("snippets", function()
            createEditor();
            );

            else
            createEditor();

            );

            function createEditor()
            StackExchange.prepareEditor(
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader:
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            ,
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            );



            );













            draft saved

            draft discarded


















            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f306790%2ffind-files-in-subdirectories-to-use-with-input%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2














            Don't bother with input@path just set the texmf.cnf or environment variable TEXINPUTS to be



            input/transcripts//:


            the trailing // means to recursively search subdirectories and the : (or ; on windows) means just prepend this search path to the existing default, so all the standard places are still searched.






            share|improve this answer























            • Would you mind expanding on how exactly to change texmf.cnf? I tried to add TEXINPUTS = ~/path/to/input//: to the users texmf.cnf in /usr/local/texlive/2015/ but it still won't find the files. What am I doing wrong?

              – jan
              Apr 28 '16 at 9:03












            • Sorry, I still couldn't get it to work. Is changing texmf.cnf in /usr/local/texlive/2015/ what you meant?

              – jan
              Apr 29 '16 at 4:08











            • @jan if you set it in texmf.cnf you need to set the whole thing rather than just .//: as that is where it's set, in the file returned by kpsewhich texmf.cnf or on the command line (with a shell such as bash) you can simply do TEXINPUTS=.//: pdflatex yourfile.tex also kpsexpand '$TEXINPUTS' will show the currently active setting

              – David Carlisle
              Apr 29 '16 at 8:28












            • Hmm, I still don't seem to get it. kpsewhich texmf.cnf gives me /usr/local/texlive/2015/texmf.cnf as expected. Now I've added TEXINPUTS = /path/to/folder//: to that file. kpsexpand '$TEXINPUTS' gives me exactly that path. But when compiling it still doesn't find it.

              – jan
              Apr 29 '16 at 9:06















            2














            Don't bother with input@path just set the texmf.cnf or environment variable TEXINPUTS to be



            input/transcripts//:


            the trailing // means to recursively search subdirectories and the : (or ; on windows) means just prepend this search path to the existing default, so all the standard places are still searched.






            share|improve this answer























            • Would you mind expanding on how exactly to change texmf.cnf? I tried to add TEXINPUTS = ~/path/to/input//: to the users texmf.cnf in /usr/local/texlive/2015/ but it still won't find the files. What am I doing wrong?

              – jan
              Apr 28 '16 at 9:03












            • Sorry, I still couldn't get it to work. Is changing texmf.cnf in /usr/local/texlive/2015/ what you meant?

              – jan
              Apr 29 '16 at 4:08











            • @jan if you set it in texmf.cnf you need to set the whole thing rather than just .//: as that is where it's set, in the file returned by kpsewhich texmf.cnf or on the command line (with a shell such as bash) you can simply do TEXINPUTS=.//: pdflatex yourfile.tex also kpsexpand '$TEXINPUTS' will show the currently active setting

              – David Carlisle
              Apr 29 '16 at 8:28












            • Hmm, I still don't seem to get it. kpsewhich texmf.cnf gives me /usr/local/texlive/2015/texmf.cnf as expected. Now I've added TEXINPUTS = /path/to/folder//: to that file. kpsexpand '$TEXINPUTS' gives me exactly that path. But when compiling it still doesn't find it.

              – jan
              Apr 29 '16 at 9:06













            2












            2








            2







            Don't bother with input@path just set the texmf.cnf or environment variable TEXINPUTS to be



            input/transcripts//:


            the trailing // means to recursively search subdirectories and the : (or ; on windows) means just prepend this search path to the existing default, so all the standard places are still searched.






            share|improve this answer













            Don't bother with input@path just set the texmf.cnf or environment variable TEXINPUTS to be



            input/transcripts//:


            the trailing // means to recursively search subdirectories and the : (or ; on windows) means just prepend this search path to the existing default, so all the standard places are still searched.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Apr 28 '16 at 8:11









            David CarlisleDavid Carlisle

            498k4111441893




            498k4111441893












            • Would you mind expanding on how exactly to change texmf.cnf? I tried to add TEXINPUTS = ~/path/to/input//: to the users texmf.cnf in /usr/local/texlive/2015/ but it still won't find the files. What am I doing wrong?

              – jan
              Apr 28 '16 at 9:03












            • Sorry, I still couldn't get it to work. Is changing texmf.cnf in /usr/local/texlive/2015/ what you meant?

              – jan
              Apr 29 '16 at 4:08











            • @jan if you set it in texmf.cnf you need to set the whole thing rather than just .//: as that is where it's set, in the file returned by kpsewhich texmf.cnf or on the command line (with a shell such as bash) you can simply do TEXINPUTS=.//: pdflatex yourfile.tex also kpsexpand '$TEXINPUTS' will show the currently active setting

              – David Carlisle
              Apr 29 '16 at 8:28












            • Hmm, I still don't seem to get it. kpsewhich texmf.cnf gives me /usr/local/texlive/2015/texmf.cnf as expected. Now I've added TEXINPUTS = /path/to/folder//: to that file. kpsexpand '$TEXINPUTS' gives me exactly that path. But when compiling it still doesn't find it.

              – jan
              Apr 29 '16 at 9:06

















            • Would you mind expanding on how exactly to change texmf.cnf? I tried to add TEXINPUTS = ~/path/to/input//: to the users texmf.cnf in /usr/local/texlive/2015/ but it still won't find the files. What am I doing wrong?

              – jan
              Apr 28 '16 at 9:03












            • Sorry, I still couldn't get it to work. Is changing texmf.cnf in /usr/local/texlive/2015/ what you meant?

              – jan
              Apr 29 '16 at 4:08











            • @jan if you set it in texmf.cnf you need to set the whole thing rather than just .//: as that is where it's set, in the file returned by kpsewhich texmf.cnf or on the command line (with a shell such as bash) you can simply do TEXINPUTS=.//: pdflatex yourfile.tex also kpsexpand '$TEXINPUTS' will show the currently active setting

              – David Carlisle
              Apr 29 '16 at 8:28












            • Hmm, I still don't seem to get it. kpsewhich texmf.cnf gives me /usr/local/texlive/2015/texmf.cnf as expected. Now I've added TEXINPUTS = /path/to/folder//: to that file. kpsexpand '$TEXINPUTS' gives me exactly that path. But when compiling it still doesn't find it.

              – jan
              Apr 29 '16 at 9:06
















            Would you mind expanding on how exactly to change texmf.cnf? I tried to add TEXINPUTS = ~/path/to/input//: to the users texmf.cnf in /usr/local/texlive/2015/ but it still won't find the files. What am I doing wrong?

            – jan
            Apr 28 '16 at 9:03






            Would you mind expanding on how exactly to change texmf.cnf? I tried to add TEXINPUTS = ~/path/to/input//: to the users texmf.cnf in /usr/local/texlive/2015/ but it still won't find the files. What am I doing wrong?

            – jan
            Apr 28 '16 at 9:03














            Sorry, I still couldn't get it to work. Is changing texmf.cnf in /usr/local/texlive/2015/ what you meant?

            – jan
            Apr 29 '16 at 4:08





            Sorry, I still couldn't get it to work. Is changing texmf.cnf in /usr/local/texlive/2015/ what you meant?

            – jan
            Apr 29 '16 at 4:08













            @jan if you set it in texmf.cnf you need to set the whole thing rather than just .//: as that is where it's set, in the file returned by kpsewhich texmf.cnf or on the command line (with a shell such as bash) you can simply do TEXINPUTS=.//: pdflatex yourfile.tex also kpsexpand '$TEXINPUTS' will show the currently active setting

            – David Carlisle
            Apr 29 '16 at 8:28






            @jan if you set it in texmf.cnf you need to set the whole thing rather than just .//: as that is where it's set, in the file returned by kpsewhich texmf.cnf or on the command line (with a shell such as bash) you can simply do TEXINPUTS=.//: pdflatex yourfile.tex also kpsexpand '$TEXINPUTS' will show the currently active setting

            – David Carlisle
            Apr 29 '16 at 8:28














            Hmm, I still don't seem to get it. kpsewhich texmf.cnf gives me /usr/local/texlive/2015/texmf.cnf as expected. Now I've added TEXINPUTS = /path/to/folder//: to that file. kpsexpand '$TEXINPUTS' gives me exactly that path. But when compiling it still doesn't find it.

            – jan
            Apr 29 '16 at 9:06





            Hmm, I still don't seem to get it. kpsewhich texmf.cnf gives me /usr/local/texlive/2015/texmf.cnf as expected. Now I've added TEXINPUTS = /path/to/folder//: to that file. kpsexpand '$TEXINPUTS' gives me exactly that path. But when compiling it still doesn't find it.

            – jan
            Apr 29 '16 at 9:06











            0














            I've recreated your file structure and this works for me:



            transcripts/
            ├── 2013-05
            │   ├── 2013-05-12
            │   │   ├── 2013-05-12-transcript1
            │   │   │   └── 2013-05-12-transcript1.tex
            │   │   └── 2013-05-12-transcript2
            │   │   └── 2013-05-12-transcript2.tex
            │   └── 2013-05-14
            │   └── 2013-05-14-transcript1
            │   └── 2013-05-14-transcript1.tex
            └── 2013-06
            └── 2013-06-07
            └── 2013-06-07-transcript1
            └── 2013-06-07-transcript1.tex


            The file 2013-05-12-transcript1.tex is textbfFirst, file 2013-05-12-transcript2.tex is textbfSecond, file 2013-05-14-transcript1.tex is textbfThird, file 2013-05-14-transcript1.tex is textbfFourth, and the example file is as follows:



            % arara: pdflatex
            documentclassarticle
            begindocument

            input2013-05-12-transcript1.tex
            ...
            input2013-05-12-transcript2.tex
            ...
            input2013-05-14-transcript1.tex
            ...
            input2013-06-07-transcript1.tex

            enddocument


            Windows



            I've saved it in D:transcripts



            Temporary configuration



            Open a command line cmd (you do not need administrator privileges) and you execute:



            set TEXINPUTS=D:/transcripts//;
            pdflatex sampleforum.tex


            this will work until you close the command line, that is, you must execute the line every
            time after close a command line ... tedious ... yes.



            Permanent configuration



            Open a command line cmd (you do not need administrator privileges) and execute:



            setx TEXINPUTS D:/transcripts//;


            close command line and open a new and execute:



            reg query HKEY_CURRENT_USEREnvironment
            pdflatex sampleforum.tex


            In this way we have configured the environment variable and now it is permeating.



            And to delete TEXINPUTS from environment variable, just use:



            reg delete HKEY_CURRENT_USEREnvironment /v TEXINPUTS /f


            Alternatively this can be done in a graphical mode adjusting your environment variable .



            Linux



            I've saved it in ~/transcripts



            Add to our file .bashrc the line:



            export TEXINPUTS='~/transcripts//:'


            Another option would be to use tlmgr conf auxtrees, but the directory would have in TDS form.



            Saludos





            share



























              0














              I've recreated your file structure and this works for me:



              transcripts/
              ├── 2013-05
              │   ├── 2013-05-12
              │   │   ├── 2013-05-12-transcript1
              │   │   │   └── 2013-05-12-transcript1.tex
              │   │   └── 2013-05-12-transcript2
              │   │   └── 2013-05-12-transcript2.tex
              │   └── 2013-05-14
              │   └── 2013-05-14-transcript1
              │   └── 2013-05-14-transcript1.tex
              └── 2013-06
              └── 2013-06-07
              └── 2013-06-07-transcript1
              └── 2013-06-07-transcript1.tex


              The file 2013-05-12-transcript1.tex is textbfFirst, file 2013-05-12-transcript2.tex is textbfSecond, file 2013-05-14-transcript1.tex is textbfThird, file 2013-05-14-transcript1.tex is textbfFourth, and the example file is as follows:



              % arara: pdflatex
              documentclassarticle
              begindocument

              input2013-05-12-transcript1.tex
              ...
              input2013-05-12-transcript2.tex
              ...
              input2013-05-14-transcript1.tex
              ...
              input2013-06-07-transcript1.tex

              enddocument


              Windows



              I've saved it in D:transcripts



              Temporary configuration



              Open a command line cmd (you do not need administrator privileges) and you execute:



              set TEXINPUTS=D:/transcripts//;
              pdflatex sampleforum.tex


              this will work until you close the command line, that is, you must execute the line every
              time after close a command line ... tedious ... yes.



              Permanent configuration



              Open a command line cmd (you do not need administrator privileges) and execute:



              setx TEXINPUTS D:/transcripts//;


              close command line and open a new and execute:



              reg query HKEY_CURRENT_USEREnvironment
              pdflatex sampleforum.tex


              In this way we have configured the environment variable and now it is permeating.



              And to delete TEXINPUTS from environment variable, just use:



              reg delete HKEY_CURRENT_USEREnvironment /v TEXINPUTS /f


              Alternatively this can be done in a graphical mode adjusting your environment variable .



              Linux



              I've saved it in ~/transcripts



              Add to our file .bashrc the line:



              export TEXINPUTS='~/transcripts//:'


              Another option would be to use tlmgr conf auxtrees, but the directory would have in TDS form.



              Saludos





              share

























                0












                0








                0







                I've recreated your file structure and this works for me:



                transcripts/
                ├── 2013-05
                │   ├── 2013-05-12
                │   │   ├── 2013-05-12-transcript1
                │   │   │   └── 2013-05-12-transcript1.tex
                │   │   └── 2013-05-12-transcript2
                │   │   └── 2013-05-12-transcript2.tex
                │   └── 2013-05-14
                │   └── 2013-05-14-transcript1
                │   └── 2013-05-14-transcript1.tex
                └── 2013-06
                └── 2013-06-07
                └── 2013-06-07-transcript1
                └── 2013-06-07-transcript1.tex


                The file 2013-05-12-transcript1.tex is textbfFirst, file 2013-05-12-transcript2.tex is textbfSecond, file 2013-05-14-transcript1.tex is textbfThird, file 2013-05-14-transcript1.tex is textbfFourth, and the example file is as follows:



                % arara: pdflatex
                documentclassarticle
                begindocument

                input2013-05-12-transcript1.tex
                ...
                input2013-05-12-transcript2.tex
                ...
                input2013-05-14-transcript1.tex
                ...
                input2013-06-07-transcript1.tex

                enddocument


                Windows



                I've saved it in D:transcripts



                Temporary configuration



                Open a command line cmd (you do not need administrator privileges) and you execute:



                set TEXINPUTS=D:/transcripts//;
                pdflatex sampleforum.tex


                this will work until you close the command line, that is, you must execute the line every
                time after close a command line ... tedious ... yes.



                Permanent configuration



                Open a command line cmd (you do not need administrator privileges) and execute:



                setx TEXINPUTS D:/transcripts//;


                close command line and open a new and execute:



                reg query HKEY_CURRENT_USEREnvironment
                pdflatex sampleforum.tex


                In this way we have configured the environment variable and now it is permeating.



                And to delete TEXINPUTS from environment variable, just use:



                reg delete HKEY_CURRENT_USEREnvironment /v TEXINPUTS /f


                Alternatively this can be done in a graphical mode adjusting your environment variable .



                Linux



                I've saved it in ~/transcripts



                Add to our file .bashrc the line:



                export TEXINPUTS='~/transcripts//:'


                Another option would be to use tlmgr conf auxtrees, but the directory would have in TDS form.



                Saludos





                share













                I've recreated your file structure and this works for me:



                transcripts/
                ├── 2013-05
                │   ├── 2013-05-12
                │   │   ├── 2013-05-12-transcript1
                │   │   │   └── 2013-05-12-transcript1.tex
                │   │   └── 2013-05-12-transcript2
                │   │   └── 2013-05-12-transcript2.tex
                │   └── 2013-05-14
                │   └── 2013-05-14-transcript1
                │   └── 2013-05-14-transcript1.tex
                └── 2013-06
                └── 2013-06-07
                └── 2013-06-07-transcript1
                └── 2013-06-07-transcript1.tex


                The file 2013-05-12-transcript1.tex is textbfFirst, file 2013-05-12-transcript2.tex is textbfSecond, file 2013-05-14-transcript1.tex is textbfThird, file 2013-05-14-transcript1.tex is textbfFourth, and the example file is as follows:



                % arara: pdflatex
                documentclassarticle
                begindocument

                input2013-05-12-transcript1.tex
                ...
                input2013-05-12-transcript2.tex
                ...
                input2013-05-14-transcript1.tex
                ...
                input2013-06-07-transcript1.tex

                enddocument


                Windows



                I've saved it in D:transcripts



                Temporary configuration



                Open a command line cmd (you do not need administrator privileges) and you execute:



                set TEXINPUTS=D:/transcripts//;
                pdflatex sampleforum.tex


                this will work until you close the command line, that is, you must execute the line every
                time after close a command line ... tedious ... yes.



                Permanent configuration



                Open a command line cmd (you do not need administrator privileges) and execute:



                setx TEXINPUTS D:/transcripts//;


                close command line and open a new and execute:



                reg query HKEY_CURRENT_USEREnvironment
                pdflatex sampleforum.tex


                In this way we have configured the environment variable and now it is permeating.



                And to delete TEXINPUTS from environment variable, just use:



                reg delete HKEY_CURRENT_USEREnvironment /v TEXINPUTS /f


                Alternatively this can be done in a graphical mode adjusting your environment variable .



                Linux



                I've saved it in ~/transcripts



                Add to our file .bashrc the line:



                export TEXINPUTS='~/transcripts//:'


                Another option would be to use tlmgr conf auxtrees, but the directory would have in TDS form.



                Saludos






                share











                share


                share










                answered 3 mins ago









                Pablo González LPablo González L

                1,0211820




                1,0211820



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid


                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.

                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function ()
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f306790%2ffind-files-in-subdirectories-to-use-with-input%23new-answer', 'question_page');

                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Lioubotyn Sommaire Géographie | Histoire | Population | Notes et références | Liens externes | Menu de navigationlubotin.kharkov.uamodifier« Recensements et estimations de la population depuis 1897 »« Office des statistiques d'Ukraine : population au 1er janvier 2010, 2011 et 2012 »« Office des statistiques d'Ukraine : population au 1er janvier 2011, 2012 et 2013 »Informations officiellesCartes topographiquesCarte routièrem

                    Isabella Eugénie Boyer Biographie | Références | Menu de navigationmodifiermodifier le codeComparator to Compute the Relative Value of a U.S. Dollar Amount – 1774 to Present.

                    Mpande kaSenzangakhona Biographie | Références | Menu de navigationmodifierMpande kaSenzangakhonavoir la liste des auteursm