Hi JD!

-------- Original-Nachricht --------
> Datum: Thu, 26 Nov 2009 00:16:28 -0800 (PST)
> Von: JD <jdhore1@...>
> An: vim_dev <vim_dev@googlegroups.com>
> Betreff: Vim VCS repo

> Hey all,
>
> I was wondering if there was some sort of known/decent VCS repo
> (Preferably hg or git, SVN if the first two aren't doable and...I
> can't use CVS) for Vim that's pretty up-to-date as far as patches and
> such. The only thing i need to qualify this with is that i know about
> the vim_extended repo at repo.or.cz, but it's branch system seems a
> bit odd.
> [...]

If you need only the official patches you can use vim_mainline at repo.or.cz
Just do: git clone git://repo.or.cz/vim_mainline.git


HTH,
Dennis Benzinger

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On Thursday 26 November 2009 02:16:28 am JD wrote:

> I was wondering if there was some sort of known/decent VCS
>  repo (Preferably hg or git, SVN if the first two aren't
>  doable and...I can't use CVS) for Vim that's pretty
>  up-to-date as far as patches and such. The only thing i need
>  to qualify this with is that i know about the vim_extended
>  repo at repo.or.cz, but it's branch system seems a bit odd.
>

odd schmod

+1 markus' git repo

of course i can't claim to be objective -- i am a fan of his
relatiive number patch -- but if i can figure it out and use it,
so can you

sc

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On Wed, 25 Nov 2009 19:52:16 +0100, Bram Moolenaar wrote:

> Solution:   Save and restore the line number and line count when calling
> 	    reg_getline().

Using Borland C++, I get the following warnings:

Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
.\regexp.c:
Warning W8065 .\regexp.c 7270: Call to function 'reg_getline_submatch'
with no prototype in function reg_submatch
Warning W8065 .\regexp.c 7296: Call to function 'reg_getline_submatch'
with no prototype in function reg_submatch
Warning W8065 .\regexp.c 7306: Call to function 'reg_getline_submatch'
with no prototype in function reg_submatch
--
Patrick Texier

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

It seems the 'Sender' header has gone missing from posts that are sent to me. It
used to always be included, with the list address as the sender, and today it
started no longer being included. My email filters now don't work.

Anyone know anything about this? A weird inexplicable Google Groups thing?
Something we could/should follow up? Something our list admins have changed?

One of these days I'll get a bit more active on the list again...just too much
on
this year to keep abreast of it all on the whole, unfortunately.

Ben.





--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

> I applied Václav ¿milauer's 2007 breakindent patch to vim trunk. After a
minimal amount of tweaking I got it to compile (see attached patch), but there
is a weird bug when breakindent and linebreak are both set.

I cannot verify this problem but I stopped patching vim at 7.2-79
because I noticed that a patch failed to be applied when the
breakindent patch was included. Which version do you use? Maybe a
patch introduced some sort of inconsistency?

I personally really wish this patch/feature were included in vim. I
personally haven't had any problems with it since I first applied it
-- shortly after 7.2 was released.

Regards,
Thomas.

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Patrick Texier wrote:

> On Wed, 25 Nov 2009 19:52:16 +0100, Bram Moolenaar wrote:
>
> > Solution:   Save and restore the line number and line count when calling
> > 	    reg_getline().
>
> Using Borland C++, I get the following warnings:
>
> Borland C++ 5.5.1 for Win32 Copyright (c) 1993, 2000 Borland
> .\regexp.c:
> Warning W8065 .\regexp.c 7270: Call to function 'reg_getline_submatch'
> with no prototype in function reg_submatch
> Warning W8065 .\regexp.c 7296: Call to function 'reg_getline_submatch'
> with no prototype in function reg_submatch
> Warning W8065 .\regexp.c 7306: Call to function 'reg_getline_submatch'
> with no prototype in function reg_submatch

Thanks for the report.  I'll make a patch.

--
While it's true that many normal people whould prefer not to _date_ an
engineer, most normal people harbor an intense desire to _mate_ with them,
thus producing engineerlike children who will have high-paying jobs long
before losing their virginity.
				 (Scott Adams - The Dilbert principle)

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Patch 7.2.309 (after 7.2.308)
Problem:    Warning for missing function prototype. (Patrick Texier)
Solution:   Add the prototype.
Files:     src/regexp.c


*** ../vim-7.2.308/src/regexp.c 2009-11-25 19:51:56.000000000 +0100
--- src/regexp.c 2009-11-26 20:39:18.000000000 +0100
***************
*** 7214,7219 ****
--- 7214,7221 ----
   }

   #ifdef FEAT_EVAL
+ static char_u *reg_getline_submatch __ARGS((linenr_T lnum));
+
   /*
    * Call reg_getline() with the line numbers from the submatch.  If a
    * substitute() was used the reg_maxline and other values have been
*** ../vim-7.2.308/src/version.c 2009-11-25 19:51:56.000000000 +0100
--- src/version.c 2009-11-26 20:40:11.000000000 +0100
***************
*** 683,684 ****
--- 683,686 ----
   {   /* Add new patch number below this line */
+ /**/
+     309,
   /**/

--
Female engineers become irresistible at the age of consent and remain that
way until about thirty minutes after their clinical death.  Longer if it's a
warm day.
				 (Scott Adams - The Dilbert principle)

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On Fri, Nov 27, 2009 at 04:06:32AM +1100, Ben Schmidt wrote:

>It seems the 'Sender' header has gone missing from posts that are sent to me.
It
>used to always be included, with the list address as the sender, and today it
>started no longer being included. My email filters now don't work.
>
>Anyone know anything about this? A weird inexplicable Google Groups thing?
>Something we could/should follow up? Something our list admins have changed?

Well, something weird definitely happened, since I seem to have been
magically resubscribed to this list after several years away.

David

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Dominique Pelle wrote:

> Function mzvim_apply(...) defined in src/if_mzsch.c is not used
> anywhere.  I assume it can be removed, or am I missing something?
>
> Attached patch removes it.  Removing it also allows to remove
> function do_apply(...) in if_mzsch.c and struct Apply_Info.

It indeed compiles for me without this function.

--
For society, it's probably a good thing that engineers value function over
appearance.  For example, you wouldn't want engineers to build nuclear power
plants that only _look_ like they would keep all the radiation inside.
				 (Scott Adams - The Dilbert principle)

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Petr Splichal wrote:

> Recently I've noticed that the Vim's "make test" does not return
> appropriate exit code if something goes wrong during the testing.
>
> This makes the usual sequence "make && make test && make install"
> unusable. Including such a test inside a source package makes no
> sense and actually does not prevent any possible failures which
> should be it's main purpose I guess.
>
> The following comment from the Makefile is not true, as the "ALL
> DONE" message appears always, regardless of the actual test result:
> # If everything is alright, the final message will be "ALL DONE".
>
> Moreover, the final result output of the test seems quite brief to
> myself. From the report it's not clear which/how many tests were
> actually run:
>
>     Test results:
>     ALL DONE
>
> I've created a simple patch that fixes all the issues mentioned.
> What do you think about it? Thank you for your time! And special
> thanks to Bram for the Vim itself! It's really a great tool! :-)
>
> psss...
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> FAIL before:
>
>     # make test
>     ...
>     test3 FAILED
>     ALL DONE
>     # echo $?
>     0
>
> FAIL after:
>
>     # make test
>     ...
>     Test results:
>     test1 PASS
>     test2 PASS
>     test3 FAILED
>     test4 PASS
>     test5 PASS
>     test6 PASS
>     ...
>     SOME TESTS FAILED
>     make: *** [nongui] Error 1
>     # echo $?
>     2

Looks good to me.  Objections anyone?

--
Engineers are widely recognized as superior marriage material: intelligent,
dependable, employed, honest, and handy around the house.
				 (Scott Adams - The Dilbert principle)

  /// Bram Moolenaar -- Bram@... -- http://www.Moolenaar.net   \\\
///        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\        download, build and distribute -- http://www.A-A-P.org        ///
  \\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

> Why don't you use the file-line.vim plugin? I mentioned it a month ago in
> exactly the current thread:
>     http://groups.google.com/group/vim_dev/msg/722aefe8494c3a44

when I tried that plugin last time, I must have made some mistake when
installing it, did not work. As you insisted, I tried it again, and:

IT WORKS :), so thanks.

