TextMate

textmate@lists.macromates.com

10171 discussions

by Tim Harper

What's this about the Dialog2 bundle... and what's this I hear about a public AppleScript API for textmate (as mentioned in a commit to the Dialog2 bundle)? Can someone enlighten me and possibly post a link, or two? I'd like to learn about Dialog2, specifically if it can help with the git bundle. I'm really interested to know if any of the following are possible: * Is it possible to open up a new html-output pane in textmate, bound to a process, invoked by an already running bundle command? * Is it possible, through the AppleScript-API, to list all of the tabs that are open. (currently using the fantastic TMTOOLS plugin to do it, but would be nice if this feature became part of core, as I'm not sure if TMTOOLS has been the cause of some unstability i've been experiencing)? * What new dialogs are provided by Dialog2? If someone's got a quick answer, I'd appreciate it :) Though, as I've invested little time to writing this message, I'd not be terribly disappointed if it was ignored. Thank you beloved TextMate community, Tim

16 years, 10 months

Ruby versions differ from shell and she-bang

by ollie saunders

A snippet with this content: `/usr/bin/env ruby -v` Tells me that it is using /opt/local/bin/ruby (1.8.6) Yet a command with this content: #!/usr/bin/evn ruby puts RUBY_VERSION Tells me that it is using /usr/bin/ruby (1.8.2) And yet if I use the she-bang outside of textmate, the correct 1.8.6 version is used: $ echo '#!/usr/bin/env ruby' > ruby_test $ echo 'puts RUBY_VERSION' >> ruby_test $ chmod +x ruby_test $ ./ruby_test 1.8.6 $ Any anyone tell me how to fix this? I wish to use 1.8.6 for everything. I've read that environment.plist might be part of the solution but I can't find such a file. If I need to create a new one, I don't know what to put in it. Many thanks -- View this message in context: http://www.nabble.com/Ruby-versions-differ-from-shell-and-she-bang-tp163104… Sent from the textmate users mailing list archive at Nabble.com.

16 years, 10 months

SVN Blame not working

by REBELinBLUE

I am having trouble with the svn blame command in the SVN bundle. Everything else works fine, but not that. I get NoMethodError reason: undefined method `+' for nil:NilClass trace: /Applications/TextMate.app/Contents/SharedSupport/Bundles/Subversion.tmbundle/Support/format_blame.rb:49 /Applications/TextMate.app/Contents/SharedSupport/Bundles/Subversion.tmbundle/Support/format_blame.rb:43:in `each_line' /Applications/TextMate.app/Contents/SharedSupport/Bundles/Subversion.tmbundle/Support/format_blame.rb:43 I have searched and none of the solutions that have previously been mentioned work, the files I've tried are definitely under version control (because the info command works on them, and svn blame works from the command line). I have tried a fresh install of Textmate, with only Ciarán Walsh’s ReMate and TMQuicklook plugins installed and it is still not working. I verified this by running "locate TextMate" after running "sudo /usr/libexec/locate.updatedb" and all I got was the output you would expect (all the files in textmate.app, and the 3 plugins with their content in my users application support folder) -- View this message in context: http://www.nabble.com/SVN-Blame-not-working-tp16176714p16176714.html Sent from the textmate users mailing list archive at Nabble.com.

16 years, 10 months

[ANN] New Velocity Bundle

by Thomas Aylott - subtleGradient

Howdy. I just finished a new bundle for Velocity. If you want to try it out it's available on Subversion at "http://macromates.com/svn/Bundles/trunk/Review/Bundles/Velocity.tmbundle " Or check it out from the terminal with: svn co http://macromates.com/svn/Bundles/trunk/Review/Bundles/Velocity.tmbundle Velocity.tmbundle; open Velocity.tmbundle This is loosely based on the original Velocity bundle by Tom Armitage Please let me know if you encounter any bugs or have any suggestions. —Thomas Aylott – subtleGradient—

16 years, 10 months

DIALOG2 - alert: display as sheet > suggestion

by Hans-Jörg Bibiko

