Patch 7.4.1849

Patch 7.4.1848 Problem:Can't build with Strawberry Perl 5.24. Solution: Define S_SvREFCNT_dec() if needed. (Damien, Ken Takata) Files: src/if_perl.xs *** ../vim-7.4.1847/src/if_perl.xs 2016-04-15 21:16:07.780407822 +0200 --- src/if_perl.xs 2016-05-26 22:01:12.668608119

Re: Strawberry Perl 5.24 doesn't work.

Ken Takata wrote: > 2016/5/26 Thu 5:49:48 UTC+9 Bram Moolenaar wrote: > > Ken Takata wrote: > > > > > 2016/5/25 Wed 13:25:44 UTC+9 Ken Takata wrote: > > > > Hi tux., > > > > > > > > 2016/5/25 Wed 7:27:04 UTC+9 tux. wrote: > > > > > Well ... > > > > > > > > > > > if_perl.obj : error LNK2001:

Re: Strawberry Perl 5.24 doesn't work.

Ken Takata wrote: > Hi Bram, > > 2016/5/26 Thu 5:49:48 UTC+9 Bram Moolenaar wrote: > > Ken Takata wrote: > > > > > 2016/5/25 Wed 13:25:44 UTC+9 Ken Takata wrote: > > > > Hi tux., > > > > > > > > 2016/5/25 Wed 7:27:04 UTC+9 tux. wrote: > > > > > Well ... > > > > > > > > > > > if_perl.obj :

Re: Strawberry Perl 5.24 doesn't work.

Hi Bram, 2016/5/26 Thu 5:49:48 UTC+9 Bram Moolenaar wrote: > Ken Takata wrote: > > > 2016/5/25 Wed 13:25:44 UTC+9 Ken Takata wrote: > > > Hi tux., > > > > > > 2016/5/25 Wed 7:27:04 UTC+9 tux. wrote: > > > > Well ... > > > > > > > > > if_perl.obj : error LNK2001: Nicht aufgelöstes externes

Re: Navigate in Vim messages bug

Hi Bram, Ramel and developers, 2016-5-25(Wed) 23:16:51 UTC+9 h_east: > Hi Ramel, > > 2016-5-25(Wed) 22:02:46 UTC+9 Ramel Eshed: > > Hi All, > > > > Please check this: > > > > vim -u NONE -N > > :for i in range(1, 200) | echoerr 'mes ' . i | endfor > > G " - go to the bottom of the list > > >

Re: Github workflow with Vim repository

Hi Ken, On Thu, May 26, 2016 at 4:53 AM, Ken Takata wrote: > Hi Yegappan, > > 2016/5/26 Thu 13:07:15 UTC+9 yega...@gmail.com wrote: >> Hi all, >> >> I recently started using the github branches to track my changes to Vim. >> I have a question about syncing a feature

Re: Github workflow with Vim repository

Hi Christian, Thanks for sending out the detailed instructions. Using your instructions I am able to update the branches. Thanks, Yegappan On Thu, May 26, 2016 at 2:11 AM, Christian Brabandt wrote: > Hi Yegappan! > > On Mi, 25 Mai 2016, Yegappan Lakshmanan wrote: > >> Hi

Re: [bug] Syntax file for markdown uses semi-absolute path

Thanks for the answer. I'll have to cope with it... -- -- 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 --- You received this message because you are

Re: [bug] Syntax file for markdown uses semi-absolute path

Axel Bender wrote: > Tracing the startup process, reading a MD file ("gvim -V readme.md") I > noticed that two HTML files were sourced: my own one in %VIM\.vim\syntax, > plus the original (unchanged) one in %VIM\syntax (rtp only contains the stems > of these two paths). > This is due to the

Re: Github workflow with Vim repository

Hi Yegappan, 2016/5/26 Thu 13:07:15 UTC+9 yega...@gmail.com wrote: > Hi all, > > I recently started using the github branches to track my changes to Vim. > I have a question about syncing a feature branch to the upstream repository. > > I first created a clone of the Vim repository: > >

Re: [bug] Syntax file for markdown uses semi-absolute path

@Christian well, that's easy: I don't use it ;-) I usually don't amend sth. to existing syntax files, but I rewrite them completely, so "runtime!" probably doesn't work in this case (while "syntax include" would...). -- -- You received this message from the "vim_dev" maillist. Do not

Re: [bug] Syntax file for markdown uses semi-absolute path

Hi Axel! On Do, 26 Mai 2016, Axel Bender wrote: > Tracing the startup process, reading a MD file ("gvim -V readme.md") I > noticed that two HTML files were sourced: my own one in %VIM\.vim\syntax, > plus the original (unchanged) one in %VIM\syntax (rtp only contains the stems > of these two

Re: Github workflow with Vim repository

Hi Yegappan! On Mi, 25 Mai 2016, Yegappan Lakshmanan wrote: > Hi all, > > I recently started using the github branches to track my changes to Vim. > I have a question about syncing a feature branch to the upstream repository. > > I first created a clone of the Vim repository: > >

Re: [bug] Syntax file for markdown uses semi-absolute path

Tracing the startup process, reading a MD file ("gvim -V readme.md") I noticed that two HTML files were sourced: my own one in %VIM\.vim\syntax, plus the original (unchanged) one in %VIM\syntax (rtp only contains the stems of these two paths). This is due to the "runtime!" (mind the exclamation