However my wrvim still makes sense as it always knows what to open, for example:

(alias vi=wrvim)
->vi my life



Thanks again, Ingo, Tony, Craig


mobi phil

being mobile, but including technology
http://mobiphil.com

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Hi Dominique,

> Function mzvim_apply(...) defined in src/if_mzsch.c is not used
> anywhere.  I assume it can be removed, or am I missing something?
>
> Attached patch removes it.  Removing it also allows to remove
> function do_apply(...) in if_mzsch.c and struct Apply_Info.

Seems like a left-over obliterated at the last time I reworked the
interface so it should be safe to remove.

--
Sergey Khorev
http://sites.google.com/site/khorser
Can anybody think of a good tagline I can steal?

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Hi,


I am using mingw and ggc version
gcc version 3.4.5 (mingw-vista special r3)

I am using this make version.

C:\vim\src>make --version
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

This program built for i686-pc-mingw32


Following help instructions, I encounter this following error :
C:\vim\src>make -f Make_ming.mak gvim.exe
make: *** No rule to make target `gvim.exe'.  Stop.

Can you help me ?

Thanks
Epanda

NB :
Do I have to mail to ronaharon@... ?

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On Nov 27, 12:15 pm, epanda <callingel...@...> wrote:
> Hi,
>
> I am using mingw and ggc version
> gcc version 3.4.5 (mingw-vista special r3)
>
> I am using this make version.
>
> C:\vim\src>make --version
> GNU Make 3.81
> Copyright (C) 2006  Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.
> There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> PARTICULAR PURPOSE.
>
> This program built for i686-pc-mingw32
>
> Following help instructions, I encounter this following error :
> C:\vim\src>make -f Make_ming.mak gvim.exe
> make: *** No rule to make target `gvim.exe'.  Stop.
>
> Can you help me ?

