Hello everybody,
I noticed that the results of typesetting LaTeX files in Textmate
gives different results as compared to other TeX programs (TeXShop,
iTeXMac). In this particular case, a PDF graphic file was missing, in
which case, the TeX typesetting stops with a fatal error (at least, I
think that is what should happen), and no output is produced.
Accordingly, TeXing in TeXShop gives (as console output):
> LaTeX Warning: File `../Figures/polymerization_triamides.pdf' not
> found on input line 133.
>
> Error: /usr/local/teTeX/bin/i386-apple-darwin-current/pdflatex
> (file ../Figures
> /polymerization_triamides.pdf): cannot find image file
> ==> Fatal error occurred, the output PDF file is not finished!
... and no new PDF file. However, TeXing in Textmate gives:
> LaTeX Warning: File `../Figures/polymerization_triamides.pdf' not
> found on inpu
>
> Found 0 errors, and 60 warnings in 0 runs
... and a new PDF file with 0 pages which prompts PDFView to crash
upon trying to update. In other words, Textmate behaves as if there
was no error. What I find strange is that I thought that the console
output was entirely the responsibility of the TeX engine ... and I
have for sure only one TeX distribution installed. Are any parameters
passed to the TeX engine from Textmate that control this behavior? If
so, is there a reason for the current settings? Or what else could be
the reason?
On a side note, as you see in the example above all warnings are
truncated (no matter what size the console window is). Is there away
to avoid this?
Holger
>>> If the current TM_LATEX_ERRLVL settings are not sufficient, let
>>> us know.
>>
>> Thanks for the hint. I played around with the values. In my eyes
>> it would be useful to have one additional option where the console
>> window would not open at all *except* for when there is an error,
>> in which case it should open and remain open. The reason is that I
>> would like it to be closed after typesetting and, as a matter of
>> fact, the typesetting of a short file on the MacBook only takes a
>> fraction of a second anyways, so that the brief opening and
>> closing of the console window is not useful (in this particular
>> case).
>
> Well it sort of opens because this is the default output of the
> command, an HTML window. So the window opens before the command
> even starts running. Theoretically it would be possible to not open
> it until later, but it would make the code of that command even
> more complicated. It's already a pretty long shell script, that I
> try not to mess with lest my inferior shell skills brake it. If
> someone else wants to take a stab at it, then we can talk about it.
> But given that it works, and it really a minor nuisance, I'm loath
> to mess with it.
Well, that is fine with me. You are right, it is a minor nuisance. If
it can be fixed easily, fine. If not, it is not essential.
Holger
__
Eidgenössische Technische Hochschule Zürich (ETH Zürich)
Department of Materials
Wolfgang-Pauli-Str. 10, HCI H515
CH-8093 Zürich
Switzerland
Phone: (+41) 1 633 6474
Fax: (+41) 1 633 1390
Email: frauenrath(a)mat.ethz.ch
Web: http://www.polychem.mat.ethz.ch/frauenrath/
Ahoy TextMateys!
Prototype'd Javascript now has better escape code completion
and option-escape menu code completion.
Also,
I updated my TextMateCodeCompletion thing again to support basic
snippetization of completions.
Prototype completions contain a bunch of method arguments. Like this:
Thing.method(one,two)
Now, when you select a completion from the menu, it'll convert each
of the method arguments into snippet placeholders.
This is, of course, just a milestone in the road toward full snippet
completion support.
The eventual goal is that the completions list is just a list of the
names, then when you select one, a unique snippet is inserted for
that name.
The only problem is that we'll either have to duplicate all of the
completions in the escape completions list and the menu completions
list or else extend the completions list format to work with both
escape completion and menu completion.
I think the only way to extend the format is to get Allan to hack
textmate to support the new version. And I loathe the thought of
wasting my time implementing it one way and then having to
reimplement it the right way once Allan gets back.
I also reorganized the codecompletion library so that it can more
easily be used by other stuff. New methods:
to_snippet converts the choice you make into a basic snippet and
returns a string. (formerly to_s)
choice returns the choice that was chosen as a string
index returns the index of the array of the item that was chosen
thomas Aylott — design42 — subtleGradient — CrazyEgg
Hello everybody,
I have a number of relatively basic questions concerning the LaTeX
bundle, the "bundle mechanism" in general, as well as Textmate's
interaction with PDFView. I am a newbie to Textmate in the sense that
I bought a license about 8 months ago but I have not regularly/
seriously used it until now, and I am sure that I have not fully
understood some of the basics yet. So, please, excuse me if some of
the questions are "stupid" or have been answered on this list or in
Textmate's documentation. It would be helpful to just point me to the
relevant parts of the documentation in this case.
I should say, though, that I followed the discussions on this list in
the last 8 months, and I have also used Textmate on and off, I
tinkered around in order to fit it to my needs, tried (and partially
succeeded) to wrap my mind around the scope selector mechanism etc.
I must say that I am really excited about Textmate's potential, in
particular, its flexibility in regard of syntax coloring. If I
interpret the recent emails to the TeX on MacOS X mailing list
correctly, there is quite a need and a desire for a TeX frontend that
has some decent capabilities as a text editor but keeps TeXShop's
simplicity. This is why I hope that I am not alone with the following
questions (because I feel that this email will be relatively long)!
There seems to be a place for Textmate among the folks who use TeX on
MacOS X. The point is, I *want* to love Textmate, but some of the
following issues/questions keep me from using it on a regular basis.
So, here we go.
1. What is (strategically) the best way to include my own additions,
e.g., to the syntax coloring? The first thing I tried was to change
the original LaTeX language file itself, but I soon understood that
was not a good idea. The second thing I tried was create my own LaTeX
addition file (which would claimall .tex files and at the end include
the original LaTeX language file) but that also seemed to break
certain things. In relation to this first question, I think I need to
understand the following related questions:
2. Do I understand correctly that the "LaTeX bundle" is somehow
officially maintained in the sense that certain improvements and
additions are included in the official release from time to time?
3. Is there a "version system" for the bundles? I mean, is there a
way to tell that I have the latest version of the bundle (or which
one I have installed)?
4. Is a new version of a bundle automatically installed with the
Textmate updates?
5. What happens to my own additions when a bundle is upgraded? As far
as I understand, my additions are stored as "differences" to the
original file. But what exactly happens, for example, when I added/
changed a behavior that is later added/modified/deleted in an updated
bundle?
Furthermore, I have some questions concerning the typesetting
process. Let me start with two observations. The first time I
installed Textmate, the TeX console window would pop up when I hit
"Typeset", and the results would appear in relatively large chunks as
HTML output which seemed rather "slow" compared to TeXShop. The
window stayed on the screen when the typesetting was finished. The
second time I installed Textmate a couple of months later, (on my
MacBook Pro, only in case this matters), the large console window
would pop up in the middle of the screen briefly during typesetting,
and immediately disappear again when typesetting was finished (which
is relatively fast on a Macbook Pro!), not leaving me any chance to
at least adjust its size and position.
6. Can anybody give me a clue why there is this difference in
behaviors? Has the bundle changed in this respect? Does it matter
which type of processor it is run on?
7. Can one bring up the TeX console window without typesetting (e.g.
in order to change its size/position)?
8. Is there a way to switch its behavior between one of the following
options: Appear upon typesetting (i) always; (ii) upon error; (iii)
never; (iv) and close when typesetting is finished?
9. In case there is no way to switch the behavior, would it not be a
desirable feature? Would it be possible to include in the LaTeX
bundle by default?
10. Are there any advantages to display the results formatted as
HTML? Would it not be more appropriate (faster) to make it plain text?
And, finally, I have a few questions concerning the interaction with
PDFView. Let me start with a few comments again. First of all, I find
PDFView a really nice tool! Thanks to the developers! It just feels
right. Simple, with a clean interface. The only "complaint" that I
have (which is not really one) is that having two applications
interact still feels more clunky than TeXShop's integrated
solution ... I wonder whether there is any chance to see a PDF
Previewer with some basic LaTeX specific functionality (pdfsync,
click-to-magnify etc.) included in Textmate?
In any case ...
11. How am I supposed to view the current selection/cursor position
in Textmate in PDFView? Sometimes (and really not always), selecting
a word and hitting Ctrl-Opt-Cmd-O seems to work. Is there a better
way? For example, one without previously selecting something, or a
simple Cmd-click?
12. Why does it sometimes fail to take me to the correct paragraph
(showing the page PDFView had previously shown)? Is this a
shortcoming of pdfsync?
Again, excuse me for this laundry list of questions.
Thank you in advance for your answers, a big Thank You to the
Textmate/Bundle/PDFView developers for providing such great tools,
and I wish you all a Happy New Year.
Holger
__
ETH Zürich
Department of Materials
Wolfgang-Pauli-Str. 10, HCI H515
8093 Zürich, Switzerland
Phone: (+41) 1 633 6474
Fax: (+41) 1 633 1390
Email: frauenrath(a)mat.ethz.ch
Web: http://www.polychem.mat.ethz.ch/frauenrath/
I just made some structural changes to the completion commands in the
LaTeX bundle, both bibliography and label. It might be a bit slower,
and more importantly I might have broken some stuff. So those of you
brave enough to try it out, and without a paper deadline in 3 days,
please update via svn (both the bundle and the global support
directory) and let me know if you encounter any problems.
The reason for this change was to remove the large amount of code
duplication that existed in these commands.
Haris
Has anyone made a language grammar for editing TWiki in TextMate? It
would be quite cool to edit my entires in Textmate rather than using
the edit field in the web browser.
--
James Milne
Hi fellow TextMaters,
Every time I post to my WordPress blog I get this error[1] on the
first line of my .blog.markdown file. The post is ok on WP, so no big
deal but still annoying.
[1]: /Library/Application Support/TextMate/Support/lib/plist.bundle:
warning: already initialized constant EPOCH
Any idea about his?
Thanks for your time.
--
FredB
Hello everybody,
one more thing: Did anybody else observe the following strange behavior:
When I hit Ctrl-Opt-Cmd-O to view the file in PDFView, and then I
choose to just close the PDF file in PDF view, the corresponding
Textmate window is blank! The text is gone, the cursor in the first
line, no scroll bar! Re-opening the file brings back the text.
Holger
__
ETH Zürich
Department of Materials
Wolfgang-Pauli-Str. 10, HCI H515
CH-8093 Zürich, Switzerland
Phone: (+41) 1 633 6474
Fax: (+41) 1 633 1390
Email: frauenrath(a)mat.ethz.ch
Web: http://www.polychem.mat.ethz.ch/frauenrath/
Haris: you mentioned that a command using a mouse
is unacceptable. I do not understand this and I
am intrigued, would you elaborate?
I also hate the mouse and love the keyboard, as
any other respectable geek. But this is only because
keyboard is much faster and much more accurate.
But I have no ideological stance against the mouse.
If at some point I find that using a mouse is much
more convenient for some purpose, I use it
immediately. E.g., I would not draw a
picture using the keyboard (neither would you
I guess).
So the point with the interface for labels is exactly that
I feel the keyboard is not the faster tool for the task;
clicking in a nice list is indeed faster. I should also
mention that I proposed to the PDFView's brilliant
developer (Andrea Bergia) to implement a click-on-
the-formula feature (you click on the formula in pdf
and the \ref is inserted in the tex file...)
Piero
Hi Textmate gurus,
I have only been messing around with Textmate for a few days now, but
I am incredibly impressed, and I can see why it is called "the" text
editor for Mac.
I had been using TeXshop for LaTeX (which is still a great program,
but not nearly as powerful as Textmate), R.app for stats and
numerical programming in R, and the X11-based idlde for IDL
programming, and now I am glad to be switching to Textmate for all
those needs.
One thing I am having trouble with, however, is getting the html R
help to appear. When I select a valid R command (one for which help
(command) in R would bring up the html help page for that command),
no help file opens, and the returned tool tip says:
/tmp/temp_textmate.eOPTfa:8:in `require': No such file to load -- /
Applications/TextMate.app/Contents/SharedSupport/Support/lib/
current_word (LoadError)
from /tmp/temp_textmate.eOPTfa:8
I am no scripter, but I looked in the bundle editor at this command,
and it is a pretty serious looking ruby script. Will I have to learn
ruby to figure out what is going on here? or is it possibly
something much more simple that I am overlooking?
The first few lines of the ruby script (after the shebang and a
comment) are as follows:
require "#{ENV["TM_SUPPORT_PATH"]}/lib/exit_codes"
require "#{ENV["TM_SUPPORT_PATH"]}/lib/escape"
require "#{ENV["TM_SUPPORT_PATH"]}/lib/web_preview"
require File.join(ENV["TM_SUPPORT_PATH"], "lib/current_word")
require 'base64'
now, I don't know anything about ruby, but I am guessing that these
are perhaps some environment variables that I need to set in the
Textmate preferences? If so, what is the proper way to assign more
than one location to the TM_SUPPORT_PATH variable? do I simply put a
colon between each absolute path name? If so, that takes care of the
first three lines, but the last two are still a mystery to me.
If anyone could get me going in the right direction here, I would me
most appreciative. Like I said before, I am no sctipter, other than
the occasional shell script, but one of the really appealing aspects
of Textmate is that it seems like a good way to learn about scripting
through useful examples. If the solution to my problem is to learn
enough ruby to understand what the script does so I can troubleshoot
it, so be it, but in the meantime I wonder if there is a simpler
solution?
Thanks,
Paul
