What a bizarre packaging choice: bash/curl command to pull a shell script to pull and compile a github project which compiles and installs a Text Mate plugin.
Did you read the contents in your standard web browser, like I did? What if it sent back a different set of commands if the user agent matched that of cURL?
Well, you're still free to curl the contents of the URL into a standard text file, and view it with the text editor of your choice (maybe even TextMate!).
What matters is that it's a terrible hack. Even ignoring the security concerns with "install this completely untrusted code from the internet": there's no way to cleanly recover/uninstall if something breaks; there's no way to tell what version you have (not even in theory, as this clones HEAD!).
Most importantly, there's no chain of authority here. In the Linux world, for example, your packages generally come from the distro and are signed. Down a layer, they might come from a third party repo (rpmfusion, say), which is still a large organization with high visibility and good auditing. Down farther still, there are tools like Launchpad or openSUSE's OBS which allow you to build installable pacakges of your own, but these are still distributed out of a managed infrastructure and your identity is reasonably tracked. Finally at the bottom are the people ("developers") who like to pull raw source code and compile it. These people are expected to be communicating as part of a project, so they can be warned about compatibility goofs or (goodness forbid) the occasional malware incident.
This "pull and install automatically" gives you the ease of use of the top level, but an even weaker promise of authority than even the bottom level. That's a bad thing.
That's a little different, pow.cx and rvm are running installer scripts to get other scripts into place on your system and add them to your .bash_profile.
This is having you run through a bunch of rigamarole to download and compile source for a plugin, and then triggering textmate to install said plugin, when you could achieve the same effect by distributing the binary plug-in and having the user double-click it.
Piping things from curl into bash is about the dumbest thing you can do security wise. Except if you also use an URL shortener, which means that in addition to trusting the author not to be evil, you're also trusting the shortener service to deliver what you (or the author) expected.
As far as I can tell, that piece is really deceptive. You can drag floating windows from the same application that would normally float over the fullscreen app. You cannot, for example, fullscreen TextMate on your primary display and have Safari or Photoshop on the secondary.
You can also use multiple spaces. Fullscreen editor in one. Full screen terminal in another. Fullscreen browser in a third, to defeat the supposedly distractionless environment a fullscreen app does its best to offer you.
My app Maximizer can do this dynamically for pretty much any app on your system (including TextMate, but also stuff like Firefox or Spotify). It's SIMBL based, but the code is clean and hopefully open source soon: http://chpwn.com/apps/maximizer.html
I'm using maximizer with TextMate and Chrome. Works pretty well, thanks! The only caveat is that to see the drawer, you have to hide it and show it again.
Sorry, I'm actually using maximizer with Chromium 14 and the real full screen with Chrome dev. The only difference though is the "curtain" button, for which I don't have much use.
this would be spot on if it handled the drawer nicely and the opening of folders. Mind it seems that Sublime Text 2 also poorly handles new files opened when the app is fullscreen. A proper implementation would once again make TextMate unbeatable on OS X.
Glad it's there in some way or another though. Using fullscreen a lot more than I thought I ever would.
This might sound kind of trivial, but the lack of split panes (and no hope on the horizon) is what finally pushed me over the edge to learning vim. Haven't looked back :)
Ok, this is the wrong place to ask, but when I'm using unix text editors I'm reasonably happy EXCEPT I don't understand how anyone could use a text editor without being able to click to move the insertion point where they want it to be. Furiously leaning on the arrow keys is way too slow.
How does one solve this? is there a way to make the terminal accept mouse input? I've mostly only used pico/nano which I understand is similar to vi, et al. but maybe don't have a way to do this where other editors do?
As noted, you can run vim or emacs in a way where you can mouse where you want to go. In practice, there's usually a way to get to the place you want to be via some other command. For vi, you can usually use /search to get where you want. One of my most-used vi commands that I miss in other editors is f[char]. It moves you to the next instance of [char] on your current line. Things like f= or f( are great for bouncing through a line of source code. I wish textmate (chocolate, sublime, whatever) had a quick keyboard equivalent to that.
I use MacVim. Keyboard navigation works great for me when moving around small areas, but I use the scrollwheel and clicking all the time for moving around larger areas of a file (and for navigating NERDtree).
Yikes.