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).
My operating system appears to be Gentoo Linux.
The (somewhat verbose) output from "vim --version" is:
=== begin output ===
VIM - Vi IMproved 7.0 (2006 May 7, compiled Apr 29 2007 13:06:51)
Included patches: 1-174
Modified by Gentoo-7.0.174
Compiled by [EMAIL PROTECTED]
Huge version without GUI. Features included (+) or not (-):
+arabic +autocmd -balloon_eval -browse ++builtin_terms +byte_offset +cindent
-clientserver -clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments
+cryptv -cscope +cursorshape +dialog_con +diff +digraphs -dnd -ebcdic
+emacs_tags +eval +ex_extra +extra_search +farsi +file_in_path +find_in_path
+folding -footer +fork() +gettext -hangul_input +iconv +insert_expand +jumplist
+keymap +langmap +libcall +linebreak +lispindent +listcmds +localmap +menu
+mksession +modify_fname +mouse -mouseshape +mouse_dec +mouse_gpm
-mouse_jsbterm +mouse_netterm +mouse_xterm +multi_byte +multi_lang -mzscheme
-netbeans_intg -osfiletype +path_extra +perl +postscript +printer +profile
+python +quickfix +reltime +rightleft -ruby +scrollbind +signs +smartindent
-sniff +statusline -sun_workshop +syntax +tag_binary +tag_old_static
-tag_any_white -tcl +terminfo +termresponse +textobjects +title -toolbar
+user_commands +vertsplit +virtualedit +visual +visualextra +viminfo +vreplace
+wildignore +wildmenu +windows +writebackup -X11 -xfontset -xim -xsmp
-xterm_clipboard -xterm_save
system vimrc file: "/etc/vim/vimrc"
user vimrc file: "$HOME/.vimrc"
user exrc file: "$HOME/.exrc"
fall-back for $VIM: "/usr/share/vim"
Compilation: i586-pc-linux-gnu-gcc -c -I. -Iproto
-DHAVE_CONFIG_H -O2 -mcpu=i586 -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -I/usr/lib/perl5/5.8.8/i586-linux/CORE
-I/usr/include/python2.4 -pthread
Linking: i586-pc-linux-gnu-gcc -rdynamic -L/usr/local/lib
-o vim -lcurses -lgpm -rdynamic -L/usr/local/lib
/usr/lib/perl5/5.8.8/i586-linux/auto/DynaLoader/DynaLoader.a
-L/usr/lib/perl5/5.8.8/i586-linux/CORE -lperl -lutil -lc
-L/usr/lib/python2.4/config -lpython2.4 -lpthread -lutil -lm -Xlinker
-export-dynamic
=== end output ===
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
