On Tue, 24 Jun 2003, Bram Moolenaar wrote:
> Hugh Sasse wrote:
> > I have tried to correct this with an entry in _vimrc, and tried with
> > one in _gvimrc as I wrote on the vim list:
> > > I have tested this in my _gvimrc using the atocommand from the
> > > manual
> > > autocmd GUIEnter * winpos 6 115
> > >
> > > but this makes no difference, either with a leading colon or
> > > without.
> For me adding a ":winpos" command in the vimrc file works as expected.
> Perhaps there is something after this command that causes the position
> to be changed? Setting another font perhaps?
After a lot of fiddling about with other settings I have found out
what is going on. Owing to confusion over the possible places in
$VIMRUNTIME where things could be, I had 2 _gvimrc files. I found
which files were being invoked, and found that the _gvimrc file in
used did not have the winpos command in it.
I now have correct highlighting, correct matchit behaviour, and the
window placed where I want it.
Many thanks to the people who have helped me out with this,
apologies for taking so much of your time, and thanks for a great
(Once again I have demonstrated that undervalued property of the
internet: it allows you to make a serious mistake in front of many
people you respect, and have it archived!)
I will write a sanity checher for vim so that things like this can
be tested, without having to add to vim's bulk. I'll do it in Ruby
first though, because my fluency in vimscript is clearly inadequate!