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.
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!
Thanks,
—Alex
Hi!
I had the same problem as described in a post from Sebastian on
2007-11-11 (http://thread.gmane.org/gmane.editors.textmate.general/
23160).
Here is my error output:
Running bibtex on Exjobb (ny).tex
Traceback (most recent call last): File "/Users/peeter/Peeterprogram/
TextMate.app/Contents/SharedSupport/Bundles/Latex.tmbundle/Support/bin/
texMate.py", line 457, in texStatus, isFatal, numErrs, numWarns =
run_bibtex(texfile=fileName) File "/Users/peeter/Peeterprogram/
TextMate.app/Contents/SharedSupport/Bundles/Latex.tmbundle/Support/bin/
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 +
r'\.aux|bu\d+\.aux)',f)]
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?
/Peeter
Hi there,
If some variable starts with "C", the whole line which contains that
variable and where it at the very first place highlighted as comment. I
suppose it comes from old F77 style, where C denotes comment, but it's
not necessary now. Is there any way to fix it? My current way-around is
to put single space before that variable, but in this case overall code
doesn't look as nice as before.
Thanks.
--
Kaster Might
Hi listers!
This is my first post here. And I'm so sorry to have a so dummy start
but...
I'd like to use TextMate to write Plain TeX (not LaTeX!) papers but I can't
figure out how to do it.
Anyone willing to help me?
Many thanks in advance.
--
ßlue
--
View this message in context: http://old.nabble.com/Plain-TeX-tp31076342p31076342.html
Sent from the textmate users mailing list archive at Nabble.com.
Hi folks,
I work on several open-source projects (VTK, ParaView, CMake...) that
follow a somewhat unusual indentation style. Instead of
if (foo)
{
bar();
}
bar();
they require
if (foo)
{
bar;
}
bar()
Getting the first curly indent right was trivial but I can't figure
out how to reduce the indentation _after_ the closing curly. When the
pattern matches decreaseIndentPattern, the current line's indentation
is reduced. What I need is for the following line to be unindented. Is
there any way to do this?
Thanks,
-berk
Since I've never had good luck with symlinking in the Library folder,
I created a little applescript app that lets me push or retrieve my
settings from a hidden folder in my Dropbox. It's working great for
me so I thought I would share!
At this time it will:
1. Grab TextMate themes, bundles, settings, etc. from
~/Library/Application Support/TextMate and ~/Library/Preferences
2. Store them in a hidden folder in your DropBox called .MateSync
3. Download them onto another machine.
It won't:
1. Work if you don't have your Dropbox in ~/Dropbox
2. Save backups (Dropbox should do this for you)
3. Transfer TextMate.app to your Dropbox. If you make GUI changes,
you have to sync those yourself.
https://github.com/johnvilsack/SyncMate
Please let me know if anyone finds this useful!
- John
Hi Allan,
Could you make the font for the commit message customizable? I can't read that small font well on the new higher-resolution screens, plus I'd prefer it to be a monospaced font anyway.
A very simple way to make it configurable (and I patched my copy of TextMate) would be to edit
TextMate.app/Contents/SharedSupport/Support/bin/CommitWindow.app/Contents/Resources/English.lproj/MainMenu.nib
Select the text view inside the scroll view for the commit message, bring up the Bindings inspector, and change the FontName property to:
Bind to: Shared User Defaults Controller
Controller key: values
Model Key Path: CommitWindowFontName (or whatever else tickles you)
Null Placeholder: Set to the default font name (Lucida Grande?)
Now folks wanting a different font can simply do
defaults write com.cjack.tmbundles.commit-window CommitWindowFontName "Menlo"
No code changes :-)
Thanks
Gerd
