Re: Vim 7.1 and aap?

Bram Moolenaar wrote: Richard van der Leeden wrote: Currently using AAP is still downloading and installing verison 7.0 (and all the patches). Will this be updated to load 7.1 instead? It's near the top of my todo list now. I have altered my local copy of main.aap to get 7.1 (and

Re: [PATCH] gvim: Fix compilation against GNOME 2.18

On Thu, 10 May 2007 11:28:25 +0200 Bram Moolenaar [EMAIL PROTECTED] wrote: Daniel Drake wrote: gvim with FEAT_GUI_GNOME fails to compile against GNOME 2.18. See https://bugs.gentoo.org/show_bug.cgi?id=176566 for more info. This patch solves the problem. Thanks. Looks safe to

Re: Project specific settings

On Mon, May 14, 2007 at 10:11:02AM +0200, Sebastian Menge wrote: Am Montag, den 14.05.2007, 10:05 +0200 schrieb Marius Roets: I always uses spaces to indent my code, but a current project requires me to use tabs. How could I make this setting only be in effect for this one project, assuming

Re: Stable Vim version 7.1 has been released

Edward L. Fox wrote: On 5/14/07, David Neèas (Yeti) [EMAIL PROTECTED] wrote: On Sun, May 13, 2007 at 09:28:11PM +0100, [EMAIL PROTECTED] wrote: Umm, I suspect there's still an issue for us pesky OSX users with our case-insensitive filesystems: [long list of successful updates

Re: Stable Vim version 7.1 has been released

On Mon, May 14, 2007 at 02:24:09PM +0200, Bram Moolenaar wrote: This is not a bug, an empty src/auto/config.h is included, because otherwise make depend doesn't work. I would rather say this means an additional problem in the Makefiles. If a rule requires src/auto/config.h, it should create

Re: [PATCH] gvim: Fix compilation against GNOME 2.18

Mike Kelly wrote: Bram Moolenaar [EMAIL PROTECTED] wrote: Daniel Drake wrote: gvim with FEAT_GUI_GNOME fails to compile against GNOME 2.18. See https://bugs.gentoo.org/show_bug.cgi?id=176566 for more info. This patch solves the problem. Thanks. Looks safe to

I can't change the font in vim7.1!

I just upgraded to 7.1, and now when I open up a gvim session, I get this huge monospaced font that I can't change. If I type: :set guifont? it returns 7x14 which is what I set it to, but it isn't what is displayed. If I change the setting to *any* other font that is valid for my system, the

breakindent, take 2

Hello, I submit patch that implements the 'breakindent' feature. It is on vim todo list, since the moment I tried a few years ago (see e.g. http://marc.info/?l=vim-devm=109921292009721w=1). Picture says what it's about (showbreak is aligned with first non-whitespace):

Re: breakindent, take 2

On Mon, May 14, 2007 at 07:30:23PM +0200, Václav Šmilauer wrote: The patch is against current svn (vim7, rev. 288). Any comments are welcome. I know this might not be desired comment, since I didn't even look at the patch but only at the screenshots. I just wanted to say that this feature would

RE: I can't change the font in vim7.1!

Okay. I've found a clue to my problem. I'm on a kde system, and I'm obtaining a list of valid fonts with the xlsfonts command. I don't know much about how the kde gui works, bit it appears that the xlsfonts command and kde are incompatible. Now to figure out how to get a list of kde fonts.

Re: Stable Vim version 7.1 has been released

(dropping [EMAIL PROTECTED] from cc) On Mon, May 14, 2007 at 07:36:30PM +0200, Bram Moolenaar wrote: This indeed works strangely; for instance `make -jN' with N 1 works with freshly unpacked sources, but it breaks completely after `make distclean' -- which one would expect to get the

Re: Stable Vim version 7.1 has been released

David Necas wrote: (dropping [EMAIL PROTECTED] from cc) On Mon, May 14, 2007 at 07:36:30PM +0200, Bram Moolenaar wrote: This indeed works strangely; for instance `make -jN' with N 1 works with freshly unpacked sources, but it breaks completely after `make distclean' -- which one

Re: Stable Vim version 7.1 has been released

On Mon, May 14, 2007 at 11:05:24PM +0200, Bram Moolenaar wrote: Hmm, in my POV a rule like: target: one two three means that one, two and three are build in sequence, not at the same time. This means `one', `two' and `three' have to be built for `target'. More precisely any commands

[Patch] proper detection of ProC files.

Fixes an apparent typo in filetype.vim. Per https://bugs.launchpad.net/ubuntu/+source/vim/+bug/86916. -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ Index: runtime/filetype.vim

Re: I can't change the font in vim7.1!

Larson, David wrote: I just upgraded to 7.1, and now when I open up a gvim session, I get this huge monospaced font that I can't change. If I type: :set guifont? it returns 7x14 which is what I set it to, but it isn't what is displayed. If I change the setting to *any* other font that is valid

Re: Stable Vim version 7.1 has been released

[Bram Moolenar] Hmm, in my POV a rule like: target: one two three means that one, two and three are build in sequence, not at the same time. I suppose adding the -jN argument changes the semantics of the Makefile, and that causes it to break. In fact, so far that I know (and