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, as

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

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 cre

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. > > > > Than

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 di

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-dev&m=109921292009721&w=1). Picture says what it's about (showbreak is aligned with first non-whitespace): http://beta.arcig.cz/

patch 7.1.001

Patch 7.1.001 Problem:Still can't build with Gnome libraries. Solution: Fix typo in bind_textdomain_codeset. (Mike Kelly) Files: src/gui_gtk.c, src/gui_gtk_x11.c *** ../vim-7.1.000/src/gui_gtk.cThu May 10 20:27:29 2007 --- src/gui_gtk.c Mon May 14 14:40:54 2007 *

Re: Stable Vim version 7.1 has been released

Davic Necas wrote: > 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 requir

Re: breakindent, take 2

Now the patch... sorry. Index: runtime/doc/eval.txt === --- runtime/doc/eval.txt (revision 288) +++ runtime/doc/eval.txt (working copy) @@ -5262,8 +5262,8 @@ keymap Compiled with 'keymap' support. langmap Compiled with 'langmap'

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: I can't change the font in vim7.1!

Hi, a) The problem has nothing to do with KDE b) KDE can't solve the problem with GVIM (which is GTK+ based) c) xlsfonts won't help you here. d) Please fix your fonts.conf file in /etc/fonts e) Please fix your xorg.conf file in /etc/X11 f) GTK+ (GNOME) as well as Qt (KDE) use freetype2 for font re

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

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

Re: what "feature" is required to return to last editing position?

On 5/10/07, Micah Cowan <[EMAIL PROTECTED]> wrote: Bram Moolenaar wrote: > Micah Cowan wrote: >> Vincent BEFFARA wrote: >>> However, it would be nice of vim to always test that it owns the $HOME >>> directory before creating files there. Would it break anything ? >> I think this would be a good i

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

[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 vali

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

problems with vim

Hello, I compiled the vim 7.1 source for unix and installed it in my fedora core 4 pc. When I pressed arrows its printing A,B,C,D's(in insert mode) , backspace is not working and when I pressed delete continuously the gvim is closing down. Someone please help me. The information that vim is show

Re: problems with vim

Nageshwar M wrote: Hello, I compiled the vim 7.1 source for unix and installed it in my fedora core 4 pc. When I pressed arrows its printing A,B,C,D's(in insert mode) , backspace is not working and when I pressed delete continuously the gvim is closing down. Someone please help me. The informat

Re: problems with vim

On 5/15/07, A.J.Mechelynck <[EMAIL PROTECTED]> wrote: Nageshwar M wrote: > Hello, > > I compiled the vim 7.1 source for unix and installed it in my fedora > core 4 pc. When I pressed arrows its printing A,B,C,D's(in insert > mode) , backspace is not working and when I pressed delete > continuousl