Hi Everyone,<br><br>Lots of progress on the new LaTeX and View command over the last two days. If you can, please check out the branch and give it a try. It should work for you right out of the box with no additional configuration.
<br><br>Both TM_LATEX_MASTER, and the TexShop directives are supported.<br><br>I think the configuration interface now handles the old ERRLVL stuff in a much more end user friendly way.<br><br>Thanks,<br><br>Brad<br><br><div>
<span class="gmail_quote">On 7/23/07, <b class="gmail_sendername">Brad Miller</b> <<a href="mailto:bmiller@luther.edu">bmiller@luther.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><br><div><div><span class="e" id="q_113f4b6ec872cb5f_1"><span class="gmail_quote">On 7/23/07, <b class="gmail_sendername">Charilaos Skiadas</b> <<a href="mailto:skiadas@hanover.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
skiadas@hanover.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Jul 23, 2007, at 2:54 PM, Brad Miller wrote:<br><br>> Thanks for the comments, see below...<br>><br>> --<br>> Brad Miller<br>> Assistant Professor, Computer Science<br>> Luther College<br>><br>> On 7/23/07, Mike Miller <
<a href="mailto:mightymiller19@gmail.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">mightymiller19@gmail.com</a>> wrote: ><br>> TM_LATEX_MASTER<br>> > This one is more interesting. We currently have two ways to
<br>> > specify a master/root file. Using this variable, or using the
<br>> > TexShop %!TEX directive embedded directly in the file. The TexShop<br>> > way seems clearly superior to me since it allows for more<br>> > flexibility than a single environment variable per directory or
<br>> > project. So my proposal is that the environment variable goes away.<br>><br>> I agree that the %!TEX directive allows for more flexibility, but I<br>> think that there are several reasons that support for the environment
<br>> variable should not be dropped. First, at least in my case, it has<br>> always sufficed to use the TM_LATEX_MASTER environment variable, and<br>> I'm not sure that I can imagine a realistic situation in which one
<br>> would need more than one master file per project. Is there a common<br>> scenario in which one uses several "master" files for the same<br>> project?<br>><br>> Here's my scenario in the book I am writing. I have a master file
<br>> for the entire book which includes the master files for each<br>> chapter. But each chapter is broken down into individual files for<br>> big sections. This scenario breaks the TM_LATEX_MASTER approach.<br>
<br><br>I assume then that one of the two levels of inclusion is with \input<br>commands instead of \include commands, since \include commands can't<br>be nested ASAIK?<br><br>I have to say that I would like to keep TM_LATEX_MASTER and the %!TEX
<br>directives, and have the directives take precedence if present. I<br>suppose this adds complexity which we are trying to avoid, but for me<br>the fact that the directives need to be included in each file is<br>quite bothersome, especially when moving files around to new projects
<br>or whatnot. But I can also see its usefulness in your case.<br><br>I suppose the way I would organize your situation is that I would<br>have a separate tmproj file for each chapter, when I want to work<br>with a particular project.
<br><br>So, I assume that your are solving the problem of having each chapter<br>compile on its own and at the same time be includable in the master<br>document in the standard not very pretty method using conditionals?</blockquote>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> Second, if I'm not mistaken, the %!TEX directive must be placed<br>> manually in every new file that is created in a project; however, if
<br>> one uses the TM_LATEX_MASTER environment variable, a new file in a<br>> project is automatically assumed to have the same master file as the<br>> environment variable.</blockquote></span></div><div><br>Yes.
<br></div><br>
I don't think that keeping TM_LATEX_MASTER around is that much extra
work. In fact I had already coded up using it before I started work on
this configuration interface. I have plenty of old papers and projects
that will break if I remove TM_LATEX_MASTER so I don't know how
strongly I feel about getting rid of this one variable.<br>
<br>
But, the question is how should we let the user set their root file?
Through the standard way of setting a project environment variable?
Tell them to edit .textmate_init, or provide another dialog that
either writes to .textmate_init or adds a line to the current file? It
seems a bit confusing to give the user two totally different ways of
configuring something as simple as the master file.<span class="q"><br><br><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">><br>> This could be solved by modifying the standard latex templates, or
<br>> adding another command to the latex bundle that allows you to<br>> quickly add a directive line to a new file.<br><br>As well as edit an existing directive line. Would that command try to<br>automatically figure out the name of the master file, or would the
<br>user be expected to type it in?</blockquote></span><div><br>I suppose it could look for other .tex files in the same directory and if they have a root directive already in place that could be suggested.<br> </div><span class="q">
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>><br>> Do we need a separate checkbox that says keep textmate html window<br>> open?<br><br>No, but we do need to make sure that it does stay open based on which<br>of the three preferences the user has selected ;)
</blockquote></span><div><br>So, maybe we should be more clear in the preferences window:<br><br>Provide a checkbox that says: Automatically start external Viewer<br><br>And the radio boxes should say:<br><br>Close output if no errors
<br>Close output if no errors or warnings<br>Do not close output window<br><br>That may be a more direct way of saying what the ERRLVL variable is really getting at. What do you think??<br><span class="sg"><br>Brad<br>
</span></div><span class="q"><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Brad<br>><br>><br>> Thanks,<br>><br>> Mike Miller<br><br>Haris Skiadas<br>Department of Mathematics and Computer Science<br>Hanover College<br><br><br><br><br><br>______________________________________________________________________
<br>For new threads USE THIS: <a href="mailto:textmate@lists.macromates.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">textmate@lists.macromates.com</a><br>(threading gets destroyed and the universe will collapse if you don't)
<br><a href="http://lists.macromates.com/mailman/listinfo/textmate" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
http://lists.macromates.com/mailman/listinfo/textmate</a><br></blockquote></span></div><br><br clear="all"><div><span class="e" id="q_113f4b6ec872cb5f_11"><br>-- <br>Brad Miller<br>Assistant Professor, Computer Science<br>
Luther College
</span></div></blockquote></div><br><br clear="all"><br>-- <br>Brad Miller<br>Assistant Professor, Computer Science<br>Luther College