HI, sorry for maybe double-posting it, but I got an error for textmate- dev list. (?) __ I've just had a look at the new DIALOG2 stuff. Very nice ;) Here comes a suggestion to allow the user to display the alert as sheet bound to the current document window: If option -e or 'sheet' is given it shows the alert as sheet. CODE: ######################################################################## ## #import "../Dialog2.h" #import "../TMDCommand.h" #import "../OptionParser.h" /* echo '{alertStyle = warning; buttonTitles = ('OK'); messageTitle = 'test'; informativeText = 'Testing';}' | "$DIALOG" alert "$DIALOG" help alert "$DIALOG" alert -s critical -m "FOOL!" -t "test" -1 foo -2 bar -3 baz "$DIALOG" alert -e -s critical -m "FOOL!" -t "test" -1 foo -2 bar -3 baz */ // ========= // = Alert = // ========= @interface TMDAlertCommand : TMDCommand { } @end @implementation TMDAlertCommand int sheetReturn; + (void)load { [super registerObject:[self new] forCommand:@"alert"]; } static option_t const expectedOptions[] = { { "m", "message", option_t::required_argument, option_t::string, "Message title."}, { "t", "text", option_t::required_argument, option_t::string, "Informative text for the alert."}, { "s", "alert-style", option_t::required_argument, option_t::string, "One of warning, critical or informational (the default)."}, { "1", "button1", option_t::required_argument, option_t::string, "Button 1 label."}, { "2", "button2", option_t::required_argument, option_t::string, "Button 2 label."}, { "3", "button3", option_t::required_argument, option_t::string, "Button 3 label."}, { "e", "sheet", option_t::no_argument, option_t::none, "If given displays alert as sheet."}, }; - (void)handleCommand:(CLIProxy*)proxy { // NSFileHandle* fh = [options objectForKey:@"stderr"]; SetOptionTemplate(proxy, expectedOptions); NSAlertStyle alertStyle = NSInformationalAlertStyle; NSString *alertStyleString = [proxy valueForOption:@"alert-style"]; NSDictionary *resultDict = nil; NSAlert *alert = [[[NSAlert alloc] init] autorelease]; int offset = 0; if([alertStyleString isEqualToString:@"warning"]) { alertStyle = NSWarningAlertStyle; } else if([alertStyleString isEqualToString:@"critical"]) { alertStyle = NSCriticalAlertStyle; } else if([alertStyleString isEqualToString:@"informational"]) { alertStyle = NSInformationalAlertStyle; } [alert setAlertStyle:alertStyle]; if([proxy valueForOption:@"message"]) [alert setMessageText:[proxy valueForOption:@"message"]]; if([proxy valueForOption:@"text"]) [alert setInformativeText:[proxy valueForOption:@"text"]]; // Setup buttons offset = NSAlertFirstButtonReturn; if ([proxy valueForOption:@"button1"]) [alert addButtonWithTitle:[proxy valueForOption:@"button1"]]; if ([proxy valueForOption:@"button2"]) [alert addButtonWithTitle:[proxy valueForOption:@"button2"]]; if ([proxy valueForOption:@"button3"]) [alert addButtonWithTitle:[proxy valueForOption:@"button3"]]; BOOL modal = YES; if([proxy valueForOption:@"sheet"]) modal = NO; // Show the alert if(modal) { int alertResult = ([alert runModal] - NSAlertFirstButtonReturn); resultDict = [NSDictionary dictionaryWithObject:[NSNumber numberWithInt:alertResult] forKey:@"buttonClicked"]; [TMDCommand writePropertyList:[NSString stringWithFormat:@"%d",sheetReturn - offset] toFileHandle:[proxy outputHandle]]; } else { id documentWindow =nil; enumerate([NSApp windows], id item) if([item isKindOfClass:NSClassFromString(@"NSWindow")]) if([item isKeyWindow]) documentWindow = item; sheetReturn = -1; [alert beginSheetModalForWindow:documentWindow modalDelegate:self didEndSelector:@selector(mySheetDidEnd:returnCode:contextInfo:) contextInfo:NULL]; [NSApp runModalForWindow:[alert window]]; [TMDCommand writePropertyList:[NSString stringWithFormat:@"%d",sheetReturn - offset] toFileHandle:[proxy outputHandle]]; } } -(id)mySheetDidEnd:(NSWindow *)sheet returnCode:(int)returnCode contextInfo:(void *)contextInfo { [NSApp endSheet:sheet]; sheetReturn = returnCode; [NSApp stopModal]; return nil; } - (NSString *)commandDescription { return @"Show an alert box."; } - (NSString *)usageForInvocation:(NSString *)invocation; { return [NSString stringWithFormat:@"%@ ¬´options¬ª\n\nOptions:\n%@", invocation, GetOptionList(expectedOptions)]; } @end ######################################################################## ## Any comments? Cheers, --Hans

16 years, 10 months

TextMate overwrites symlinks

by Tim Harper

