Uh oh... I spoke slightly too soon. Although the up/down/delete
functions that I first asked about now behave normally, the
vim -N -u NONE -i NONE
option now results in "999 d<space>" deleting 999 characters,
often well beyond those of the present line. I had been used
to this deleting up to 999 characters, but only up to the end
of the present line. It appears that the "set compatible"
option had been helping me to get the desired 'this line only'
functionality, but the "-N" option above now overrides that.
- David.
To: [email protected]
Subject: Re: repeating up/down/delete commands
Date: Fri, 18 May 2007 23:22:59 -0230 (NDT)
From: [EMAIL PROTECTED] (David Pike)
Hi Gary, and thanks for your response. I just tried your
suggestion of
vim -N -u NONE -i NONE
and it behaved "normally" (i.e., in the way that I want).
<snip>
Again, thanks,
- David.
Date: Fri, 18 May 2007 18:39:54 -0700
From: Gary Johnson <[EMAIL PROTECTED]>
To: [email protected]
Subject: Re: repeating up/down/delete commands
On 2007-05-18, David Pike <[EMAIL PROTECTED]> wrote:
> This will hopefully be an easy question or two...
>
> An upgraded version of vim was installed on our systems
recently,
> and some tricks that I'm used to are no longer functional,
such as:
> "[a large integer, say N] <up>" to quickly get to the top of
the
> file that I am editting, "[N] <down>" to quickly get to the
last
> line of the file (similarly, <PageUp> and <PageDown> could be
used).
> Also, while part way through a file, "[N] dd" or "[N] d
<Enter>"
> was a handy way of deleting all remaining lines in the file.
>
> The new version of vim does not seem to let me do this
anymore.
> Specifically, if the N value that I enter (typically 9999) is
> larger than the number of lines involved, then vim now just
beeps
> to signal that it won't do what I would like to do.
>
> Is there some easy way of getting vim to accept these commands
> once again?
I just tried this with a new installation of vim 7.1 on Linux
and
all of the examples you gave worked for me. This was true
whether I
invoked vim as just "vim" or as "vim -N -u NONE -i NONE". I
suspect
some configuration file in your upgrade has botched this for
you.
Try invoking vim as
vim -N -u NONE -i NONE
as see if it still misbehaves. It might help us to know the
operating system you are using and the complete output from
"vim --version", too.
Regards,
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | Mobile Broadband Division
| Spokane, Washington, USA
