set noanti has no effect in .gvimrc

[GoogleCodeExporter]

What steps will reproduce the problem?

Add "set noanti" in ~/.gvimrc or in the global Contents/Resources/vim/gvimrc

What is the expected output? What do you see instead?

Upon loading, fonts should not be antialiased, instead they are.

What version of the product are you using? On what operating system?

Snapshot 26
Mac OS X 10.5.2

Please provide any additional information below.

I can successfuly change the font in ~/.gvimrc by adding "set 
gfn=AndaleMono:h12", but not the 
antialiasing.
Please note that typing "set noanti" in the MacVim screen once it has loaded 
_DOES WORK_, it's 
just that it cannot be automated by inserting it in the ~/.gvimrc file, so I 
have to type it manually 
every time I load a file.

Original issue reported on code.google.com by carles.c...@gmail.com on 17 Apr 2008 at 5:50

[GoogleCodeExporter]

These sort of problems are usually caused by a "set nocp" in your .gvimrc.  The 
problem is that setting 'nocompatible' resets certain options.

Let me know if that solves it for you,
Bjorn

Original comment by bjorn.winckler@gmail.com on 17 Apr 2008 at 8:18

[GoogleCodeExporter]

No, unfortunately there's no "set nocp" in my .gvimrc or .vimrc. In fact, 
here's the full contents of those files:

~/.vimrc:
set ignorecase
set number
set ruler
set tabstop=8
syntax enable

~/.gvimrc:
set gfn=AndaleMono:h12
set noanti

It must be something else... I tried other, earlier snapshots and still got the 
same problem. Is this working for 
other people? In case this is of interest, I am running Leopard on Intel, and 
not PowerPC.

Carles

Original comment by carles.c...@gmail.com on 17 Apr 2008 at 10:37

[GoogleCodeExporter]

I suggest you post this on the vim_mac list.  Somebody there might be able to 
figure 
out what's going on.  Not many people read the Issues reported here so it is 
unlikely you'll get an answer unless you use the mailing list.

Original comment by bjorn.winckler@gmail.com on 19 Apr 2008 at 8:08

[GoogleCodeExporter]

For what it's worth, I have the same problem. I do have "set nocompatible" in, 
though. I took a guess and tried 
putting "set noanti" after it, but that doesn't seem to work either.

Original comment by suracil....@gmail.com on 3 May 2008 at 2:35

[GoogleCodeExporter]

I've had a chance to try this myself now and can confirm this as a bug.  I will 
have to see what I can do about it.

Original comment by bjorn.winckler@gmail.com on 3 May 2008 at 3:15

• Changed state: Accepted

[GoogleCodeExporter]

The fix is in the repo and will be included in the next snapshot.  Thanks to 
everybody who reported this bug.

Original comment by bjorn.winckler@gmail.com on 9 May 2008 at 11:41

• Changed state: Started

[GoogleCodeExporter]

Original comment by bjorn.winckler@gmail.com on 11 May 2008 at 3:59

• Changed state: Fixed