Can someone explain the difference between command-p and command-t?
On OS X, they appear to do the same thing. On Windows, ctrl-t doesn't seem to do anything. I don't have Sublime set up on Linux so I can test there. I suspect the author has an older configuration since he's been using it for almost 2 years, and that the keybinding probably changed since then to cmd-p.
Configuring Sublime Text 2
21–30 of 92 posts
IIRC, ⌘P was Sublime's original mapping, and then ⌘T was added on Mac because the then-extremely-popular TextMate had a well-known ⌘T function that was similar.
Re: Configuring Sublime Text 2
#22As a python programmer, these were the first two settings I configured after installing Sublime Text.
"tab_size": 2,
"translate_tabs_to_spaces": true
You can either set them as Preferences > Settings - Default or Settings - Syntax specificRe: Configuring Sublime Text 2
#23Earlier quoted context omitted.
An even better one IMO is @, same thing as with # but it uses symbols.
You can get that via Ctrl-R (or Cmd, if on a Mac). Ctrl-; brings up fuzzy matching for words in the file.
Cmd-R is just for jumping to symbols in the current file, Cmd-T+@ to jump to a symbol on any given file.
Re: Configuring Sublime Text 2
#24Does sublime text 2 work well with CL or Haskell?
I use it to write Haskell. The syntax highlighting screws up the first line of multiline record declarations. Out of the box, it can't run a Hoogle search or launch GHCI like TextMate did. It's definitely not a fully-featured Haskell IDE, but it's a usable basic editor. Depending on what you're used to, it may or not be adequate. I switched because I liked the default color theme better (... I mean... because TextMate was being abandoned).
Re: Configuring Sublime Text 2
#25The biggest win I've had from configuring Sublime Text is in setting up build systems. Specifically, configuring F4/shift-F4 (skip to next/previous error). The build system integration is rudimentary (and I hope that's a focus for Sublime Text 3) but "skip to next error" is all you really need to be productive.
Re: Configuring Sublime Text 2
#26Re: Configuring Sublime Text 2
#27My first piece of advice is to set up a command line alias for Sublime... Sublime ships w/ a command-line executable: /usr/bin/subl
Nitpick: the trailing 'l' has always seems superfluous to me - my alias is 'sub'
Re: Configuring Sublime Text 2
#28My first piece of advice is to set up a command line alias for Sublime... Sublime ships w/ a command-line executable: /usr/bin/subl
This hasn't been working for me for some reason on OSX, the posted alternative however did work so I'm quite excited!
Re: Configuring Sublime Text 2
#29If you're using Sublime I'd highly recommend writing some Snippets, there's plenty you can write and it gets you digging into Sublime's docs. Helped me get used to Sublime a lot more.
Re: Configuring Sublime Text 2
#30> "trim_trailing_white_space_on_save": true, # trims trailing whitespace
bad for Markdown, as it will delete spaces that are needed for newline, I believe.