Re: Patch 7.3.710

[Andy Wokula]

Am 14.11.2012 07:23, schrieb Christian Brabandt:

On Tue, November 13, 2012 22:02, Andy Wokula wrote:

Am 23.10.2012 05:09, schrieb Bram Moolenaar:


Patch 7.3.710 (after 7.3.704)
Problem:Patch 7.3.704 breaks "fn".
Solution:   Add check for ca.cmdchar. (Christian Brabandt)
Files:  src/normal.c


Still doesn't look right (gVim 7.3.712).

When typing  fn  the cursor changes its shape.
Typing  fnl  jumps to begin of buffer.

Also the  r  command is affected:
Bothrn  and  rN  beep.


Hm, I don't see this behaviour with vim 7.3.712 on Unix but only with
the latest Cream version which is 7.3.709 on Windows (don't have a
built machine for Windows)


Ok, my mistake then (using Mercurial).  Sorry for the noise.

--
Andy

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: gn/gN and backwards search

[Ben Fritz]

On Wednesday, November 14, 2012 12:28:16 AM UTC-6, Christian Brabandt wrote:
> On Tue, November 13, 2012 22:08, Andy Wokula wrote:
> 
> > Am 22.10.2012 17:12, schrieb Benjamin Fritz:
> 
> >> The help for gn and gN says that gn searches "forward...like with n"
> 
> >> and that gN "searches backward, like with N". But when you do a
> 
> >> backward search with ? instead of /, n moves the cursor backwards, and
> 
> >> N moves it forwards. gn and gN do not behave accordingly, they
> 
> >> continue to move forward with gn and backwards with gN. I think the
> 
> >> behavior would be more intuitive if it accounted for the search
> 
> >> direction like n and N, but at the very least, a documentation update
> 
> >> is needed.
> 
> 
> 
> I really hope, this is not going to be "fixed". The behaviour of
> 
> n/N depending on the inital search direction is one of my greatest
> 
> annoyances of Vim.
> 
> 

Regardless, the inconsistency is confusing. At least the documentation should 
reflect this difference.

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: printf() vs. unicode (multi-byte encodings)

[Bram Moolenaar]

Christian Brabandt wrote:

> Hi lith!
> 
> On So, 11 Nov 2012, lith wrote:
> 
> > Am Sonntag, 11. November 2012 10:03:49 UTC+1 schrieb ZyX:
> > > > Is this intended? Is there an (easy) way to make printf() respect
> > > > multi-byte encodings?
> > > It is clearly stated in documentation that printf() operates with
> > > bytes.
> > 
> > My question rather was am I missing something since I personally find
> > this behaviour rather useless in the context of a text editor.
> > 
> > A formatted string usually is something that should eventually be
> > displayed in a vim buffer. When I want to get a string padded with
> > whitespace, I'm almost always rather interested in its display width
> > than in its size in bytes -- and I can hardly imagine a use case where
> > it would be otherwise.
> > 
> > I can work around this problem by adjusting the width dependent on the
> > difference between len(s) and strwidth(s) but I personally find this
> > unnecessarily complicated.
> 
> I guess, we could use the 'S' type for printf() to specify length is 
> given in char (see patch).

Thanks.  I think it's good that without the +multi_byte feature 'S'
works just like 's', that's easier for script writers.
I also fixed a signed/unsigned comparison that my compiler complained
about.

-- 
How To Keep A Healthy Level Of Insanity:
18. When leaving the zoo, start running towards the parking lot,
yelling "run for your lives, they're loose!!"

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Patch 7.3.713

[Bram Moolenaar]

Patch 7.3.713
Problem:printf() can only align to bytes, not characters.
Solution:   Add the "S" item. (Christian Brabandt)
Files:  runtime/doc/eval.txt, src/message.c


*** ../vim-7.3.712/runtime/doc/eval.txt 2012-10-21 00:44:59.0 +0200
--- runtime/doc/eval.txt2012-11-14 18:00:40.0 +0100
***
*** 4427,4432 
--- 4451,4457 
  
Often used items are:
  %sstring
