#1742 [LaTeX Tools] "Set Main File" broken

closed-invalid
None
5
2014-09-12
2013-10-15
No

With current versions of jEdit and the LaTeX Tools plugin, I am unable to set the main file of a LaTeX file. It works neither globally through the "Set Main File" menu entry, nor locally through the :latex.root line in the document itself. This renders the "Compile" command useless for split documents.

Discussion

  • Alan Ezust

    Alan Ezust - 2013-11-28
    • status: open --> pending-works-for-me
     
  • Alan Ezust

    Alan Ezust - 2013-11-28

    "Set Main File" works for me. If I have the main file opened as my current buffer and invoke that command,
    I can see that it is set from the "show main file path". After that, the "compile" command will invoke my chosen latex command on the main file, passing the absolute path as an argument.
    I need further steps to reproduce your issue.
    Perhaps your settings have changed, and you don't have the correct command set for latex?

     
  • Frederik Elwert

    Frederik Elwert - 2013-11-29
    • status: pending-works-for-me --> closed-invalid
     
  • Frederik Elwert

    Frederik Elwert - 2013-11-29

    Thanks for the feedback.

    I just misunderstood how the "set main file" command is supposed to work: I called it with my chapter file as the current buffer, and expected to get a dialog that allows me to set the main file. Now I tried it the way you described it, and it works. Thanks!

     
  • Steve

    Steve - 2013-12-03

    Perhaps a name change would help. Like the OP, I would expect "Set main file" to pop a dialog. Perhaps the feature should be "Set this file as main" or something.

     
  • Alan Ezust

    Alan Ezust - 2013-12-03

    i added a tooltip: "... to currenly opened buffer"
    And clarified how it works in the documentation for 0.6.1

     
  • Alan Ezust

    Alan Ezust - 2013-12-03
    • assigned_to: nobody --> ezust
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks