David Turetsky | 1 Mar 01:40 2003

RE: Problems in linux w Windows _vimrc RESOLUTION

>>> David Turetsky bemoans:   

   I am running vim 6.1 (2002 Mar 24) under Windows XP, and vim 6.1.18
   under linux 3.0r1 (Woody)

   I love my vimrc under windows, which starts with Bram's example
   vimrc, add's Jeff Kinzli's potpourri of nice additions, and also
   includes colormenu.vim by Geoff Reedy

   When I pasted the Windows vimrc onto the tail end of the vimrc that
   comes with the woody distribution, I got color highlighting, but vim
   opens up with a long list of complaints to the shell

   I've been commenting out segments, but though even commented out, vim
   complains about the code as though the comment (") wasn't even there

   I've got a bunch of 'Not an editor command: ^M (yes, I know, this is
   a carriage return), and things like 'E15: Invalid expression:
   globpath(&rtp, "colors/*.vim")^M

   The latter occurs even though I first changed the variable in
   globpath to "/usr/vim/colors/*.vim" which I had set up and installed
   all of the colorscheme files I got from the php list

   Even though I've then commented that line out and similarly commented
   out 'bs=2^M' and 'ch=2^M', it keeps complaining

   Any insights?

(Continue reading)

Antoine J. Mechelynck | 1 Mar 01:50 2003

Re: Problems in linux w Windows _vimrc RESOLUTION

David Turetsky <davidturetsky <at> earthlink.net> wrote:
>    The cure is simply :set fileformat=unix. Set ft=unix also clears
>    the problem, but removes the color rendition until that file is
> reopened

ft = filetype
ff = fileformat (can be overridden by :edit ++ff filename)

I don't know what kind of a filetype "unix" is. I believe it was a typo on
the part of whoever recommended setting ft to unix.


Hari Krishna Dara | 1 Mar 03:13 2003

Re: nested autocommand question

On Wed, 26 Feb 2003 at 9:00pm, Bram Moolenaar wrote:

> > > > 3. It should be easier to emulate the regular behavior when defining a
> > > > FileChangedShell sutocommand.
> > >
> > > By allowing autocommands to trigger that should be solved now.
> >
> > Are you going to add a new mechanism to do this? Most often, IMHO,
> > users would like to do something in addition to the default mechanism
> > (of prompting user etc.), so overriding the default mechanism is not
> > what they want. Also, I am guessing that users would like to have the
> > choice of doing it before or after the file is reloaded, so both
> > FileChangedShellPre and FileChangedShell events will be expected.
> This event happens at an unpredictable moment (e.g., when gaining
> focus).  I am very careful and want to discourage people to do something
> here.  Adding more events gives a wrong idea.
> The above solution to trigger autocommands when loading the buffer
> should be sufficient in most situations.

I just want to confirm this. So is the :doautocmd on FileChangedShell
going to be the recommended apprach for this? Will you be documenting

Also, are you going to add some flag to FileChangedShell autocommand
that allows the default mechanism to continue to work even with the
autocommand defined? If not, I am going to keep the code that emulates
(Continue reading)

Michael P. Soulier | 1 Mar 03:21 2003

Re: runaway vim processes

On 27/02/03 Daniel Elstner did speaketh:

> Now that was way more than 10 minutes.  Anyway, I think I got it
> working, the patch is attached.

    God I love open source. 



Michael P. Soulier <msoulier <at> digitaltorque.ca>, GnuPG pub key: 5BC8BE08
"...the word HACK is used as a verb to indicate a massive amount
of nerd-like effort."  -Harley Hahn, A Student's Guide to Unix
HTML Email Considered Harmful: http://expita.com/nomime.html
Steve Hall | 1 Mar 05:24 2003

Re: :WManager

jonah wrote:
 > I seem to remember an email a while back about an enhanced version
 > of WManager that could display directory trees, as opposed to simple
 > file lists, in the left nav, much like windows explorer does.

Opsplorer is a very cool basic implementation that gets little press:

Complete with single-click +/- nodes and indention, I use it daily.

Steve Hall [ digitect <at> mindspring.com ]

Gary Johnson | 1 Mar 12:49 2003

Looking for Alexey Marinichev (Lyosha)

I am looking for the author of ctags.vim,
http://vim.sourceforge.net/scripts/script.php?script_id=12, Alexey
Marinichev, who signs messages with "--Lyosha".  His last message to
this list was dated March 20, 2002.  Mail to the address in that
message, which is the same one used at vim online,
<lyosha <at> lyosha.2y.net>, bounces with "Host not found".

I have made some changes to that script that I would like to send to
the author.



Gary Johnson                 | Agilent Technologies
garyjohn <at> spk.agilent.com     | Spokane, Washington, USA

Alan Schmitt | 1 Mar 17:50 2003

doing several diffs successively


I am merging some code from a project that has forked, and I have
trouble editing several diff files. More precisely, here is what

- I open gvim, diffsplit my first file, everything works fine
- I :e the next file, to diffsplit it, and the whole file is marked as
  changed. I tried doing a :set nodiff before opening it again, to no
  avail. The only solution I have found is quitting and restarting vim.

Is there a more efficient solution for successively diffing several
files ?


Alan Schmitt


The hacker: someone who figured things out and made something cool happen.

Payal Rathod | 1 Mar 17:48 2003

Re: highlight

> :nn - :set hls!

This did the trick. Thanks.
So can I use :set nohls



"Visit GNU/Linux Success Stories"
Guest-Book Section Updated.

Payal Rathod | 1 Mar 13:51 2003

help on help windows

A question on help windows.
When someone tells me to refer to help I do,

:help <topic>

and a help window pops up. I covers almost 4/5 of my screen. Now I want
to read a part of help and switch back to full mode of my orginal window
to try help. I do not want to :q the help cos' I might require it. Just
switch the windows.
One solution is I make 2 windows half the screen and use ctrl-w to
switch between them. But I want to switch to original window with full
screen. Any ways to do this?

Thanks a lot and bye.
With regards,


"Visit GNU/Linux Success Stories"
Guest-Book Section Updated.

Payal Rathod | 1 Mar 13:45 2003

multiple copy

Thanks for the mails. I *think* I got it cleared. Just confirming this.
The comments besides each line indicate what I did.
I have,

$ vim sample.dat

Line 1		# "ayy
Line 2		# "bdd
Line 3		# "cyy
Line 4		# "myy
Line 5
Line 6

So it means that now I have Line 1,2,3,4 in registers a,b,c,m
respectively. Right?

Now I go to Line 5 and do "dd" and similarly on Line 6. Which registers
are now Line 5 and Line 6 copied into by default?

Thanks a lot for all the help.
With warm regards,


"Visit GNU/Linux Success Stories"
Guest-Book Section Updated.

(Continue reading)