Lord, give us the wisdom to utter words that are gentle and tender, for tomorrow we may have to eat them.
Sen. Morris Udall
I am doing a startup!
Cross-browser testing from your browser!
I have written my fourth book!
Be faster than Larry Wall at command line!
You're replying to a comment by argv.
The merits of Vim aside, dum8d0g makes a point worth considering with respect to *all* software. Too much customisation.
How much is "too much"?
Consider if you were by chance left without all your customisations, and you had to get things done. How long would it take you to get back up to speed?
Learning to work with default configurations and "base" software, and to use the simplest means possible to accomplish tasks can be a beneficial practice. Among other things, it makes recovery easier, reduces fear of data loss and encourages *your* portability.
We have all perhaps at some time become enthused with the potentials of customisation. Indeed it is a channel for one's creativity toward improving efficiency. But... do you agree that:
"Limitation breeds creativity"
For reasons I will not explain, not every computer will have Vim, perl, xargs, bash, etc. *But*... most all of them will have a very "old" line or stream editor and a very "old" shell. These programs are always present, decade after decade, for reasons I will not explain.
Personally, for text clips, I prefer the ::multiple copy-paste buffer:: of tmux (a GNU screen alternative). It is small, simple stable (more so than screen, in my experience), and it compiles easily. It allows, with some creativity, clips to be copied, stored, loaded and pasted across *all* applications, whether to or from the console or X windows. And of course one can set key bindings, just like Vim or screen.
(why do I need your e-mail?)
It would be nice if you left your e-mail address. Sometimes I want to send a private message, or just thank for the great comment. Having your e-mail really helps.
I will never ever spam you.
(Your twitter handle, if you have one.)
* use <pre>...</pre> to insert a plain code snippet.
* use <pre lang="lang">...</pre> to insert a syntax highlighted code snippet.
For example, <pre lang="python">...</pre> will insert Python highlighted code.
* use <code>...</code> to highlight a variable or a single shell command.
* use <a href="url" nospam>title</a> to insert links.
<a href="url" nospam>title</a>
* use other HTML tags, such as, <b>, <i>, <blockquote>, <sup>, <sub> for text formatting.
Type the word "network_151": (just to make sure you're a human)
Please preview the comment before submitting to make sure it's OK.
Peter Krumins' blog about programming, hacking, software reuse, software ideas, computer security, browserling, google and technology.
Reach me at:
Or meet me on:
Subscribe through an RSS feed:
(what is rss?)
Subscribe through email:
Enter your email address:
Delivered by FeedBurner
I love to read science books. They make my day and I get ideas for awesome blog posts, such as Busy Beaver, On Functors, Recursive Regular Expressions and many others.
Take a look at my Amazon wish list, if you're curious about what I have planned reading next, and want to surprise me. :)
See all top articles
See all downloads
See more detailed list of recent articles
See more detailed category information
See more detailed list of all articles