Earlier quoted context omitted.
See, I tried to use Visual Studio and I must admit I don't "get it". Actually, I'm not mocking you there. This is the truth. But I don't get many things. So I end up compiling with VS and editing code in Emacs, because VS does not have a shortcut to switch between files quickly and because VS does not integrate with Git properly and because VS does not have keyboard macros and because I just don't like VS much. Funny…
ctrl + tab to switch between open files. ctrl + w, ctrl + s to focus the project explorer, from where you can use the arrow keys to select a file from the current project.
Sublime Text 2.0 Released
311–320 of 358 posts
Re: Sublime Text 2.0 Released
#312Earlier quoted context omitted.
And why would I want to spend years crafting the perfect .vimrc for myself when tools exist that already do 80% of that better and without any configuration? I say this with a carefully crafted and organized .vim folder.
Upvoted. And I have an .emacs.d folder carefully crafted over 20 years.
Re: Sublime Text 2.0 Released
#313Re: Sublime Text 2.0 Released
#314Earlier quoted context omitted.
I continue to be haunted by something a good artist friend used to say: "Don't obsess over your tools. They are not the goal". This would ring in the back of my head as I spent many hours configuring my editor / shell / terminal setup. It felt like a guilty pleasure. It dawned on me however, that what had drawn me to programming in the first place was a sublime text editor (TextMate), and that my business is in fact…
>>> "Don't obsess over your tools. They are not the goal" Actually, someone from design background once told me "Good tools produce great work".
Re: Sublime Text 2.0 Released
#315Hm, Am I the only one who spends hours in vim each day with ~15 lines in my .vimrc and almost zero plugins? At some point I think I realized that no matter how feature-rich my editor was, the main thing stopping me from writing good and fast code was _thinking_, not configuring my text editor.
Configuring my text editor isn't the main thing stopping me from writing good and fast code, but a badly configured editor does inhibit it. Working with 0 plugins is not a bad deal, but I am missing the point why I would want to.
Sure I can manually comment/uncomment(nerdtree), manually write nested html(zenconding), manually balance parens when writing clojure/racket(paredit, autoclose), do a :ls and buffer switch(bufexplorer), diff swap file and on disk file and recover accordingly(recover)....etc etc.
These aren't the most important things when it comes to writing good code. That doesn't mean it doesn't help. My .vimrc is 300 lines, and there is nothing in there which I don't need or which doesn't help me write fast code.
These simple abbreviations save me a ton of irritation:
inoremap \1 %>2hi
inoremap \2 %>2hi
inoremap \3 {%%}2hi
inoremap \4 {{}}2hi
No one is contesting you can't type '{{ some_crap }}' repeatedly, but I don't see how doing that is beneficial in any way.Adding simple customization to vimrc is simple. Plugins are even simpler. Committing the shortcuts to muscle memory is not as simple. But if you really need the customization/plugin, that means you will be using it and it will become muscle memory very quickly.
Thinking is the major hurdle when it comes to writing good code, but it isn't the only one. The other factors are important.
Re: Sublime Text 2.0 Released
#316As an Intellij user (and Emacs way before that) I'm trying to give this a chance, but I see no way to click-navigate through source code. Am I missing something? I tried installing SublimeCodeIntel, and that lets me (occasionally) navigate to symbols in the current file. But I don't seem to be able to click through to symbols defined in other files/classes. Am I missing something fundamental, or is this strictly the…
Why do you want to use your mouse while coding?
This reminds me of the times I was tasked with the job of assisting junior programs with their code.
At times their mouse usage habits would drive me nuts!!!
I would say something like cut those three lines and move them outside of the loop.
I would watch them try to mark the three lines of code with the mouse.
That would take a second or two.
Then they would right click on the mouse to bring up the copy popup menu only to accidentally hit the left mouse button and remove the marked area forcing them to start again.
Five or six seconds later the task was still not done and I would say please move and let me jave a go.
A few key strokes later the cut and past is done.
Re: Sublime Text 2.0 Released
#317Re: Sublime Text 2.0 Released
#318Earlier quoted context omitted.
Why do you want to use your mouse while coding?
Because when browsing code it's faster to click on a method name than to navigate to it with the keyboard.
In the Zeus editor you just have to place the cursor on the name (using the keyboard or mouse) and hit the F12 key.
Re: Sublime Text 2.0 Released
#319Earlier quoted context omitted.
In my experience, Sublime Text hits that exact niche you're describing. It does the things important to programmers, or people who work with lots of text, well enough that you don't have to worry about any plugins, etc. But it also offers a great plugin ecosystem for just about anything you want. Turning on "vintage" mode is a great plus, too, especially coming from vim.
And, like every vim emulator ever (with the possible exception of Emacs' spawn), it doesn't support all the vim keystrokes I use daily. My brain knows vim, and I'll code in vim. You don't see professional pianists perform on electric keyboards.
Classical pianists don't. Every other kind of professional pianist does it all the time.
Except if you don't consider someone like Keith Jarrett, Herby Hancock or Chick Corea a "professinal pianist".
As for "not supporting all the vim keystrokes", ever heard of the 80/20 rule?
Re: Sublime Text 2.0 Released
#320I'd like to use Sublime Text if it had vi bindings.
Enable Vintage and then install VintageEx from https://github.com/SublimeText/VintageEx
Very simple - and brilliant!