+ %6S   string right-aligned in 6 display cells
  %6s   string right-aligned in 6 bytes
  %.9s  string truncated to 9 bytes
  %csingle byte
***
*** 4541,4546 
--- 4566,4575 
s   The text of the String argument is used.  If a
precision is specified, no more bytes than the number
specified are used.
+   S   The text of the String argument is used.  If a
+   precision is specified, no more display cells than the
+   number specified are used.  Without the |+multi_byte|
+   feature works just like 's'.
  
*printf-f* *E807*
f   The Float argument is converted into a string of the 
*** ../vim-7.3.712/src/message.c2012-03-28 16:49:25.0 +0200
--- src/message.c   2012-11-14 17:58:25.0 +0100
***
*** 4290,4295 
--- 4290,4296 
case '%':
case 'c':
case 's':
+   case 'S':
length_modifier = '\0';
str_arg_l = 1;
switch (fmt_spec)
***
*** 4318,4323 
--- 4319,4325 
}
  
case 's':
+   case 'S':
str_arg =
  #ifndef HAVE_STDARG_H
(char *)get_a_arg(arg_idx);
***
*** 4354,4359 
--- 4356,4379 
str_arg_l = (q == NULL) ? precision
  : (size_t)(q - str_arg);
}
+ #ifdef FEAT_MBYTE
+   if (fmt_spec == 'S')
+   {
+   if (min_field_width != 0)
+   min_field_width += STRLEN(str_arg)
+- mb_string2cells((char_u *)str_arg, -1);
+   if (precision)
+   {
+   char_u *p1 = (char_u *)str_arg;
+   size_t i;
+ 
+   for (i = 0; i < precision && *p1; i++)
+   p1 += mb_ptr2len(p1);
+ 
+   str_arg_l = precision = p1 - (char_u *)str_arg;
+   }
+   }
+ #endif
break;
  
