Steve Losh's .vimrc • Hacker News Board

Re: Steve Losh's .vimrc

#101

Post by gerrit » Sat, Nov 19, 2011, 3:13 PM UTC

sjs wrote: post #73

JoshTriplett wrote: post #66

Earlier quoted context omitted.

That's a huge amount of trust you've placed in bit.ly, and in insecure http. You might at least consider typing out https://bit.ly/newbox so that you only have to trust bit.ly. Better yet, memorize the URL that bit.ly links to. Also, why do you symlink your dotfiles into your cloned git repo, rather than just checking out the git repo as ~? Personally, I just move the .git directory from the clone to ~, and then "git…

I'm lazy and don't want to type out the github URL, but you're right I should place the redirection under my control and use HTTPS. Honestly though I cannot think of a single reason why anyone would want to hijack my script. I don't do anything very interesting that would make my machine a lucrative target for that sort of malicious activity. I'm a very small fish in a massive pond. Also due to laziness I don't want…

There’s always git.io: https://github.com/blog/985-git-io-github-url-shortener

Re: Steve Losh's .vimrc

#102

Post by crazydiamond » Sun, Nov 20, 2011, 6:26 AM UTC

swah wrote: post #78

nickknw wrote: post #47

I didn't know this was possible: " Resize splits when the window is resized au VimResized * exe "normal! \ =" That's really handy. Also, this part made me smile: " Heresy inoremap I inoremap A

(I love both editors) That's something disgusting about Vim - mapping to other keys instead of commands. In Emacs its much nicer IMO: (global-set-key (kbd "C-a") 'beginning-of-line)

You can bind a key to a command too. However, mapping to keys allows you to create your own. To give you a crude example, you could map a key to go down 5 times (5j). A real example would be more complicated for some specific task -- jump to other window, maxmimize it, go down to 5th line or some bookmark, etc.

Re: Steve Losh's .vimrc

#103

Post by sashahart » Mon, Nov 21, 2011, 4:01 AM UTC

sramov wrote: post #96

exDM69 wrote: post #91

Earlier quoted context omitted.

I don't think that the author wrote his 1200 lines of .vimrc in one sit. More likely it's years of accumulated 1-2 line additions and removals. My vimrc has slowly accumulated, I add 1 or 2 new keybinds every now and then and I might remove them later if I notice they don't suit my workflow. Most of my changed keybindings are related to making Vim usable with my native keyboard layout (finnish/swedish). Also per-lang…

My point was, time better spent is coding, not dicking around (and relying) on .vimrc. We often forgot about the essence of things such as typing the actual code or words, and focus on tools. Better investment is learning how to properly type than having countless little helpers which are nothing more than debt. Increasing complexity in all areas of life really is troublesome.

There is no dichotomous distinction between coding and using vim to automate tasks. The latter is part of the former - no different from using q or @ or .