Re: Trial patch for variable tabstops

On Mon, Dec 8, 2008 at 08:23, Markus Heidelberg [EMAIL PROTECTED] wrote: I just tried it again and it seems I had misunderstood some things. The tabstops have a fixed position. If a word is longer than the space for the current tabstop, then this tabstop will be ignored and the next will be

Re: Build failure for vim_extended with Vim 7.2.065

On Mon, Dec 8, 2008 at 01:10, Markus Heidelberg [EMAIL PROTECTED] wrote: Markus, please put the attached file into the git repo. In which branch, master? Yes. That way, everyone will be able to see the README. I already have plans to split the readme part on the gitweb interface into

Re: Trial patch for variable tabstops

On Mon, Dec 8, 2008 at 11:54, Tony Mechelynck [EMAIL PROTECTED] wrote: I don't personally use variable tabs so maybe I'm off-target; but for some options (such as 'syntax' and 'filetype', not to mention 'compatible') special actions are taken at the exact moment when their their setting is

Re: Objective-c syntax file

Jjgod Jiang a écrit : Hi Xavier, On Mon, Dec 8, 2008 at 5:54 AM, Xavier Glattard [EMAIL PROTECTED] wrote: Attached to this message is an Objective-c syntax file. I started from the default syntax file, but it's now almost fully rewritten. It probably needs some improvements but it looks

Re: Build failure for vim_extended with Vim 7.2.065

Hello Everybody, I fixed this problem with a simple patch. I also had to add something to the Makefile. I decided to separate the Vim source tree patches related to CodeCheck from the direct code_check.c patches. That is why I am attaching two files. Please let me know if this is not a good idea,

Re: Build failure for vim_extended with Vim 7.2.065

Richard Hartmann, 08.12.2008: On Mon, Dec 8, 2008 at 01:10, Markus Heidelberg [EMAIL PROTECTED] wrote: Markus, please put the attached file into the git repo. In which branch, master? Yes. That way, everyone will be able to see the README. I've got it. I will put a README file

Re: Build failure for vim_extended with Vim 7.2.065

Birgi Tamersoy, 08.12.2008: Hello Everybody, I fixed this problem with a simple patch. I also had to add something to the Makefile. I decided to separate the Vim source tree patches related to CodeCheck from the direct code_check.c patches. That is why I am attaching two files. Please let

Re: Trial patch for variable tabstops

Thanks. I see the same thing. I'll look into it presently. What's the status of this patch? Does it still work with current Vim? If yes, Markus, would you be willing to merge this into vim_extended? FYI, I always have the patch compiled into all my versions of Vim (GTK, console, MacVim) and

Re: Build failure for vim_extended with Vim 7.2.065

Birgi Tamersoy, 09.12.2008: Hello Markus, On Tue, Dec 09, 2008 at 01:41:37AM +0100, Markus Heidelberg wrote: Birgi Tamersoy, 08.12.2008: Hello Everybody, I fixed this problem with a simple patch. I also had to add something to the Makefile. I decided to separate the Vim

Re: Build failure for vim_extended with Vim 7.2.065

Markus Heidelberg, 09.12.2008: Currently the code_check.txt help file also has the *intro* and *progress* keywords which overwrite the default goals to intro.txt and the progress filetype. Could this be adjusted? I forgot to mention: after doing this, runtime/doc/tags could also be updated in

Re: Build failure for vim_extended with Vim 7.2.065

Hello Markus, On Tue, Dec 09, 2008 at 03:38:30AM +0100, Markus Heidelberg wrote: Currently the code_check.txt help file also has the *intro* and *progress* keywords which overwrite the default goals to intro.txt and the progress filetype. Could this be adjusted? Yes, I can adjust that. I