You need only to do:
make -f Make_ming.mak

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On 27 nov, 23:21, andalou <cesar.rom...@...> wrote:
> On Nov 27, 12:15 pm, epanda <callingel...@...> wrote:
>
>
>
>
>
> > Hi,
>
> > I am using mingw and ggc version
> > gcc version 3.4.5 (mingw-vista special r3)
>
> > I am using this make version.
>
> > C:\vim\src>make --version
> > GNU Make 3.81
> > Copyright (C) 2006  Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions.
> > There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> > PARTICULAR PURPOSE.
>
> > This program built for i686-pc-mingw32
>
> > Following help instructions, I encounter this following error :
> > C:\vim\src>make -f Make_ming.mak gvim.exe
> > make: *** No rule to make target `gvim.exe'.  Stop.
>
> > Can you help me ?
>
> You need only to do:
> make -f Make_ming.mak

Thanks, I have copied all extra vim 72/src into  vim/src directory.
I would like to do 2 things :

1/ enlarge icons from toolbar menu
2/ manage transparency into Gvim window

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On 27 nov, 23:21, andalou <cesar.rom...@...> wrote:
> On Nov 27, 12:15 pm, epanda <callingel...@...> wrote:
>
>
>
>
>
> > Hi,
>
> > I am using mingw and ggc version
> > gcc version 3.4.5 (mingw-vista special r3)
>
> > I am using this make version.
>
> > C:\vim\src>make --version
> > GNU Make 3.81
> > Copyright (C) 2006  Free Software Foundation, Inc.
> > This is free software; see the source for copying conditions.
> > There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
> > PARTICULAR PURPOSE.
>
> > This program built for i686-pc-mingw32
>
> > Following help instructions, I encounter this following error :
> > C:\vim\src>make -f Make_ming.mak gvim.exe
> > make: *** No rule to make target `gvim.exe'.  Stop.
>
> > Can you help me ?
>
> You need only to do:
> make -f Make_ming.mak

Yes but do I have to put all files present into directory vim-7.2-extra
\vim72\src to directory vim

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Hi,

Actually using Gvim on Xp, I would like to have a toolbar with
iconsize 32x32.

I have modified tools.bmp in order to pass size from 558x18 to 992x32.

Do I have only to build with this new tools.bmp ?

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On 27-Nov-2009 Cornelius <cornelius.howl@...> wrote:
> Hi,
>
> I have a patch for  javascript binding to vim, this is my first time sending
> a patch for vim.
> I don't know if this work is acceptable.  i would appreciate if this could
> be accept.  :-)
>
> I will continue on developing this feature.
>
>
> this patch is diffed from:
>
> URL: https://vim.svn.sourceforge.net/svnroot/vim/vim7
> Repository Root: https://vim.svn.sourceforge.net/svnroot/vim
> Repository UUID: 2a77ed30-b011-0410-a7ad-c7884a0aa172
> Revision: 1682
>
>
> --
> Best Regards.
>
> Cornelius ( Yo-An Lin )
> E-mail: cornelius.howl@...


Thank you for your interest in improving Vim!

If you are unsure whether your code is acceptable, you might want to
have a look at develop.txt (:help develop.txt), especially at notes
regarding the coding style (:help coding-style). You will notice that
you have broken some of the rules stated there:
- you use the ANSI style function declarations,
- you do not place opening braces on a new line as is done throughout
   Vim source code,
- you do not declare variables at the beginning of code blocks,
- you do not put space between an 'if' and opening parenthesis,
- in 'if' statements you put the condition and the action in one line,
- you use strchr() instead of vim_strchr().

