Slash Boxes
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.
More | Login | Reply
Loading... please wait.
  • From the fine manual:

    Since the '|' character is used to separate a map command from the next
    command, you will have to do something special to include  a '|' in {rhs}.

    There are three methods:
       use       works when                    example
       <Bar>     '<' is not in 'cpoptions'     :map _l :!ls <Bar> more^M
       \|        'b' is not in 'c

    • How did you find that in the fine manual? "help |" doesn't help, nor does my various attempts at escaping the bar. (Well, I've had trouble escaping bars before, but I equivocate ...)

      • by Damian (784) on 2006.08.12 17:48 (#49327)
        How did you find that in the fine manual?
        I've actually read the entire manual (because I'm writing a book on Vim), so it was more a matter of remembering than finding.

        If I hadn't, then I would have typed:

        :help bar<TAB>
        (where that <TAB> is literally the act of hitting the TAB key). That would have produced:
        bar                cpo-bar            'toolbar'          gui-scrollbars
        :bar               map_bar            +toolbar           -scrollbarwidth
        /bar               expr-barbar        gui-toolbar        'toolbariconsize'
        /\bar              CTRL-W_bar         toolbar-icon
        :\bar              escape-bar         hl-PmenuSbar
        bars               <Bar>              hl-Scrollbar
        :help bar
        at which point it's trivial to find the map_bar entry.
        • A book on vim? Thank god. We've desperately needed a really good one. A friend of mine is kind of a vim god and people keep telling him he needs to write such a book, but it's good to know it's actually going to get written. I'll buy it!

        • This is good news. We need a good book on vim. There's a lot of power that goes way under-exploited because of the lack of readable, well-indexed documentation.