Sebastian Menge wrote:
[...very helpful summary for Vim Wiki...]
Thanks for keeping this moving. I'm happy with what you said,
but here are some comments. Please disregard all this and just
do it, if you can't stand my detail at the moment!
everything should fit on one page, no scrolling
On 5/22/07, Edward L. Fox [EMAIL PROTECTED] wrote:
On 5/21/07, Swaroop C H [EMAIL PROTECTED] wrote:
When programming, I have to turn the spelling check off. Or it will
show a lot of spelling mistakes in the code. I'd like to apply
spelling check for sentences within the comment blocks
Swaroop C H wrote:
Is there a way to use wget or curl to get scripts off the Vim site?
Use `wget http://www.vim.org/scripts/download_script.php?src_id=$id -O
foo` ?
Best,
Swaroop
Must have been a corrupt file. I removed everything and reinstalled the
scripts and all is well.
Robert
hello all,
Is the enter key on the numeric keypad different than the enter key of
the keyboard?
i was thinking that it would be super handy to map it to gg. I have a
lot of long files to mess around with.
thanks for any tips.
shawn
On Mon, May 21, 2007 10:16 am, Sebastian Menge wrote:
A problem are tips that contain URLs to external sites (e.g. other tips)
This is regarded as spam by mediawiki (captcha). Though the URLs are
clean (since someone edited them before) we have to either import these
tips by hand or convert
Hey all,
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B on them, respectively.
That I can live with, but check this out, if I have the following
sentence:
fREW
On May 22, 2007, at 11:39 AM, fREW wrote:
Hey all,
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B on them, respectively.
That I can live with, but check this
On 5/22/07, Michael Hernandez [EMAIL PROTECTED] wrote:
On May 22, 2007, at 11:39 AM, fREW wrote:
Hey all,
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B on them, respectively.
Sounds like it stopped recognising arrow keys' ANSI sequences (esc[A
and esc[B). Wouldda
On 5/22/07, Gene Kwiecinski [EMAIL PROTECTED] wrote:
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B on them, respectively.
Sounds like it stopped recognising
On 5/22/07, fREW [EMAIL PROTECTED] wrote:
On 5/22/07, Gene Kwiecinski [EMAIL PROTECTED] wrote:
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B on them,
On 2007-05-22, Natesh Kedlaya [EMAIL PROTECTED] wrote:
From: Gary Johnson [EMAIL PROTECTED]
Sent: Monday, May 21, 2007 5:30:52 PM
On 2007-05-21, Natesh Kedlaya [EMAIL PROTECTED] wrote:
Hi,
I am using Vim6.3
My cscope db was built on a source directory structure 'src1' which was
Op dinsdag 22 mei 2007, schreef fREW:
I figured it out and if anyone else has this problem I am sending out
the solution. Basically when I run vi it is running vim.tiny.
vim.tiny sources /etc/vim/vimrc.tiny, not /etc/vim/vimrc, also,
vim.tiny is pretty crippled, in that it doesn't even have
On May 22, 2007, at 11:59 AM, fREW wrote:
I figured it out and if anyone else has this problem I am sending out
the solution. Basically when I run vi it is running vim.tiny.
vim.tiny sources /etc/vim/vimrc.tiny, not /etc/vim/vimrc, also,
vim.tiny is pretty crippled, in that it doesn't even
On Tue, May 22, 2007 at 09:39:29AM -0600, fREW wrote:
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B on them, respectively.
This is what vi does. Movement is
On 5/22/07, Peter Palm [EMAIL PROTECTED] wrote:
Op dinsdag 22 mei 2007, schreef fREW:
I figured it out and if anyone else has this problem I am sending out
the solution. Basically when I run vi it is running vim.tiny.
vim.tiny sources /etc/vim/vimrc.tiny, not /etc/vim/vimrc, also,
vim.tiny
On May 22, 2007, at 12:34 PM, David Nečas (Yeti) wrote:
This has been hopefully explained already (vi runs a binary
that really behaves like vi, whereas vim runs something more
featureful -- this common in Linux distros). Anyway, it's
a bit strange when a vim user describes vi as `crazy' and
On 5/22/07, David Nečas (Yeti) [EMAIL PROTECTED] wrote:
On Tue, May 22, 2007 at 09:39:29AM -0600, fREW wrote:
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B
On Tue, May 22, 2007 at 10:41:18AM -0600, fREW wrote:
Well, nocompatible is recommended, and since this is a vim list, not
just a vi list, I wouldn't think that it would be strange at all for
people to expect vim (not vi) when they want vim.
That's why you have two commands: vi and vim.
Vim
Hi Gary,
I apologize for my earlier email. I should have given the full details.
I would like to provide it now.
I have tried your suggestion of setting the cscopeprg to a script that
contained
/usr/local/bin/cscope $@ | sed s@/dir1/@/dir2/@
But the cscope results still contained the
--- Natesh Kedlaya [EMAIL PROTECTED] wrote:
Hi,
I am using Vim6.3
My cscope db was built on a source directory structure 'src1' which was
mounted on /dir1. If I use this cscope db in my vim, my cscope query would
yeild following results.
On 2007-05-22, Natesh Kedlaya [EMAIL PROTECTED] wrote:
Hi Gary,
I apologize for my earlier email. I should have given the full details.
I would like to provide it now.
I have tried your suggestion of setting the cscopeprg to a script that
contained
/usr/local/bin/cscope $@ | sed
David Nečas (Yeti) wrote:
it's a bit strange when a vim user describes vi as `crazy' and `so
weird'...
It may sound strange to us Vim veterans, but it's what I would expect.
My path to learning Vi/Vim (which took place at the same time as my
learning of GNU/Linux, by the way) was as follows:
On May 22, 2007, at 3:11 PM, Tobia wrote:
The point is: I don't consider my learning path in any way
peculiar, and
if Vim had suddenly reverted to Vi while I was in phases 1 to 3, I
would
have looked at my computer with a blank, baffled expression on my
face.
Tobia
If you find
Quoting Robert Hicks [EMAIL PROTECTED]:
Is there a way to use wget or curl to get scripts off the Vim site?
Sure -- getscript.vim (:GLVS, :GetLatestVimScripts) uses wget if its available,
curl otherwise. Getscript comes with vim 7.1, too. If you set up a file called
GetLatestVimScripts.dat:
First, thanks very much for creating VIM! I have been using it on Linux
systems for years, and now use it via cygwin at home as well. I vastly prefer
VIM to EMACS, especially at home. I learned vi on a VAX/VMS system long ago (a
friend of mine had ported it), when our computer science
Robert M Robinson wrote:
First, thanks very much for creating VIM! I have been using it on Linux
systems for years, and now use it via cygwin at home as well. I vastly
prefer VIM to EMACS, especially at home. I learned vi on a VAX/VMS
system long ago (a friend of mine had ported it), when
That brings me to my question. I have noticed that when
editing large files (millions of lines), deleting a large
number of lines (say, hundreds of thousands to millions) takes
an unbelieveably long time in VIM--at least on my systems.
The issue of editing large files comes up occasionally. A
Thanks, Tim. I'll look at the options you recommended--and those you
didn't, so I may not need to ask next time. :)
Cheers,
Max
On Tue, 22 May 2007, Tim Chase wrote:
The issue of editing large files comes up occasionally. A few settings can
be tweaked to vastly improve performance.
Well, I don't mean to. :set says this:
--
autoindent helplang=en scroll=11 t_Sb=Esc[4%dm
backspace=2 history=50 ttyfast t_Sf=Esc[3%dm
cscopetag hlsearchttymouse=xterm
cscopeverbose ruler viminfo='20,50
Do you have syntax highlighting enabled? That can really slow vim
down.
Well, I don't mean to. :set says this:
It can be toggled via
:syntax on
and
:syntax off
To see what flavor of syntax highlighting you currently have, you
can query the 'syntax' setting:
I just tried deleting 1133093 lines of a 1133093+1133409 line file, after
typing :syntax off. It took about 3 minutes.
Max
On Tue, 22 May 2007, Tim Chase wrote:
Do you have syntax highlighting enabled? That can really slow vim
down.
Well, I don't mean to. :set says this:
It can be
:set syntax? replies syntax=. I don't think it's syntax highlighting.
I've used that with C and Prolog code before; I gave it up because it was
too slow. I'm editing text output from one of my programs; truncating the
output of a day-long run to match a run in progress for testing purposes,
A.J.Mechelynck schrieb:
Robert M Robinson wrote:
First, thanks very much for creating VIM! I have been using it on
Linux systems for years, and now use it via cygwin at home as well. I
vastly prefer VIM to EMACS, especially at home. I learned vi on a
VAX/VMS system long ago (a friend of
Thanks, Andy; the black hole register is a new idea to me. Unfortunately,
:.,$d _ to the black hole register appears to take the same amount of
time as :.,$d itself. set undolevels=-1 speeds it up, but set
undolevels=0 does not; this suggests to me that the problem isn't related
to how
Hi
I just wanted to share this little mapping I've come up with:
:map RightMouse LeftMouseza
It makes right-clicking on a fold toggle it opened/closed.
Using the mouse wheel all the time to scroll around in GVim, I find this
very useful for navigating big files, especially with
On 2007-05-22, Robert Maxwell Robinson [EMAIL PROTECTED] wrote:
:set undolevels=-1 caused my test to run in less than 15 sec, with no
other options fiddled with. Thanks Tim, now I have a work-around!
Now, does having the undo facility available _necessarily_ mean deleting a
large
Hmm, interesting. I've noticed before that the CPU is pegged when I'm
deleting, but I don't think my machine's behavior is due to CPU load; the
machine has two CPUs, I'm typically the only (serious) user, as top has
confirmed is the case now, and I get the same behavior whether I'm running
fREW wrote:
On 5/22/07, fREW [EMAIL PROTECTED] wrote:
On 5/22/07, Gene Kwiecinski [EMAIL PROTECTED] wrote:
I just updated to feisty on a samba server machine and a lot of the
vim defaults went crazy. For example: Pressing the Up or Down keys
in insert mode add new lines with just A or B
On 2007-05-22, Robert Maxwell Robinson [EMAIL PROTECTED] wrote:
Hmm, interesting. I've noticed before that the CPU is pegged when I'm
deleting, but I don't think my machine's behavior is due to CPU load; the
machine has two CPUs, I'm typically the only (serious) user, as top has
I just wanted to share this little mapping I've come up with:
:map RightMouse LeftMouseza
I find using the keyboard more useful, so I use the space bar to
toggle the opening/closing of the folds:
:map space za
So, it becomes 'j/k/c-f/c-b', space (expand), read, space
On 5/22/07, Tobia [EMAIL PROTECTED] wrote:
David Nečas (Yeti) wrote:
it's a bit strange when a vim user describes vi as `crazy' and `so
weird'...
It may sound strange to us Vim veterans, but it's what I would expect.
My path to learning Vi/Vim (which took place at the same time as my
On 5/22/07, Gary Johnson [EMAIL PROTECTED] wrote:
On 2007-05-22, Robert Maxwell Robinson [EMAIL PROTECTED] wrote:
Hmm, interesting. I've noticed before that the CPU is pegged when I'm
deleting, but I don't think my machine's behavior is due to CPU load; the
machine has two CPUs, I'm
fREW [EMAIL PROTECTED] 写于 2007-05-23 08:15:55:
Yeah, the really big problem is that the guy I am working with who I
am helping admin a few servers is at exactly step 1. In fact, it
wasn't until recently that he figured out (I told him) that Ctrl-Z is
not the same as :q!. And like you said,
AFAIK Vim 7 has a different way of handling undo levels.
Have you tried with Vim 6 instead? I had used Vim 6 to edit a text file
(3Gbytes) and do things within seconds.
--
Sincerely, Pan, Shi Zhu. ext: 2606
Robert Maxwell Robinson [EMAIL PROTECTED] 写于 2007-05-23 05:59:20:
:set undolevels=-1
[EMAIL PROTECTED] wrote:
It seems nature to have vim behave like vi, if the Linux distribution
choose to do so. The distribution decides everything and it is non-related
to vim developers themselves.
All you need to do is to: sudo apt-get install vim-gtk, which installs a
Big version of
Hi,
I may become blinded by to often looking for too long
onto my monitor, but...
I am trying to write a simple function, which searches through
the whole buffer to fund a certain pattern and stops searching
when found the first match. I also want the function to
return a matched/not
Hi, everyone:
I am a beginner user of vim and I use it to write my C/C++ code in
Ubuntu. Every time I finished a C code and I want to compile it, I have
to type:
:gcc -o mycfile.out mycfile.c
How can I map this command to a shortcut key like F12?
Thanks a lot.
TJ
I am a beginner user of vim and I use it to write my C/C++ code in
Ubuntu. Every time I finished a C code and I want to compile it, I have
to type:
:gcc -o mycfile.out mycfile.c
How can I map this command to a shortcut key like F12?
See `:help :make` and `:help compiler-select` and `:help :map`
I am trying to write a simple function, which searches through
the whole buffer to fund a certain pattern and stops searching
when found the first match. I also want the function to
return a matched/not matched return code and given the caller
the line/column of the match if found.
Hi TJ,
On Tue, 2007-05-22 at 21:56 -0500, Ting Jiang wrote:
Hi, everyone:
I am a beginner user of vim and I use it to write my C/C++ code in
Ubuntu. Every time I finished a C code and I want to compile it, I have
to type:
:gcc -o mycfile.out mycfile.c
How can I map this command to a
Thank you very much, Swaroop! This is (almost) the answer to my
unrequested feature for spell checking, specially for gettext message
catalogs (po files).
I tried editing the improved po.vim syntax script
(http://www.vim.org/scripts/script.php?script_id=913) and figured out
a 95% good solution,
I was wondering if vim can edit files larger than 2GB? (My
understanding is that it would have to be compiled in 64-bit mode to
allow this.)
Thanks,
Brian
Hello,
python with vim is just prosciuto di parma with melone, idem est the
best combination.
However: I cannot use omniorb (python CORBA stuff), since it is a C++
module as shared library.
Even python main module must be compiled as C++ in order to be able to
load the c++ stuff.
My
54 matches
Mail list logo