Comments from myself:
- you seem to be slightly inconsistent about whitespace: in feature.h
   you use spaces while the code around your change uses tabs,
- you left trailing spaces in a few places, while I can only find 2 such
   places in Vim so far,
- you left some commented-out code (js_rand, js_srand), which in my
   experience eventually tends to make maintaining the code harder,
- your code seems to be written with the following settings:
   sw=4 et
   while Vim's code seems to follow the standard:
   ts=8 sw=4 noet
- if FEAT_JS is not defined, you define ex_js to be ex_script_ni.
   Otherwise, there is no such thing as ex_js.

Additionally, in reportError() you use uninitialised error_msg pointer.

I have no idea about JavaScript and therefore feel incompetent to state
anything more useful about your code. Maybe others will be interested.

Keep up the good work!

--
Cheers,
Lech

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On 03/11/09 11:32, Bram Moolenaar wrote:
>
> Tony Mechelynck wrote:
>
>> On 05/10/09 20:18, Bram Moolenaar wrote:
>>>
>>> Florian Rehnisch wrote:
>>>
>>>> Hi Bram, folks.
>>>>
>>>> I wonder if noone noticed yet that ft_sql.txt is missing
>>>> from the overview list in help.txt.  Could be after ft_ada.txt.
>>>
>>> You must be using a slightly old version, the line is there now.
>>
>> Bram, the line is there, and the file is there, but clicking the link in
>> help.txt gives me an error E149, because here's the first line of
>> ft_sql.txt (as found among the current 7.2 runtimes on the rsync server):
>>
>> *sql.txt* For Vim version 7.0g.  Last change: 2009 Oct 08
>>
>> Looks like something happened "not quite right". (The file itself has a
>> mod date of 2009-10-29 here, as shown by "ls -l".)
>
> Right, the version number is wrong.
>

Also the tag at left on the first line, which doesn't jibe with the
filename.

