Re: [vim/vim] printf("%p") is useless (#1466)

On Sat, Feb 11, 2017 at 7:31 PM, vim-dev ML wrote: > Hi Nikolai, > > Excuse, This has nothing to do with the subject, will not you stop using > `VimL`? > GitHub ceased using VimL. > See the attached image. > -- > Best regards, > Hirohito Higashi (a.k.a. h_east) I

Re: [patch] Fix capitalizations of some menu items...

> I haven't looked at this for a long time. Perhaps we can ignore > differences in case when looking for translations. I would not expect > the same menu to exist with only a difference in case. > That will defenitely be a simpler change. Hi Bram, I think this approach makes sense. In the

Re: [patch] Fix capitalizations of some menu items...

On Friday, February 10, 2017 at 8:02:59 PM UTC-6, Kazunobu Kuriyama wrote: > Oops, I committed a blunder with pasting.  The patch part contains my > 'showbreak' characters. > > > Please see that attached patch.  Sorry about the inconvenience. Thanks for the patch, Kazunobu -- -- You

Re: Patch 8.0.0325

Hirohito Higashi wrote: > 2017-2-11(Sat) 19:37:13 UTC+9 Bram Moolenaar: > > Patch 8.0.0325 > > Problem:Packadd test does not clean up symlink. > > Solution: Delete the link. (Hirohito Higashi) > > Files: src/testdir/test_packadd.vim > > > > > > ***

Patch 8.0.0326

Patch 8.0.0326 (after 8.0.0325) Problem:Packadd test uses wrong directory name. Solution: Use the variable name value. (Hirohito Higashi) Files: src/testdir/test_packadd.vim *** ../vim-8.0.0325/src/testdir/test_packadd.vim2017-02-11 11:34:55.363822971 +0100 ---

Re: [vim/vim] printf("%p") is useless (#1466)

2017-02-11 21:31 GMT+03:00 h_east : > Hi Nikolai, > > Excuse, This has nothing to do with the subject, will not you stop using > `VimL`? > GitHub ceased using VimL. > See the attached image. I have no reasons to, and me starting to use this term has nothing to do with GH:

Re: [vim/vim] printf("%p") is useless (#1466)

Hi Nikolai, Excuse, This has nothing to do with the subject, will not you stop using `VimL`? GitHub ceased using VimL. See the attached image. -- Best regards, Hirohito Higashi (a.k.a. h_east) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below

Re: Patch 8.0.0325

Hi Bram and list, 2017-2-11(Sat) 19:37:13 UTC+9 Bram Moolenaar: > Patch 8.0.0325 > Problem:Packadd test does not clean up symlink. > Solution: Delete the link. (Hirohito Higashi) > Files: src/testdir/test_packadd.vim > > > *** ../vim-8.0.0324/src/testdir/test_packadd.vim

Re: [patch] E11 message via Ex command is not translated

Hi Bram and all, It has nothing to do with this patch, but why `e_zerocount` does not have an error number(E999)? Is this intentional? -- Best regards, Hirohito Higashi (a.k.a. h_east) -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the

Re: Patch 8.0.0314

Hi, On Sat, Feb 11, 2017 at 12:19 PM, Bram Moolenaar wrote: > > Ismail Donmez wrote: > >> On Monday, February 6, 2017 at 10:23:09 PM UTC+1, Bram Moolenaar wrote: >> > Patch 8.0.0314 >> > Problem:getcmdtype(), getcmdpos() and getcmdline() are not tested. >> > Solution:

[patch] E11 message via Ex command is not translated

Hi Bram and list, E11 output by the following procedure are not translated. q::tabn E11: Invalid in command-line window; executes, CTRL-C quits In this procedure, the translated one is output. q:w E11: コマンドラインでは無効です; で実行, CTRL-Cでやめる NOTE for Beginner. Actually, in order to output the

Re: patch to nsis script for updated gettext

Hi Bram! On Sa, 11 Feb 2017, Bram Moolenaar wrote: > > Christian Brabandt wrote: > > > Bram, > > the latest windows compiled libintl-8.dll from > > https://github.com/mlocati/gettext-iconv-windows adds an additional > > dependency on libgcc_s_sjlj-1.dll for the 32bit architecture. I can > >

Re: patch to nsis script for updated gettext

Christian Brabandt wrote: > Bram, > the latest windows compiled libintl-8.dll from > https://github.com/mlocati/gettext-iconv-windows adds an additional > dependency on libgcc_s_sjlj-1.dll for the 32bit architecture. I can > adjust the vim-win32-installer (see >

Re: Patch 8.0.0314

Ismail Donmez wrote: > On Monday, February 6, 2017 at 10:23:09 PM UTC+1, Bram Moolenaar wrote: > > Patch 8.0.0314 > > Problem:getcmdtype(), getcmdpos() and getcmdline() are not tested. > > Solution: Add tests. (Yegappan Lakshmanan) > > Files: src/testdir/test_cmdline.vim > > This

Re: tag priority

Charles Campbell wrote: > Bram Moolenaar wrote: > > Charles Campbell wrote: > > > >> Maybe I was just lucky for years, but it seemed to me that the order of > >> tags files (left to right in the tags option) and order of tags > >> (top-to-bottom in the tags file) was important in resolving

Re: Build 8.0.0324: TEST FAILURE

Elimar Riesebieter wrote: > > From test_cmdline.vim: > Found errors in Test_getcmdtype(): > function RunTheTest[21]..Test_getcmdtype[15]..Check_cmdline line 1: Expected > 'MyCmd a' but got '' > function RunTheTest[21]..Test_getcmdtype[15]..Check_cmdline line 2: Expected > 8 but got 0 >

Re: Misinterpretation of "#" with --remote-silent

Axel Bender wrote: > Will this get fixed? > > The prob is really annoying when you work with {C#|F#} etc... This is tricky, since the interpretation of backslashes depends on 'isfname'. Best would be to find a way to pass the file name literally, do any wildcard expansion first and then send

Patch 8.0.0325

Patch 8.0.0325 Problem:Packadd test does not clean up symlink. Solution: Delete the link. (Hirohito Higashi) Files: src/testdir/test_packadd.vim *** ../vim-8.0.0324/src/testdir/test_packadd.vim2017-02-05 16:07:50.291087646 +0100 --- src/testdir/test_packadd.vim

Re: Patch 8.0.0308

Hirohito Higashi wrote: > 2017-2-6(Mon) 0:08:19 UTC+9 Bram Moolenaar: > > Patch 8.0.0308 > > Problem:When using a symbolic link, the package path will not be > > inserted > > at the right position in 'runtimepath'. (Dugan Chen, Norio > > Takagi) > > Solution: Resolve symbolic

Re: [patch] Fix capitalizations of some menu items...

Zhen-Huan Hu wrote: > > > Not that it really matters but the capitalizations of some menu items > > > are rather inconsistent. Here is a small patch for the capitalization. > > > > Although I like the idea, unfortunately this breaks translations. > > To avoid that, at least the English part of