I've been using TextMate for years and I'm productive and happy with it. However, I like to try other editors from time to time to see if I'm missing anything. Recently I spent some time learning Vim and I discovered a few things that I particularly liked.
1) Split windows -- not the kind of split windows you normally get in Mac applications, but the Vim style ones. In Vim you can easily navigate from the keyboard to your different splits and choose what files to display in each. Additionally, you don't have to reach for your mouse to create a split. When you split, Vim divides the space up for you which is what you want most of the time. I found that it is very handy when needing to view more than 1 file at a time, which in my case is most of the time. Closing splits is about as easy as they are to create -- all from the keyboard. Multiple windows isn't really the same thing because they are slow to setup and tear down.
2) Selective multifile grep -- in Vim you can use a regular expression to open a set of files, and then just grep across the open files.
3) Don't need arrow keys -- after years of editing with the mouse; I find it painful to reach for it. It hurts my right shoulder and shoulder blade. It even hurts to have to move my hand down to the arrow keys. However, in Vim it is easy to keep your hands resting on your keyboard with your shoulders relaxed. No reaching for the mouse or arrow keys.
Q1: I recently updated to TM2alpha, and I'm quite fond of it! I mostly use
TM as my LaTeX editor. However, when I compile documents the log window
doesn't close when the PDF is viewed in Skim. I have made sure the "Keep log
window open" option is not checked. Actually I would like the window to show
only at errors
Q2: I would prefer to be able to chose the log window layout to be more
minimalistic, kind of terminal-like, as I find the default layout to be
unnecessary graphical and heavy. I've tried to google about a bit, but can't
seem to find if changing it is possible or not.
View this message in context: http://textmate.1073791.n5.nabble.com/Compiling-LaTeX-log-window-tp25794.ht…
Sent from the textmate users mailing list archive at Nabble.com.
So I'm a bit late to the TextMate wonderfulness.. I've been using the
30-day trial version for the last week, and got it pretty customized to
my liking. Project+, MissingDrawer, SVNMate, bundles, a few custom
Templates for my C++ projects, etc. Loving it.
Today I went out and got the latest TextMate2 compile from about 2 days
ago, I believe, and wow. That's a huge step backward IMO. No
"Projects" that I can see, just look at a Directory (which doesn't work
for me, my Directory Structure != Project structure). No support for
Templates either, it seems, which I just recently figured out and
_really_ love (great to just pull in a template of my base C++ class and
"fillin the blanks"). Plus lots of things I customized don't see to be
there anymore, or are buried in the new "tm_properties" file.
Basically, I'm trying to figure out what to do next. I was getting
ready to buy TextMate1, but if this is what TextMate2 is going to look
like maybe I should evaluate some other tools. Is TM1 still "alive"?
Or are users urged to start using TM2? Am I just really missing
something in TextMate2? I'm a C/C++ developer that also uses Arduino,
CMake, Python, and other stuff, so things like CTags, project-specific
environment variables, and true "Projects" are important to me.
Hi LaTeX users,
I'm working some more on the Typeset and View command, we are going to replace the default command that currently ships with TextMate. But I need some information. What process are TextMate's LaTeX users following for building their documents? I'm sure most of you are using bibtex, but what about other things like makeindex? Has everyone moved to a pure pdf-based process, or are some of you still using dvi/postscript? What are you using for pictures? Anything you can tell me will help.
I would also *love* example documents along with the expected output. This will aid in testing, and ensure that your particular process will be supported!
I had the same problem as described in a post from Sebastian on
Here is my error output:
Running bibtex on Exjobb (ny).tex
Traceback (most recent call last): File "/Users/peeter/Peeterprogram/
texMate.py", line 457, in texStatus, isFatal, numErrs, numWarns =
run_bibtex(texfile=fileName) File "/Users/peeter/Peeterprogram/
texMate.py", line 71, in run_bibtex return stat,fatal,err,warn
UnboundLocalError: local variable 'stat' referenced before assignment
It seems that it had to do with the parentheses in my filename messing
up the regexes.
My solution was to change lines 71 and 72 in Textmate.app/Contents/
SharedSupport/Bundles/Latex.tmbundle/Support/bin/texMate.py as follows:
# auxfiles = [f for f in os.listdir('.') if re.search('.aux
$',f) > 0]
# auxfiles = [f for f in auxfiles if re.match(r'('+ basename +
auxfiles = [f for f in os.listdir('.') if re.search('.aux$',f)
> 0 and (f.startswith(basename) or re.match(r'bu\d+\.aux', f))]
This works, at least for me.
Or have I messed something else up in the process?
I'm hitting Command+/ to toggle code comments on and off, but it always
defaults to block comments (/* ... */). Is there a way to default Command+/
to line comments (// ...), or can I press another hotkey to do this?