Here, "ls -l" gives a mod date of 2009-10-08 when applied to the file
~/.build/vim/vim72/runtime/doc/ft_sql.txt (synchronized by rsync, which
I think copies the date across, and anyway doesn't overwrite the file if
it's already up-to-date) but not to its copy $VIMRUNTIME/doc/ft_sql.txt
(which bears the date of my latest "make install" or "make -C src
installruntime").


Best regards,
Tony.
--
"I only touch base with reality on an as-needed basis!"
		 -- Royal Floyd Mengot (Klaus)

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Hi Bram,

There was a runtime files update today. I notice that you updated the
version number on the first line of ft_sql.txt but forgot to change
*sql.txt* to *ft_sql.txt* on the same line.

Thumbs-up for all the work you put into Vim (and the many recent patches
;-) ).


Best regards,
Tony.
--
The computing field is always in need of new cliches.
		 -- Alan Perlis

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On 04/11/09 08:40, Gary Johnson wrote:
>
> On 2009-11-04, James Vega wrote:
>> On Tue, Nov 03, 2009 at 11:02:38PM -0800, Gary Johnson wrote:
>>> On 2009-11-04, Parker Jones wrote:
>>>> Recently, I wanted to change the syntax highlighting language, but even
after
>>>> spending 15 minutes reading the documentation I got fed up and gave up.  It
>>>> really shouldn't be that hard.  A menu-driven interface could solve this by
>>>> just letting the user pick out settings from a list and likewise choose
from
>>>> possible values.
>>>
>>> I don't see how a menu-driven interface will help with this.
>>> Writing syntax highlighting rules is more akin to writing a program
>>> than it is to choosing option settings.
>>
>> I think this is referring to changing the filetype for a buffer, not
>> changing the syntax highlighting rules.
>
> OH.  I see now.  Thanks.
>
> If that's the case, then executing
>
>      :set ft=<filetype>
>
> where the set of<filetype>  values can be found from
>
>      :!ls $VIMRUNTIME/syntax
>
> seems pretty simple to me.  Yes, I realize that's not nearly as
> clear and straightforward as selecting the file type from a menu,
> but a user should very rarely need to select the file type manually;
> Vim should almost always be able to determine the file type
> automatically.
>
> If Vim is not able to determine the correct file type automatically,
> the proper solution is to give it better guidance in the user's
> ~/.vim/filetype.vim, not require the user to set the file type
> manually every time he opens such a file.
>
> Regards,
> Gary

I thought the OP _was_ referring to constructing a syntax script, which
is indeed a kind of programming and would IMHO not benefit at all from a
menu-driven interface.

However, if the matter is merely choosing among the existing "known"
filetypes, then there _is_ a menu, however you must first enable it by
using "Syntax => Show filetypes in menu". Then you get a menu for
setting the 'syntax' option. Experiment shows that it also sets the
filetype, e.g., after you've added the filetypes to the Syntax menu,
clicking "Syntax => A => Aap" sets both 'filetype' and 'syntax' to "aap".

In Console Vim, it is possible to use the same menus as in gvim,
provided that your Console Vim is compiled with +menu. They look
slightly different because of the differences between a text interface
and a GUI; and they are at bottom rather than at top. See ":help
console-menus" about how to enable them in your vimrc.

I agree that automatic setting of filetypes is the Vim-like way to go.
Some filetypes are so similar that user guidance (I mean, guidance
_from_ the user _to_ filetype.vim) can help discriminate among them.
This can be done either by means of global options, or of modelines,
depending on the particular circumstances. For details, see:
	 :help filetype.txt
	 :help syntax.txt

Best regards,
Tony.
--
More than any time in history, mankind now faces a crossroads.  One
path leads to despair and utter hopelessness, the other to total
extinction.  Let us pray that we have the wisdom to choose correctly.
		 -- Woody Allen

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On 25-Nov-2009 Petr Splichal <psplicha@...> wrote:
> Hi all!
>
> Recently I've noticed that the Vim's "make test" does not return
> appropriate exit code if something goes wrong during the testing.
>
> This makes the usual sequence "make && make test && make install"
> unusable.

[...]

Actually... the comment in src/Makefile is perfectly valid. The problem
is that you seem to have worked on src/testdir/Makefile as it was in Vim
7.2.000, while in 7.2.015 it was changed so that "ALL DONE" is only
displayed in case of all tests having passed and "make && make test &&
make install" works the way you wanted it to.

There still remains the issue of displaying which tests have been
performed, though, which - I believe - is a matter of personal taste.
I have no opinion here.

To prevent problems with outdated files from occurring in the future you
might want to use one of the repositories tracking Vim source code:
- SVN (described here: http://www.vim.org/subversion.php)
- CVS (described here: http://www.vim.org/cvs.php)
- git (available here: http://repo.or.cz/w/vim_mainline.git)

There is also the vim-extended git repository, which additionally holds
code for a few Vim extensions: http://repo.or.cz/w/vim_extended.git

--
Cheers,
Lech

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On Nov 28, 6:17 am, epanda <callingel...@...> wrote:
> Hi,
>
> Actually using Gvim on Xp, I would like to have a toolbar with
> iconsize 32x32.
>
> I have modified tools.bmp in order to pass size from 558x18 to 992x32.
>
> Do I have only to build with this new tools.bmp ?

Hi,

You'll also need to edit gui.h (around line 164)

#ifdef FEAT_GUI_W16
# define TOOLBAR_BUTTON_HEIGHT 15
# define TOOLBAR_BUTTON_WIDTH 16
#else
# define TOOLBAR_BUTTON_HEIGHT 16
# define TOOLBAR_BUTTON_WIDTH 16
#endif

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

Hello,

file for php omni completation is quite old. I added some new keywords
and functions.

New file and patch are attached.

(I hope this is right mail discussion for script patches)

--
Jan Kastanek

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

On Sun, Nov 29, 2009 at 09:55, cyril romain <cyril.romain@...> wrote:

> Here is a patch for yaml syntax highlighting.

I’ll review it.

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php

> Actually... the comment in src/Makefile is perfectly valid. The problem
> is that you seem to have worked on src/testdir/Makefile as it was in Vim
> 7.2.000, while in 7.2.015 it was changed so that "ALL DONE" is only
> displayed in case of all tests having passed and "make && make test &&
> make install" works the way you wanted it to.

Oh, I've just downloaded the latest tar archive from the web
before. Now I know where are the most fresh bits. It's nice to
find out this has already been fixed.

> There still remains the issue of displaying which tests have been
> performed, though, which - I believe - is a matter of personal taste.
> I have no opinion here.

As the output from the "make test" is really fast and contains a
lot of known & expected errors & warning messages which can be
confusing at the first sight (happened to me) --- I think adding a
nice summary at the end won't hurt and will make it absolutely
clear that everything went all right.

As you said, this is rather matter of style & personal taste and
not that important as the right exit code return. Anyway, if you
decide to include this a little bit more verbose behaviour I'm
attaching a simple patch for that.

> To prevent problems with outdated files from occurring in the future you
> might want to use one of the repositories tracking Vim source code:
> - SVN (described here: http://www.vim.org/subversion.php)
> - CVS (described here: http://www.vim.org/cvs.php)
> - git (available here: http://repo.or.cz/w/vim_mainline.git)

Thanks for the links! ;-)

psss...

--
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php