Is it just me, or does the CodeBrowser not work when TextMate is run
in Intel-Mode? When I start it in Rosetta everything is fine, in
intel-mode I have no CodeBrwoser, but instead a:
2006-03-22 01:00:00.774 TextMate *** -[NSBundle load]: Error
loading code /Users/dekay/Library/Application Support/TextMate/
bundle /Users/dekay/Library/Application Support/TextMate/PlugIns/
TmCodeBrowser.tmplugin, error code 2 (link edit error code 0, error
number 0 ())
2006-03-22 01:00:00.775 TextMate instance TmCodeBrowser plugin
doesn't have proper initializer
on my console…
I've written a little command to help me grep the current file and copy
matching lines to a new document. I've copied the example of "Search the
TextMate Mailing List" for the CocaoDialog. However my implementation is
stalling and I need to killall CocaoDialog to free it up.
Output: Create new document
res=$(CocoaDialog inputbox \
--title "Find matching lines" \
--informative-text "Regular expression to match lines:" \
--button1 "Find" --button2 "Cancel")
[[ $(head -n1 <<<"$res") == "2" ]] && exit_discard
pattern=$(tail -n1 <<<"$res")
perl -ne "print if /$pattern/";
The only thing much different here from the "Search mailing list" code
is the use of stdin.
Not sure if this is possible. Anyone ever use Zend Studio? The auto
competition and function prototypes are simply amazing.
Basically, completion happens automatically, and gives a nice drop
down with prototype information in it. Also, if you are inside a
functions brackets, it will show a prototype of the function, based
on the PHPDoc comments (if it's available).
Is this possible in the current version of textmate? I imagine it
would have to index the project to get this going. If it's not
possible, is it every planned? I immagine it would be useful for
to parse the source code in the project.
Since TextMate already has such great support for Markdown I'm
wondering why Smartypants has been left in the dark.
I was reading this: http://rentzsch.com/notes/contemporaryQuill
...and wondering why a solution like this has not already been
implemented. The only reason I don't want to use this is because it
will break when TextMate has been updated.
Is there an implementation like this already out there?
So, in the process of writing the screenwriting bundle I'm working
(and using every day) I've come to the conclusion that it might be
cool to look into subversion for working with screenwriting projects.
Obviously I know nothing about subversion, so my question is:
Is this stupid?
Do you guys have any good resources for getting started with subversion?
Is there a better solution (since I'm just using text-documents)?
I can't seem to find a really good intro on how to use TextMate with
Subversion, did I miss it somewhere?
Thanks in advance.
>> [...] TextMate seems to show tabs and line endings but not any more of
>> the non-printing characters that BBEdit shows
> It does show unprintable characters, but not spaces.
It's good to know I wasn't doing something wrong. However, if the
functionality exists [and has already been written/tested] why keep it out
of a release?
Trust me, I want to fall in love with TextMate, but there's some things that
can't yet be done in TextMate -- I find myself jumping back to BBEdit in
order to accomplish these tasks.
> I found that to look too busy and the spaces should be indicated by where
> there are no other ,,invisibles% shown
I respect the consideration to keep the application lean and fast, but when
should a developer's personal preference get in the way of what his/her end
user's want out of a product?
> (I know there are requests for configuration here).
A simple option or preference would be a welcome addition and wouldn't
require people to use it. BBEdit conditionally allows one to show invisibles
and then selectively choose whether or not spaces are shown.
>> I was able to find the ShowInvisibles Bundle for TextMate that aims
>> to highlight tabs and spaces in different colors but it doesn't
>> appear to work with my setup and/or preferences.
> It was created prior to the theme system. What it does is give a
> certain scope to spaces (and other characters), but for that to show,
> you would need to add a theme rule for it.
This information is encouraging, but the bundle doesn't come with any
documentation or configuration instructions, only to edit the
Invisibles.plist to suit ones' needs.
Could you put together an example of a theme rule that would highlight the
spaces in a document using this bundle?
I am curious: the PropertyList bundle keeps getting lost on my
system. No apparent reason why. A svn update does not tell me about
any changes; it is still installed - yet the bundle editor does not
list it in its filters list. I have to install it into ~/Library/
Application Support/TextMate/Bundles/ else it will not be listed at
I'm currently working on a website where I'm going to add text
through html forms. I have tried the Edit in Textmate option, but it
seems to be an issue with the encoding.
The site I'm working on uses iso-8859-1 as encoding, and when I get
the text in Textmate all Norwegian characters are not represented
correct. I guess this is because Textmate uses unicode in its
internal representation of the text. Are there any workarounds for this?
I have a project with about 500 files that split neatly into a few
categories. Is there some way to split the project drawer or otherwise
get two separate scrolling views of different subsections of the project?
And/or can one get a multi-pane hierarchical view (like one of the
It looks like Go to File... will often be the quickest way to open a
file, but sometimes I'll have to manually hunt through the hierarchy and
some hints on how best to wade through it would be much appreciated.
> Could you put together an example of a theme rule that would
> highlight the
> spaces in a document using this bundle?
Just add a new line to whatever theme you are using (in prefs,
fonts&colors, click the plus button), select that line, enter the
scope selector that the Invisibles.bundle assigns to invisibles - et
PS: I don't have access to the bunlde -- thus you will need to figure
out the scope yourself from the bundle editor.