I tend to work on projects by opening a textmate disk browser from
commandline, using mate <dirname>
Then when I open the first file, it doesn't have an editor tab anymore,
whereas previously it used to
When I open a 2nd file, at this point the tabset appears
Is this a bug, or an intentional change? I much prefer the old way, and to
be honest I preferred the fixed width tabs too
There's an odd behaviour with project windows disappearing when clicking the Zoom (+) button. When TM2 first opens, it reopens any preexisting windows. Then when I click on the Zoom button the window zoom shrinks and ultimately disappears. I cannot bring it back from hidden status after that.
Anyone else experience this behaviour? It only started happening recently, maybe within the last 2 or 3 builds.
Hey, I don't mean to cause a stir, but for me TextMate's code folding is
generally just broken. I've spent a lot of time lately working on Jinja2
templates and it just doesn't handle them well at all and sometimes code is
removed accidentally. I've had the same thing happen with messier PHP
Is there a way to just turn this off? Toggling folding levels at "All
Levels" does not address the problem, some "weirder" blocks of templates
(and other bits of messier code that I, of course, didn't write) still
remain folded weirdly.
I'm developing a new bundle for a scripting language. For the "Run" command I'd like to make usage of TM's TextMate::Executor library. Fine.
But I was confronted with two subjects for a discussion:
In order to use TextMate::Executor one should execute "TextMate.save_if_untitled('foo')" in beforehand. But I'd like to allow to the user that s/he runs either the entire document or only a selection. With the current implementation this doesn't work, so I suggest the following change (adding of the first 6 lines of code and a new argument):
save_current_document.rb line: 33ff
def save_if_untitled(temp_ext='tmp', ignore_selection=true)
if not ignore_selection and not ENV['TM_SELECTED_TEXT'].nil?
ENV['TM_FILEPATH'] = nil
if not ENV['TM_SELECTED_TEXT'].nil?
ENV['TM_DISPLAYNAME'] += ' (Selection)'
return unless ENV['TM_FILEPATH'].nil?
ENV['TM_FILEPATH'] = TextMate::IO.tempfile(temp_ext).path
ENV['TM_FILENAME'] = File.basename(ENV['TM_FILEPATH'])
ENV['TM_FILE_IS_UNTITLED'] = 'true'
This approach does't break the default behaviour. Only if the developer would like to add that functionality s/he has only set the second argument to "false". By adding "(Selection)" or whatever to TM_DISPLAYNAME the user will be notified additionally.
2) TextMate::Executor.run -> version
The interpreter I'm working with is an "hybrid". If you start it without arguments or with arguments which can't be interpreted as a file name the interpreter starts in the GUI mode, i.e. a real application with windows etc. pops up. Otherwise, if you pass as first argument a valid file path plus optional arguments, the interpreter works like Perl, Python, etc. in a command line mode.
The current TextMate::Executor.run implementation has a nice feature, you can get the current version number from the current installed interpreter or compiler as default BUT you are NOT able to avoid it.
In my case the interpreter doesn't catch these kind of querying, in other words I can set the ":version_*"-options to whatever the GUI is popping up and tells me stories about errors. Finally I ended up to write a special script which returns the version number and I call it via:
:version_args => ENV["TM_BUNDLE_SUPPORT"] + "/bin/version.praat"
but I believe one could solve this kind of problem quite easily, namely if the developer sets explicitly ":version_args => nil" the version querying won't be executed. To achieve that one has to change one single line:
executor.rb line: 99
version = (not options[:version_args].nil?) ? parse_version(args, options) : ''
Did I miss something?
I found a bug while argument parsing in several DIALOG2 commands:
"$DIALOG" x-insert --text "--Pitch"
"$DIALOG" tooltip --text "--Pitch"
if you execute theses commands (via CTRL+R or within a script) DIALOG2 will fail due to the fact that the text argument begins with two "-".
In Recent Projects window that’s opened by ⌘⇧O when one removes a project using ⌘⌫ a “Trash” sound is heard.
This scared the shit out of me and I immediately went to Trash to check if the actual folder was removed and not just the link in TM.
I don’t know if it’s an intended behavior but I’m pretty sure it’s a wrong one as I almost had a small heart attack :)