I am just posting this here for the heck of it.
I just updated to b9 with the latest bundles via svn and I just gotta say WOW. The new theme support is outstanding. Although it doesn't quite make sense to me yet, how to navigate those features and even create my own theme, but it looks so much better!!!
This is the first time I would call a text editor "fun." That's how great this is! Everything about it shines, it's so much better even than the b5 I was using with the older bundles...
Just two brief comments:
1. The folding keystrokes are great but it doesn't make sense the way it works. folding to level two, it seems, should logically fold TO level two, not just at that level. Meaning, if you fold to level two, then fold to level one, if you "unfold" level one it seems odd that level two is still folded! I can't think of a logical reason for it to work this way... just my 2cents...
2. I can't figure out the keystrokes to switch between tabs but it seems like they should be the same as Safari if possible....
Keep up the great work. This is in my top five favorite Mac apps, I can't imagine programming without it anymore!!!
Kindest regards, Raymond
On May 22, 2005, at 18:32, Raymond Brigleb wrote:
I just updated to b9 with the latest bundles via svn and I just gotta say WOW. The new theme support is outstanding. Although it doesn't quite make sense to me yet, how to navigate those features and even create my own theme, but it looks so much better!!!
Thanks! And the GUI will improve to make things more clear :)
- The folding keystrokes are great but it doesn't make sense the
way it works. folding to level two, it seems, should logically fold TO level two, not just at that level. [...]
hmm... I personally do use toggle foldings at level and only want it to be at that level. This arises e.g. if I have a “list” (either plist or html ul/ol list) at level 3-4 and want all list items to be folded (so the list more resemble small bullet points), or e.g. when I want to fold all methods of a class, but I don't want to fold the class itself or the outer namespace declaration.
- I can't figure out the keystrokes to switch between tabs but it
seems like they should be the same as Safari if possible....
It's cmd-option left/right (shown in the navigation menu). Previously Safari used cmd-shift left/right which was rather bad, since that's select to begin/end of line (even in Safari forms). But starting with Tiger, Safari now use cmd-{/}. I could use these keys for consistancy, but probably in addition to the current.
It's cmd-option left/right (shown in the navigation menu). Previously Safari used cmd-shift left/right which was rather bad, since that's select to begin/end of line (even in Safari forms). But starting with Tiger, Safari now use cmd-{/}. I could use these keys for consistancy, but probably in addition to the current.
I quietly second this. I have to admit that it bugged me a bit since the first time I used TextMate. I understand the conflict with the Apple-style text navigation (though I never personally use CMD to navigate -- I use PC-style home/end [fn-left/right]), but cmd-opt-left/right is too useful a keystroke to tie up with something which might just as well be the same.
In particular, I have always found cmd-opt-left/right to be far and away the most natural shortcut for virtual desktop naviation (with cmd-ctrl-left/right switching desktops and taking the foreground window with you). Having Safari use cmd-shift-arrow and TM use cmd-opt-arrow effectively prevents using *either* for virtual desktop switching.
Just a small frustration I hadn't mentioned before, but thought I'd raise since you mentioned optionally adding support for cmd-shift-arrow. It's fine with me if you keep both (as system-wide keystrokes like vdesktop switching override application shortcuts, anyway), though, of course. -jrk
On Jun 1, 2005, at 22:00, Jonathan Ragan-Kelley wrote:
Just a small frustration I hadn't mentioned before, but thought I'd raise since you mentioned optionally adding support for cmd-shift-arrow.
No, it was cmd-{ and }. Cmd-shift-arrow is still for selecting. And I'm quite sure that the reason Apple changed the Safari keys was because people bitched about this (at least I have read dozen of people mention this unfortunate choice, and has been bitten by it myself countless times, despite the fact that I rarely use Safari)!
Why they didn't choose cmd-option-arrow is beyond me, seeing how this is also used by Xcode (so it's not just TextMate), and cmd-{ and } would be cmd-option-shift-8 & 9 on a lot of European keymaps, so this is really a horrible choice for international support.
Btw: if you're not aware, you can change the menu keys of any application using System Preferences -> Keyboard & Mouse.
-
Allan Odgaard -
Jonathan Ragan-Kelley -
Raymond Brigleb