Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Re: Learn vi/vim in 50 lines and 15 minutes

by Abigail-II (Bishop)
on Mar 04, 2004 at 17:43 UTC ( #333946=note: print w/replies, xml ) Need Help??


in reply to Re: Learn vi/vim in 50 lines and 15 minutes
in thread Learn vi/vim in 50 lines and 15 minutes

There is no escape from beep mode.
Oh, sure there is. At least, on many vi-clones, and, IIRC, even on plain old vi. (But maybe not in vim).

In my vi clone, it's as simple as :set noerrorbells, and that will turn off visual and audio bells.

Abigail

  • Comment on Re: Learn vi/vim in 50 lines and 15 minutes

Replies are listed 'Best First'.
Re: Re: Learn vi/vim in 50 lines and 15 minutes
by flyingmoose (Priest) on Mar 04, 2004 at 18:01 UTC
    psst...you weren't supposed to tell them that. No, seriously, for newbies I think the bells are good instructional aids. I used to want them off, but they seem to be helping. I would only turn them if covertly coding in the bushes (say you are on a sting operation and have to take notes) and you don't want anyone to know where you are hiding.
      I've always find them annoying, and never, ever helpful. It hardly helps you in typing a wrong command, as almost any character is a valid command anyway. It's not that if you mistype a and hit s or z that you've hit a non-command. q is one of the few characters that's unclaimed (at least in standard vi, many clones have assigned a command to it - I've a command in my .rc file to disable it), but since it's unclaimed, it's tempting to :map it to something else.

      beep! usually means "the command you tried to give cannot be performed with the cursor in this situation", like not being able to go to the next line if you're on the last line anyway. But since nothing is happening (if something would happen, vi wouldn't beep), it's bloody obvious already that the command you intended to give isn't working.

      No, seriously, for newbies I think the bells are good instructional aids.
      Oh, get out of your ivory tower. I detest this degenerate attitude that newbies are morons and can't think for themselves. (That's a general pet peeve of mine, and not specific to you, or to vi). I really love that fact that a few hits on the return keys or the (back)space button bring my cursor down, left or right towards to margin. I really don't want vi to beep because I couldn't bother to count whether it was 3 or 4 lines. If I hit 4 times, I'm there, even if it was three lines. (Yes, I know shift-G brings me there, and ^ or 0 brings me to one of the left margins, and $ to the end - return and space, due to their large keys, are sometimes faster). I don't think it'll help newbies that vi beeps.

      Abigail

Re: Re: Learn vi/vim in 50 lines and 15 minutes
by insensate (Hermit) on Mar 06, 2004 at 20:35 UTC
    Or do it in your terminal... I use xterms on Solaris (/usr/openwin/bin/xset -b)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://333946]
help
Chatterbox?
[choroba]: On the other hand, lots of options to receive the requests :-)
[Corion]: ... values to be used. For example, I think for headers, one would want to have various kinds of Content-Encoding headers, but for the get_parameters one would have various kinds of Bobby Tables
[choroba]: What about [metadoc:// Algorithm::Loops]?
[Corion]: choroba: Yeah, but handing off the request to Dancer,Plack, Mojolicious,LWP is easy once I have the data filled into some structure ;))
[choroba]: Algorithm::Loops
[Corion]: choroba: I'm using that to generate the permutations, but I don't know how the user can pass the intended values to my function in a sane way
[Corion]: I have a prototype that permutes the get_parameters, but the values used for the get parameters should be different from the values used for the headers and potentially for parts of the URL
[Corion]: But yes, in general, my approach will be "split the URL into another set of parameters, generate an array of allowed values for each parameter and then NestedLoops() over the set"
[choroba]: hmm... so you need something like bag from Test::Deep, but not for checking, but for generation
[Corion]: This has the dual use of easily requesting sequential URLs and also being suitable for testing

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (9)
As of 2017-01-17 08:16 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Do you watch meteor showers?




    Results (152 votes). Check out past polls.