For reasons I've yet to determine, pageUp: and pageDown: seem to be
misbehaving in TextMate (and only TextMate). I've tried removing all my
local changes (except to bind pageUp to pageUp: and pageDown to pageDown:
and including ~/Library/KeyBindings/DefaultKeyBindings.dict), all
non-standard bundles, scanning the list of bundle keybindings, and even
The behavior I'm seeing is downright bizarre: It seems as if pageUp/Down are
executing multiple commands and ending badly confused. Surprisingly,
option-pageUp/Down, which are bound to pageUp:/pageDown: at the system
level, work fine.
These same bindings work fine in TextEdit and XCode.
Any suggestions about where I might look? Is there some TextMate default I
can set to see more of what's happening?
Anyone that's using the Quick
under Leopard finding that it's now broken? I'm getting the following
error as soon as I choose "Quick Search"
/tmp/temp_textmate.xdnrYn:4:in `require': no such file to load --
> /Library/Application Support/TextMate/Support/lib/dialog (LoadError) from
> /tmp/temp_textmate.xdnrYn:4 from /tmp/temp_textmate.xdnrYn:4:in `each' from
I've updated the bundles directory to the latest, but alas still no joy. Any
help would be appreciated.
> When I do a quick look on a TextMate text document, I just see a big
> TextMate icon and not the content. Does anyone have an idea how that could
> be fixed? Is it a Mac OS problem for not showing the content of a text file
> or is the OS simply asking the app (TextMate) how the document should be
> shown somehow?
I was able to hack together something that works on my machine, based
on the comments here and some docs at Apple:
that there are probably *WAY* more intelligent ways to do this, and if
you implement what I suggest here you are doing so AT YOUR OWN RISK.
Now, with that out of the way, I just created an empty application
(from the shell) with a hacked Info.plist, as follows:
In Info.plist I put the following:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN"
The important stuff in there is the UTType stuff. Just adjust/copy
that "dict" section with fake data about the file type you want to use
with QuickLook. As long as UTTypeConformsTo is public.plain-text,
QuickLook will display it as text.
And if someone else knows how to do this properly, please let me know. :-)
I think I have discovered a bug in the LaTeX bundle:
When I insert a tabular/array snippet when I go to the second tab
stop (specification of the column) Iget
the spec rl tells that there are two columns, but inside the
environment I have 3 columns (resulting in a LaTeX error).
The same behaviour does not occur for example with r|l as column spec.
All the best
Dr Guido Governatori
School of Information Technology and Electrical Engineering
The University of Queensland
Brisbane, Queensland, 4072, Australia
Phone: +61-(0)7-336 52907
Fax: +61-(0)7-336 54999
Hi, I'm a brand new TextMate user (as of yesterday), and have enjoyed
very much my experience so far. I do a lot of writing in LaTeX, and
have been very impressed with the design of the LaTeX-related
features. Virtually everything has worked as advertised, and I'm
busy integrating those new features I haven't had in the past into
both my memory and my workflow.
One question: The command "Typeset & View (PDF)" works fine, as does
syncing from my viewer (Skim) back to TextMate. However, I currently
am unable to go the other way. When I try "Show in PDF Viewer
(pdfsync)", nothing happens; if I change the output setting for the
command (in the bundle editor) to "Show as HTML", then executing the
command via the menu gives the following message:
Running sync on sensory-function.tex
pdfsync.sty must be included to use this command
I've looked through the list archives, but don't see any mention of
this symptom. I don't mind getting my hands dirty (and do have some
skill in Python, so I've started looking at texMate.py), but was
hoping someone could point me in the right direction to finish
diagnosing and/or fixing this particular issue.
(TeX Live 2007 distribution, Skim and TextMate both up-to-date)
Thanks very much,
Rudimentary editing inquiry here. I need to be able to append
alt="foo" to about 30 <img> tags on my HTML document which resembles
<img width="30" height="30" src="<?= base_url()
Is there a quick way to do this in TextMate?
There are so many wonderful shortcuts and key assignments within
TextMate that it can sometimes get a bit confusing. I know that you
can hit `<apple><ctrl>t` and TextMate will happily bring up a master
list of all the bundle items and their associated key triggers or key
shortcuts, but that takes a while to search through if you are trying
to find out what '<apple><alt><shift>G' will do.
I would like to know if there is a bundle or hidden action, that will
allow you to go into a mode where you can then hit a key combo and it
will show you the action(s) associated with that combo. This would
also be very useful while you are in the Bundle editor mode to see if
a key-combo has already been assigned to something else when you are
creating your own commands or snippets.
When I do a quick look on a TextMate text document, I just see a big
TextMate icon and not the content. Does anyone have an idea how that could
be fixed? Is it a Mac OS problem for not showing the content of a text file
or is the OS simply asking the app (TextMate) how the document should be
The content of Text Clipping are not shown, but the content of RTF files and
OpenDocumentText (odt) files created by TextEdit are.
View this message in context: http://www.nabble.com/leopard-quick-look-on-TextMate-text-documents-tf47281…
Sent from the textmate users mailing list archive at Nabble.com.
I'm sure Allan is all over it, but I noticed an issue with TextMate (v1.5.7)
running on Leopard. Clicking the "gear" popup at the bottom of the window
and selecting various bundles to see the commands, the text in the menus are
different sizes! Some small, some large. I remember seeing this before and
it was corrected.
I'll play around more tonight to see if there's some correlation between
menu items and text size.