default:
*** ../vim-7.3.712/src/version.c2012-10-23 05:35:30.0 +0200
--- src/version.c   2012-11-14 17:54:12.0 +0100
***
*** 727,728 
--- 727,730 
  {   /* Add new patch number below this line */
+ /**/
+ 713,
  /**/

-- 
In many of the more relaxed civilizations on the Outer Eastern Rim of the
Galaxy, "The Hitchhiker's Guide to the Galaxy" has already supplanted the
great "Encyclopedia Galactica" as the standard repository of all knowledge
and wisdom, for though it has many omissions and contains much that is
apocryphal, or at least wildly inaccurate, it scores over the older, more
pedestrian work in two important respects.
First, it is slightly cheaper; and second, it has the words "DON'T PANIC"
inscribed in large friendly letters on its cover.
-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Patch 7.3.714

[Bram Moolenaar]

Patch 7.3.714
Problem:Inconsistency: :set can be used in the sandbox, but :setlocal and
:setglobal cannot. (Michael Henry)
Solution:   Fix the flags for :setlocal and :setglobal. (Christian Brabandt)
Files:  src/ex_cmds.h


*** ../vim-7.3.713/src/ex_cmds.h2012-08-08 17:31:36.0 +0200
--- src/ex_cmds.h   2012-11-14 20:41:28.0 +0100
***
*** 832,840 
  EX(CMD_setfiletype,   "setfiletype",  ex_setfiletype,
TRLBAR|EXTRA|NEEDARG|CMDWIN),
  EX(CMD_setglobal, "setglobal",ex_set,
!   TRLBAR|EXTRA|CMDWIN),
  EX(CMD_setlocal,  "setlocal", ex_set,
!   TRLBAR|EXTRA|CMDWIN),
  EX(CMD_sfind, "sfind",ex_splitview,
BANG|FILE1|RANGE|NOTADR|EDITCMD|ARGOPT|TRLBAR),
  EX(CMD_sfirst,"sfirst",   ex_rewind,
--- 832,840 
  EX(CMD_setfiletype,   "setfiletype",  ex_setfiletype,
TRLBAR|EXTRA|NEEDARG|CMDWIN),
  EX(CMD_setglobal, "setglobal",ex_set,
!   TRLBAR|EXTRA|CMDWIN|SBOXOK),
  EX(CMD_setlocal,  "setlocal", ex_set,
!   TRLBAR|EXTRA|CMDWIN|SBOXOK),
  EX(CMD_sfind, "sfind",ex_splitview,
BANG|FILE1|RANGE|NOTADR|EDITCMD|ARGOPT|TRLBAR),
  EX(CMD_sfirst,"sfirst",   ex_rewind,
*** ../vim-7.3.713/src/version.c2012-11-14 18:10:49.0 +0100
--- src/version.c   2012-11-14 20:43:01.0 +0100
***
*** 727,728 
--- 727,730 
  {   /* Add new patch number below this line */
+ /**/
+ 714,
  /**/

-- 
"So this is it," said Arthur, "we are going to die."
"Yes," said Ford, "except...no!  Wait a minute!"  He suddenly lunged across
the chamber at something behind Arthur's line of vision.  "What's this
switch?" he cried.
"What?   Where?" cried Arthur, twisting around.
"No, I was only fooling," said Ford, "we are going to die after all."
-- Douglas Adams, "The Hitchhiker's Guide to the Galaxy"

 /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net   \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\  an exciting new programming language -- http://www.Zimbu.org///
 \\\help me help AIDS victims -- http://ICCF-Holland.org///

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: some vim syntax fixes for multi-lined commands

[Charles E Campbell Jr]

Alexey Radkov wrote:

Hi Charles.

Thank you!


You're welcome!



2012/11/14 Charles Campbell >

(snipped)


BTW, I prefer direct email contact for patches rather than via the
mailing list.


Ok, sure. But i did not know whom i should address with that.
At the top of the syntax files the Maintainers (usually) include their 
email address.  Mine is there, although one has to manually remove the 
NOSPAM embedded therein.


Regards,
Charles Campbell

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: Please include the Dungeon Crawl syntax file with Vim

[Jason A. Spiro]

On Fri, Nov 9, 2012 at 9:22 AM, Darshan Shaligram  wrote:
> [...] I do not believe this syntax file needs to be
> included with Vim since it is likely to have a *very* small niche of users
> (viz. Crawl level designers) [...]

I suspect that more Crawl players than Crawl level designers view
Crawl level files.

Can Vim automatically send anonymous usage statistics to the Vim team?
 If so, does the Vim team have information on how often Vim users view
files with the extension .des?

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Patch 7.3.715

[Bram Moolenaar]

Patch 7.3.715
Problem:Crash when calling setloclist() in BufUnload autocmd. (Marcin
Szamotulski)
Solution:   Set w_llist to NULL when it was freed.  Also add a test.
(Christian Brabandt)
Files:  src/quickfix.c, src/testdir/test49.ok, src/testdir/test49.vim


*** ../vim-7.3.714/src/quickfix.c   2012-06-29 12:57:03.0 +0200
--- src/quickfix.c  2012-11-14 22:33:20.0 +0100
***
*** 107,113 
  };
  
  static intqf_init_ext __ARGS((qf_info_T *qi, char_u *efile, buf_T *buf, 
typval_T *tv, char_u *errorformat, int newlist, linenr_T lnumfirst, linenr_T 
lnumlast, char_u *qf_title));
! static void   qf_new_list __ARGS((qf_info_T *qi, char_u *qf_title));
  static void   ll_free_all __ARGS((qf_info_T **pqi));
  static intqf_add_entry __ARGS((qf_info_T *qi, qfline_T **prevp, char_u 
*dir, char_u *fname, int bufnum, char_u *mesg, long lnum, int col, int vis_col, 
char_u *pattern, int nr, int type, int valid));
  static qf_info_T *ll_new_list __ARGS((void));
--- 107,113 
  };
  
  static intqf_init_ext __ARGS((qf_info_T *qi, char_u *efile, buf_T *buf, 
typval_T *tv, char_u *errorformat, int newlist, linenr_T lnumfirst, linenr_T 
lnumlast, char_u *qf_title));
! static void   qf_new_list __ARGS((qf_info_T *qi, char_u *qf_title, win_T 
*wp));
  static void   ll_free_all __ARGS((qf_info_T **pqi));
  static intqf_add_entry __ARGS((qf_info_T *qi, qfline_T **prevp, char_u 
*dir, char_u *fname, int bufnum, char_u *mesg, long lnum, int col, int vis_col, 
char_u *pattern, int nr, int type, int valid));
  static qf_info_T *ll_new_list __ARGS((void));
***
*** 266,272 
  
  if (newlist || qi->qf_curlist == qi->qf_listcount)
/* make place for a new list */
!   qf_new_list(qi, qf_title);
  else if (qi->qf_lists[qi->qf_curlist].qf_count > 0)
/* Adding to existing list, find last entry. */
for (qfprev = qi->qf_lists[qi->qf_curlist].qf_start;
--- 266,272 
  
  if (newlist || qi->qf_curlist == qi->qf_listcount)
/* make place for a new list */
!   qf_new_list(qi, qf_title, curwin);
  else if (qi->qf_lists[qi->qf_curlist].qf_count > 0)
/* Adding to existing list, find last entry. */
for (qfprev = qi->qf_lists[qi->qf_curlist].qf_start;
***
*** 885,893 
   * Prepare for adding a new quickfix list.
   */
  static void
! qf_new_list(qi, qf_title)
  qf_info_T *qi;
  char_u*qf_title;
  {
  int   i;
  
--- 885,894 
   * Prepare for adding a new quickfix list.
   */
  static void
! qf_new_list(qi, qf_title, wp)
  qf_info_T *qi;
  char_u*qf_title;
+ win_T *wp;
  {
  int   i;
  
***
*** 897,903 
--- 898,908 
   * way with ":grep'.
   */
  while (qi->qf_listcount > qi->qf_curlist + 1)
+ {
+   if (wp != NULL && wp->w_llist == qi)
+   wp->w_llist = NULL;
qf_free(qi, --qi->qf_listcount);
+ }
  
  /*
   * When the stack is full, remove to oldest entry
***
*** 905,910 
--- 910,917 
   */
  if (qi->qf_listcount == LISTCOUNT)
  {
+   if (wp != NULL && wp->w_llist == qi)
+   wp->w_llist = NULL;
qf_free(qi, 0);
for (i = 1; i < LISTCOUNT; ++i)
qi->qf_lists[i - 1] = qi->qf_lists[i];
***
*** 3181,3187 
 eap->cmdidx != CMD_vimgrepadd && eap->cmdidx != CMD_lvimgrepadd)
|| qi->qf_curlist == qi->qf_listcount)
/* make place for a new list */
!   qf_new_list(qi, *eap->cmdlinep);
  else if (qi->qf_lists[qi->qf_curlist].qf_count > 0)
/* Adding to existing list, find last entry. */
for (prevp = qi->qf_lists[qi->qf_curlist].qf_start;
--- 3188,3194 
 eap->cmdidx != CMD_vimgrepadd && eap->cmdidx != CMD_lvimgrepadd)
|| qi->qf_curlist == qi->qf_listcount)
/* make place for a new list */
!   qf_new_list(qi, *eap->cmdlinep, curwin);
  else if (qi->qf_lists[qi->qf_curlist].qf_count > 0)
/* Adding to existing list, find last entry. */
for (prevp = qi->qf_lists[qi->qf_curlist].qf_start;
***
*** 3747,3753 
  
  if (action == ' ' || qi->qf_curlist == qi->qf_listcount)
/* make place for a new list */
!   qf_new_list(qi, title);
  else if (action == 'a' && qi->qf_lists[qi->qf_curlist].qf_count > 0)
/* Adding to existing list, find last entry. */
for (prevp = qi->qf_lists[qi->qf_curlist].qf_start;
--- 3754,3760 
  
  if (action == ' ' || qi->qf_curlist == qi->qf_listcount)
/* make place for a new list */
!   qf_new_list(qi, title, wp);
  else if (action == 'a' && qi->qf_lists[qi->qf_curlist].qf_count > 0)
/* Adding to existing list, find last entry. */
for (prevp = qi->qf_lists[qi->qf_curlist].qf_start;
**

Re: patch 691: Python, thread

[Jakson Alves de Aquino]

Hello!

I'm replying to my own message again, but this time to inform people
reading this thread how I have solved the problem:

   1) I no longer create a socket server in Vim. I now use the Vim's
  +clientserver feature.

   2) I adapted the C code of vim-remote to be used in the R package
  vimcom.

The vim-remote library is available at
http://www.vim.org/scripts/script.php?script_id=3482

The new files vimremote.c, vimremote.h, vimthings.c and vimthings.h
were added to the src directory of vimcom:
https://github.com/jalvesaq/VimCom/tree/master/src

Thanks to Yukihiro Nakadaira for writing vim-remote!



On Fri, Nov 9, 2012 at 6:25 PM, Jakson Alves de Aquino
 wrote:
> I'm adding more details on the problem...
>
> On Thu, Nov 8, 2012 at 6:21 PM, Jakson Alves de Aquino
>  wrote:
>> I'm the maintainer of Vim-R-plugin which may start a separate Vim
>> instance to run an "Object Browser". This Vim instance has a UDP
>> server running in a new thread. The server is written in Python and it
>> receives messages from R to update the list of objects. This Vim
>> instance isn't used to edit code and thus there is no problem if Vim
>> code is executed from the server thread.
>>
>> Problem: The server stopped working after patch 691. The problem is
>> the line 748 of src/if_python.c. If I delete this line, the server
>> works as before. The server is created by the function VimServer() of
>> https://github.com/jcfaria/Vim-R-plugin/blob/master/r-plugin/vimcom.py
>
> The line 748 of src/if_python.c is:
>
> pygilstate = PyGILState_Ensure();
>
> The function VimServer() is called by RunServer() which uses the
> threading module to create a new thread running VimServer(). The
> VimServer() becomes immediately unresponsive. For example, there one
> message that the VimServer() function sends to R when the server is
> successfully started, but this message is actually being sent only
> when the server is joined to the main thread or when the thread is
> killed.
>
> It seems that currently it's not possible to run a thread in parallel
> to the main Vim process.
>
>> I'm far from an expert in Python programming, and I don't know how to
>> solve the problem. Any help is appreciated.
>
> The solutions that I think that may be possible are:
>
> 1) Undo the effect of PyGILState_Ensure() in the vimcom.py code
>(I don't know if this is possible).
>
> 2) Create a Vim option to call/not call PyGILState_Ensure(). That
>is, transfer to plugin developers the option to use or not use
>unsafe threads.
>
> In the Vim-R-plugin, the server is only used when Vim is running
> inside a Tmux session and we have two independent Vim instances. I use
> the server in the editor instance of Vim only to change the value of a
> variable storing the number of the port of the Object Browser server.
> In the Object Browser instance of Vim, the server calls functions to
> rewrite the content of the buffer but that is almost always done when
> the user is editing code in the editor instance and, thus, it's almost
> always idle and almost never crashes. And when it does crash, no data
> is lost since the Object Browser is not used to edit code.
>
> Thanks

-- 
Jakson Alves de Aquino
Federal University of Ceará
Social Sciences Department
www.lepem.ufc.br/aquino.php

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: codebase documentation of vim?

[Nazri Ramliy]

On Wed, Nov 14, 2012 at 5:30 PM, Mostafa Shahverdy wrote:

> How can I find a good overall structural documentation of vim codebase?
>

A good place to start is the data structures. Read src/structs.h.

nazri

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: codebase documentation of vim?

[Marc Weber]

There is src/README.txt

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: codebase documentation of vim?

[Mostafa Shahverdy]

Thanks, I think I have found files that I need to modify ;)


On Thu, Nov 15, 2012 at 7:46 AM, Marc Weber  wrote:

> There is src/README.txt
>
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>



-- 
Regards,
Mostafa Shahverdy 

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: codebase documentation of vim?

[Marc Weber]

Consider contributing - talking about what you're doing now or when
you're done.
Your work might be of interest to more people.

Marc Weber

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Re: codebase documentation of vim?

[Mostafa Shahverdy]

Sure, I am trying to implement BiDi support as an internal feature for vim.
I am at very first levels of understanding structures ;)


On Thu, Nov 15, 2012 at 10:35 AM, Marc Weber  wrote:

> Consider contributing - talking about what you're doing now or when
> you're done.
> Your work might be of interest to more people.
>
> Marc Weber
>
> --
> You received this message from the "vim_dev" maillist.
> Do not top-post! Type your reply below the text you are replying to.
> For more information, visit http://www.vim.org/maillist.php
>



-- 
Regards,
Mostafa Shahverdy 

-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Can't compile latest Vim using Make_cyg.mak

[Christian J. Robinson]

gcc-3 -O3 -fomit-frame-pointer -freg-struct-return -fno-strength-reduce -DWIN32 -DHAVE_PATHDEF -DFEAT_BIG  
-DWINVER=0x0500 -D_WIN32_WINNT=0x0500 -DFEAT_PERL -DDYNAMIC_PERL -DDYNAMIC_PERL_DLL=\"perl512.dll\" 
-DFEAT_PYTHON -DDYNAMIC_PYTHON -DDYNAMIC_PYTHON_DLL=\"python27.dll\" -DFEAT_RUBY -DDYNAMIC_RUBY 
-DDYNAMIC_RUBY_DLL=\"msvcrt-ruby191.dll\" -DDYNAMIC_RUBY_VER=191 -DDYNAMIC_GETTEXT -DDYNAMIC_ICONV 
-DFEAT_MBYTE -DFEAT_MBYTE_IME -DDYNAMIC_IME -DMSWINPS -DFEAT_CSCOPE -DFEAT_NETBEANS_INTG -DFEAT_XPM_W32 
-DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_OLE -march=i386 -Iproto -I/cygdrive/c/strawberry/perl/lib/CORE 
-I/cygdrive/c/Ruby192/include/ruby-1.9.1 -I/cygdrive/c/Ruby192/include/ruby-1.9.1/i386-mingw32 -s -mno-cygwin 
-Ixpm/include -o gvim.exe gobj/blowfish.o  gobj/buffer.o  gobj/charset.o  gobj/diff.o  gobj/digraph.o  
gobj/edit.o  gobj/eval.o  gobj/ex_cmds.o  gobj/ex_cmds2.o  gobj/ex_docmd.o  gobj/ex_eval.o  gobj/ex_getln.o  
gobj/fileio.o  gobj/fold.o  gobj/getchar.o  gobj/hardcopy.o  gobj/hashtab.o  gobj/main.o  gobj/mark.o  
gobj/memfile.o  gobj/memline.o  gobj/menu.o  gobj/message.o  gobj/misc1.o  gobj/misc2.o  gobj/move.o  
gobj/mbyte.o  gobj/normal.o  gobj/ops.o  gobj/option.o  gobj/os_win32.o  gobj/os_mswin.o  gobj/pathdef.o  
gobj/popupmnu.o  gobj/quickfix.o  gobj/regexp.o  gobj/screen.o  gobj/search.o  gobj/sha256.o  gobj/spell.o  
gobj/syntax.o  gobj/tag.o  gobj/term.o  gobj/ui.o  gobj/undo.o  gobj/version.o  gobj/vimrc.o  gobj/window.o  
gobj/if_perl.o gobj/if_python.o gobj/if_ruby.o gobj/if_cscope.o gobj/netbeans.o gobj/xpm_w32.o gobj/gui.o 
gobj/gui_w32.o gobj/gui_beval.o gobj/os_w32exe.o gobj/if_ole.o -L/lib/w32api -L/usr/lib/mingw 
-L/usr/lib/w32api -I/usr/include/mingw -I/usr/include/w32api -luuid -lole32 -lwsock32 -Lxpm/lib -Lxpm/x86/lib 
-lXpm -L/lib/w32api -mwindows -lcomctl32 -lversion -loleaut32 -lstdc++
gobj/eval.o:eval.c:(.text+0x70b7): undefined reference to `_pow'
collect2: ld returned 1 exit status
Make_cyg.mak:534: recipe for target `gvim.exe' failed
make: *** [gvim.exe] Error 1

--
Having a non-smoking section in a restaurant
   is like having a non-peeing section in a pool.
Christian J. Robinson   http://christianrobinson.name/

--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php