Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Might as well be using Notepad on Win32. :) Give vim some time and you will learn it. It takes a little while.
    • Give vim some time and you will learn it. It takes a little while.

      I found vi to be like perl in one important way. I could use it effectively after learning a small subset of its capabilities. Then, every 6 months or so, I'd read through the manual again and add 4 or 5 more idioms to my repetoire. When the subsequent 6 month iteration came along, 2 or 3 of those idioms would have stuck and become part of my regular working set. Then, I'd be ready to try adding some more (possibly retrying ones that hadn't stuck before). Eventually, the interval between reading the manual stretched out to a few years, as I'd reached the point where idioms that I could still learn were ones that I didn't use often enough for them to enter into my fingertips.

      Once every decade or so during this process, I'd read a description of some emacs variant but eventually give up - where vi(m) uses n operators and m selectors to get n*m different "things that can be done", emacs uses n*m operators that mostly have to all be learned independently. The first 2 or 3 movement variants for many of the operators use a consistant ctrl-foo, ctrl-X foo, meta-foo; but then there are exceptions to those, and the remaining possible movement variants of the same operation are somewhat arbitrary and perhaps not even present. This dates back to the days when having a whole megabyte of main memory was luxury, and EMACS was understood to mean Eight Megabytes And Constantly Swapping.

      • I'm not so good with getting myself to function in iterative integration, but I'm trying to change that. I really need to. :) Your description of how to learn vim makes me think that this is a good chance to try.

        I have a tendency to try to learn everything at once, and it never really works. The only things where I consistently learn are the things that don't really have much by way of manuals or have tutorials that make you follow step by step. (Speaking of which, it occurs to me now that vim has a t

        --

        ------------------------------
        You are what you think.