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?
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.
This is my first post here. And I'm so sorry to have a so dummy start
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.
View this message in context: http://old.nabble.com/Plain-TeX-tp31076342p31076342.html
Sent from the textmate users mailing list archive at Nabble.com.
I work on several open-source projects (VTK, ParaView, CMake...) that
follow a somewhat unusual indentation style. Instead of
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?
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.
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.
Please let me know if anyone finds this useful!
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
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 :-)
I've posted a plugin which lets you define keystrokes to move about and edit
your text files with ease, in the spirit of the Vim command-line editor.
Feedback and contributions are welcome.