some python commands are not working here, specifically the commands
which begin with "#!/usr/bin/env python".
When I try them, they output "env: python: No such file or directory"
My python lives at /usr/local/bin/python and this is also what the
(Preferences) textmate shell variable $TM_PYTHON is set to.
What do I need to do to get "#!/usr/bin/env python" also recognize that?
Dirk van Oosterbosch
de Wittenstraat 225
1052 AT Amsterdam
There are two commands, "Go to symbol" and "Go to file", that uses a
search dialog to select a file or a symbol.
I think this would be very usefull for other commands too. I am
thinking about the insertion of references and citations in Latex. Is
there a possibility to use this feature in bundles?
Happy Helloween ;)
There are two commands, "Go to symbol" and "Go to file", that uses a search dialog to select a file or a symbol.
I think this would be very usefull for other commands too. I am thinking about the insertion of references and citations in Latex. Is there a possibility to use this feature in bundles?
Happy Helloween ;)
Der GMX SmartSurfer hilft bis zu 70% Ihrer Onlinekosten zu sparen!
Ideal für Modem und ISDN: http://www.gmx.net/de/go/smartsurfer
I've been using TextMate to edit some C/C++ code, and I've noticed
that the language module doesn't catch functions where the parameter
list is split across multiple lines.
For example, it will catch this:
void myFunction( int a, int b )
But it will not catch this:
I was just wondering whether the regular expression should be
modifier to ignore any white-space and new-lines between elements of
the function definition?
I'm using TextMate 1305.
There seems to be a problem with how TextMate deals with processes
run from a document. If you want your TextMate to become
irresponsive, just do the following
1. Open a new document
2. Type "yes"
3. Press ^R
Of course what you do is to run into an endless loop here. But the
problem is that the whole application becomes irresponsive. It really
should not be as prone to errors in external programs, since this
creates the risk of data losses.
Is there any way to make a bundle command that works while there
is no file open in TextMate?
I often want to use the 'Remote Open...' command in my remote
editing bundle (http://www.cse.unsw.edu.au/~willu/RemoteEdit/) when
no other windows are open.
I've just updated my bundles from the repository as I thought I'd see
what new goodies are available. Now however when I attempt to commit
I get the usual status window with the following message:
"These files are not under version control, and so will not be committed:
(and so on)
Then CommitWindow pops up with all those files listed again
(understandably with a ? status) and they are all selected too. This
is different behaviour to what I'm used to - the previously the
subversion bundle silently ignored ._* files and wouldn't even mention
their presence the status window.
I realise the ._* files appear as the project is on a NFS share but
previously this wasn't a problem. Is there way to tell the bundle to
globally ignore ._* or is the only option to set the svn:ignore
property recursively on every directory (and every new directory in
(I've update the entire /Library/Application Support/TextMate/
checkout so I've got the up-to-date version of CommitWindow.app too)
The 'Insert Command Header' snippet in the 'source' bundle has '//'
hardcoded as the start comment token. Wouldn't it make more sense to
turn it into a command that would take each language comment delimiters