Just ran into this problem today. In our project, we have several files that our mirrored, so we use git to manage the symlinks. Today we discovered that you can open a symlinked file, but when you try to go and save it, the symlink is erased and replaced with a brand new file, rather than updating the contents of the file that the symlink points to. Is this a known issue? Is there any suggested workaround for it? (other than, make sure you don't edit a symlinked file?) Thanks, Tim

16 years, 10 months

Bug in Ruby bundle: Control-Q comment reformatting produces an error for long words

by Bill McNeill

I've found a bug in the Ruby bundle for Textmate. Under certain circumstances, using Control-Q to reformat comment code raises an exception that spews error code into the source. Is this the right forum to post bugs in Ruby bundles? The problem occurs if you have a comment that contains a single word that goes past column 79. For example, in the following code (also attached) the x's in the comment extend out to column 80: # xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx def func(x,y) x+y end If you place the caret inside the comment and press control-Q you see the following: /Applications/TextMate.app/Contents/SharedSupport/Bundles/Source.tmbundle/Support/bin/rubywrap.rb:365:in /bin/bash: +': invalid option Usage: /bin/bash [GNU long option] [option] ... /bin/bash [GNU long option] [option] script-file ... GNU long options: --debug --dump-po-strings --dump-strings --help --init-file --login --noediting --noprofile --norc --posix --rcfile --restricted --verbose --version --wordexp Shell options: -irsD or -c command or -O shopt_option (invocation only) -abefhkmnptuvxBCHP or -o optionwrite' from /Applications/TextMate.app/Contents/SharedSupport/Bundles/Source.tmbundle/Support/bin/rubywrap.rb:408 def func(x,y) x+y end This doesn't happen if the word in the comment stops before column 80. This isn't an impossible scenario because it's easy to have a URL in your documentation that's more than 80 characters long. -- Bill McNeill http://staff.washington.edu/billmcn/index.shtml

16 years, 10 months

Black PDF window which never renders from LaTeX docs; Acrobat Pro to blame?

by Ashley

I am a recent TextMate convert. Part of what swayed me was the range of bundles including LaTeX. I'm also pretty new to LaTeX. I have been using TextMate to render LaTeX with various engines including XeTeX. It has been working perfectly on everything until now. Now when I Apple+R to render I get the regular panel for a moment, along with engine output/info, then it goes black but the spinner stays. It "runs" forever like this. The behavior happens on any engine and document content/size. The documents render to PDF fine from TeXShop. None of that setup has changed. I installed the bleed version of TextMate two days ago to see if it might fix it. No difference. What *has* changed in my setup is I installed the CS3 Adobe web suite (a new paid/registered version, not warez) which includes Acrobat Professional. I am guessing this has hooked/broken some PDF meta-info somewhere. Any pointers where to look to fix this? Acrobat includes an uninstaller but I'd rather not do that. Is it something that can be updated in the LaTeX bundle? I think this is likely since other LaTeX apps are still rendering to PDF, only TextMate's behavior changed. Thanks for looking at this! -Ashley

16 years, 10 months

Bug in Ruby bundle: Control-Q comment reformatting produces an error for long words

by Bill McNeill

Repost because the original message was garbled... I've found a bug in the Ruby bundle for Textmate. Under certain circumstances, using Control-Q to reformat comment code raises an exception that spews error code into the source. Is this the right forum to post bugs in Ruby bundles? The problem occurs if you have a comment that contains a single word that goes past column 79. For example, in the following code the x's in the comment extend out to column 80: # xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx def func(x,y) x+y end If you place the caret inside the comment and press control-Q you see the following: /Applications/TextMate.app/Contents/SharedSupport/Bundles/Source.tmbundle/Support/bin/rubywrap.rb:365:in /bin/bash: +': invalid option Usage: /bin/bash [GNU long option] [option] ... /bin/bash [GNU long option] [option] script-file ... GNU long options: --debug --dump-po-strings --dump-strings --help --init-file --login --noediting --noprofile --norc --posix --rcfile --restricted --verbose --version --wordexp Shell options: -irsD or -c command or -O shopt_option (invocation only) -abefhkmnptuvxBCHP or -o optionwrite' from /Applications/TextMate.app/Contents/SharedSupport/Bundles/Source.tmbundle/Support/bin/rubywrap.rb:408 def func(x,y) x+y end This doesn't happen if the word in the comment stops before column 80. This isn't an impossible scenario because it's easy to have a URL in your documentation that's more than 80 characters long. -- Bill McNeill http://staff.washington.edu/billmcn/index.shtml

16 years, 10 months

Problems with Rails Bundle and RakeMate

by Sebastian Friedrich

Lately, i've been experiencing various issues with the Rails Bundle: - none of the generator tasks (controllers, models, migrations etc.) work anymore. I just get an empty confirmation window and the tasks are not run. - when running any rake tasks, i get "stack level too deep" errors:. For insatnce, here's the output from "Migrate to current" command: RakeMate r6193 rake aborted! stack level too deep (See full trace by running task with --trace) (in /Library/WebServer/railsapps/sparkle) Done Rake tasks and generator tasks work perfectly fine from the command line. I'm using current Rails Bundle from trunk, but also tried the one that came with the lastest TM release. I'm running on Leopard, Ruby 1.8.6; projects are Rails 2.0.2, but it also seems to happen with Rails 1.2 projects. Any ideas? Thanks. Sebastian

16 years, 10 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

TextMate