Hi,
I've updated the patch a bit.
Regards,
Ken Takata
2024年1月9日(火) 15:17 Ken Takata :
> Hi Dr. Chip,
>
> Many changes to netrw are added in the Vim repository, but they are not
> included in your Web site.
> I created a patch to apply the latest changes in the Vim reposit
Hi Dr. Chip,
Many changes to netrw are added in the Vim repository, but they are not
included in your Web site.
I created a patch to apply the latest changes in the Vim repository to
netrw v174b.
Could you apply this patch to your code?
Regards,
Ken Takata
--
--
You received this message from
t if the glyph from a
single-width font is used,
the width can be changed.
(KaoriYa Vim's ambiwidth=auto patch doesn't support DirectWrite, but I have
an additional patch to support it.)
If you need a fine tuning, you can also use setcellwidths().
Regards,
Ken Takata
2023年12月18日月曜日 10:
m still using the mercurial mirror on osdn.net.
I use MQ (mercurial queues) to manage my personal patches.
There are some similar tools for Git (guilt, etc.),
but they had some issues (for my usecases) when I tried them.
Regards,
Ken Takata
2023年8月24日木曜日 14:58:12 UTC+9 Ernie Rael:
> Hoping https:
think?
Regards,
Ken Takata
2023年8月6日日曜日 1:11:39 UTC+9 Christian Brabandt:
> Am 2023-08-05 16:30, schrieb Yegappan Lakshmanan:
> > On Sat, Aug 5, 2023 at 5:53 AM Maxim Kim wrote:
> >>
> >> https://groups.google.com/g/vim_announce/c/tWahca9zkt4
> >>
> &g
Hi Dr. Chip,
I've just tried Netrw 174a from your site and confirmed that the changes in
https://github.com/vim/vim/pull/12150 have been included. Thank you.
However, I found that the indentation is not correct.
Could you check the attached patch?
Regards,
Ken Takata
--
--
You received
Hi,
So, you are using the beta version of python 3.12, right?
Then, if_python3.c should be updated to support python 3.12, I think.
Regards,
Ken Takata
2023年6月1日木曜日 2:50:46 UTC+9 N i c o l a s:
> Hi,
>
> From vim.9.0.1594 source, I obtain this error trying to build gvim HUGE
> v
Hi Christian,
I think that the master branch used to be updated by your server.
But it seems that the master branch has not updated.
Any issues in your server?
Regards,
Ken Takata
2023年4月13日木曜日 15:59:25 UTC+9 Christian Brabandt:
>
> On Mi, 12 Apr 2023, igo...@gmail.com wrote:
>
> &
Hi Bram,
I confirmed that you updated the wiki page.
> I don't think we have had a problem with this until now. Did you have
> to remove something before?
Only once, but there was spam a few months ago.
Regards,
Ken Takata
2022年4月13日水曜日 19:01:04 UTC+9 Bram Moolenaa
itory.
What do you think of this setting?
Regards,
Ken Takata
--
--
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
Hi,
Couldn't reproduce.
Does sodium.h exist in C:\msys64\mingw64\include (for 64-bit) and/or
C:\msys64\mingw32\include (for 32-bit)?
2022年3月7日月曜日 6:27:47 UTC+9 niva...@gmail.com:
> Hi Ken,
>
> Just getting same error after match 4519 of vim: sodium.h is not
> regognized.
>
> foo.bar@I-1 MING
Hi,
The current version of Make_cyg_ming.mak only supports setting "yes" to the
"SODIUM" option.
If you install libsodium from pacman, you can use "SODIUM=yes".
I created PR #9896 to fix that.
Specifying -*I./libsodium-win32-1.0.18/include *in the command line is not
correct. It specifies the i
ive: the
> Mercurial
mirror on BitBucket <https://bitbucket.org/vim-mirror/vim>.
Regards,
Ken Takata
2021年6月1日火曜日 3:04:45 UTC+9 Bram Moolenaar:
>
> Ken Takata wrote:
>
> > https://www.vim.org/mercurial.php needs to be updated because BitBucket
> > stopped suppor
also hosted and has
full support.
and here:
> 1. Clone the repository
> ~/code $ hg clone https://bitbucket.org/vim-mirror/vim
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying
Hi Bram,
2021年1月2日土曜日 5:35:14 UTC+9 Bram Moolenaar:
>
> Ken Takata wrote:
>
> > Now we are using GitHub Actions. So, the most of the issues were solved.
> > But we still need to use Travis CI for some environments.
> > As I wrote before, travis-ci.org will shut
Hi and Christian Bram,
2020年11月24日火曜日 18:57:43 UTC+9 Ken Takata:
> Hi,
>
> 2020年11月24日火曜日 18:30:52 UTC+9 Bram Moolenaar:
>
>>
>> Christian wrote:
>>
>> > On Mo, 23 Nov 2020, Yegappan Lakshmanan wrote:
>> >
>> > > The Travis CI bui
t consider is that travis-ci.org will shutdown at the
end of this year.
If we still use Travis CI, we have to migrate to travis-ci.com.
https://docs.travis-ci.com/user/migrate/open-source-repository-migration
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Hi Bram,
2020年6月22日月曜日 3時38分54秒 UTC+9 Bram Moolenaar:
>
>
> Ken Takata wrote:
>
> > 2020年6月21日日曜日 22時53分37秒 UTC+9 Bram Moolenaar:
> > >
> > >
> > > Patch 8.2.1028
> > > Problem:Vim9: no error for declaring buffer, window, etc.
&g
27;: scope = " global"; break;
> + case 'b': scope = " buffer"; break;
> + case 'w': scope = " window"; break;
> + case 't': scope = " tab"; break;
> + case 'v': scope = &q
Hi Bram,
2020/6/9 Tue 1:55:38 UTC+9 Bram Moolenaar wrote:
>
>
> Patch 8.2.0932
> Problem:Missspelling spelllang.
>
Oh, you misspelled the word misspelling.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type
the right thing to do so I defer to
> others for a patch.
>
> - mike
>
"windowsVersion" is used only in the windowsversion() function.
So, I think that the attached patch is better.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not
*** [gvim.exe] Error 1
> Error by compiling gvim.exe
>
> --
> Cesar
>
Attached patch should fix the issue.
Regards,
Ken Takata
--
--
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 i
rm, I see
> t_vb=^[[?5h$<100/>^[[?5l
>
> and there is a faint but discernible visualbell. In a konsole, t_vb
> has the same value as in xterm and the visualbell is much more
> visible.
>
> Best regards,
> Tony.
>
gui_mch_flash() is not implemented for GTK
uch from stackoverflow. Whoops sorry
> :-)
>
I don't think we need to use #if here.
Attached patch should be enough.
Additionally, at least Windows 7's msvcrt.dll doesn't support the "z"
specifier.
Regards,
Ken Takata
--
--
You received this message from the &quo
Hi,
2020/5/9 Sat 20:06:48 UTC+9 Ken Takata wrote:
>
> Hi John,
>
> 2020/5/9 Sat 16:30:42 UTC+9 John Marriott wrote:
>>
>> Hi All,
>>
>> After cleaning my vim source repo and rebuilding with the brand new gcc
>> 10.1 (mingw64), I get these warnings:
&
note: in definition of macro 'STRCPY'
> 1591 | #define STRCPY(d, s) strcpy((char *)(d), (char *)(s))
>| ^~
> In file included from vim.h:1815,
> from userfunc.c:14:
> userfunc.c: In function 'get_user_func_name':
>
Hi Bram,
2020/3/29 Sun 4:45:18 UTC+9 Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > 2020/3/28 Sat 5:09:20 UTC+9 Bram Moolenaar wrote:
> > >
> > > I wrote:
> > >
> > > > Patch 8.2.0463
> > > > Problem:
.h, src/evalfunc.c
>
> Somehow the git commit got the wrong description and tag.
> Don't think that can be fixed afterwards.
>
You cannot modify the commit message, but you can modify the tag by `git
tag -f` and `git push -f`.
Regards,
Ken Takata
--
--
You received this message
testing/#requirements
> but jobs will run in series as the Free plan allows 1 concurrent job per
account.
One possible option is utilizing GitHub Actions. It supports parallel
builds.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Typ
/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/8.1.0/threads-posix/seh
>
>
> Thanks for the hints.
>
> I tried the second entry in INSTALLpc.txt, using MSYS2 with MinGW, but
> the website appears to be down.
>
> It would be nice
quot;$HOME/.vimrc"
> 2nd user vimrc file: "~/.vim/vimrc"
> user exrc file: "$HOME/.exrc"
>defaults file: "$VIMRUNTIME/defaults.vim"
> fall-back for $VIM: "/usr/local/share/vim"
> Compilation: cc -c -I. -Iproto -DH
Hi Bram,
2020/2/8 Sat 7:03:24 UTC+9 Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > `:help :!` says:
> >
> > Vim redraws the screen after the command is finished,
> > because it may have printed any text. This requires a
>
Hi,
2020/2/7 Fri 18:19:53 UTC+9 Ken Takata wrote:
>
> Hi,
>
> `:help :!` says:
>
> Vim redraws the screen after the command is finished,
> because it may have printed any text. This requires a
> hit-enter prompt, so that y
a/src/ex_cmds.c
+++ b/src/ex_cmds.c
@@ -1469,6 +1469,8 @@ do_shell(
wait_return(term_console ? -1 : msg_silent == 0); // see below
# else
wait_return(msg_silent == 0);
+if (swapping_screen() && msg_silent > 0)
+redraw_later_clear();
# endif
no_wait_return =
7;1. red', '2.
> green', '3. blue'])\1\", 'tx')
I tried it locally and it worked fine.
I also find another issue related to this.
* When vim.exe is compiled with VIMDLL, test_feedinput() causes an infinite
loop.
gui.in_use should be checked.
* Call of
x27;mousehide' 'mh'boolean(default on)
Regards,
Ken Takata
--
--
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 receiv
Hi Bram and Charles,
2020/1/11 Sat 3:57:27 UTC+9 Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > There are many regressions in Charles' plugins in the latest runtime
> file
> > update
> > as reported at
> >
> https://github.com/vim/vim/
Hi Bram and Charles,
There are many regressions in Charles' plugins in the latest runtime file
update
as reported at
https://github.com/vim/vim/commit/2963456ff2b740244b3a064785fe681b1998d75e#r36734504
.
Please check the attached patch.
Regards,
Ken Takata
--
--
You received this message
doctags
# Generated by "make shadow". The directory names could be anything but we
# restrict them to shadow (the default) or shadow-*
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text yo
a{" or "i{" don't work well without the starting "{".
Also "%" may not work well.
> The only place where "{" will appear is a block by itself, used to
> declare a variable:
>
> {
>let tmp = 0
>
Make_cyg_ming.mak and Make_mvc.mak.
Please check the attached patch.
Regards,
Ken Takata
--
--
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
---
Yo
Hi Christian,
It seems that the hg mirror repositories are missing two tags: v8.2.0 and
v8.2..
Could you add those tags?
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to
moved, is was not enabled in any build.
+The FEAT_TAG_ANYWHITE code was removed, it was not enabled in any build.
The UNICODE16 code was removed, it was not useful.
Workshop support was removed, nobody was using it.
The Aap build files were removed, they were outdated.
Regards,
Ken Takata
--
--
/vim/vim-win32-installer/pull/116.
Isn't it better to use "www.cs.utah.edu" or some another mirror?
(www.cs.utah.edu is one of the official mirrors.)
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the t
makefiles, I found that some dependencies to
version.h are missing.
So this can happen when MSVC or MinGW is used.
I will prepare a patch when I have a time.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the te
Hi Bram,
2019/12/9 Mon 14:02:11 UTC+9 Ken Takata wrote:
>
> Hi Charles and Bram,
>
> I found some mistakes in the documents of Charles' plugins.
> Could you check and merge the attached patch?
>
You made a mistake in the latest runtime file update.
A single quote was remov
Hi Charles and Bram,
I found some mistakes in the documents of Charles' plugins.
Could you check and merge the attached patch?
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replyi
Hi Bram,
Here is another patch for the latest version8.txt:
--- a/runtime/doc/version8.txt
+++ b/runtime/doc/version8.txt
@@ -40841,7 +40841,7 @@ Files:src/register.c, src/testdir/t
Patch 8.1.2376
Problem:Preprocessor indents are incorrect.
Solution: Fix the indents. (Ken Takata
Hi Bram,
2019/12/5 Thu 21:42:51 UTC+9 Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > 2019/12/5 Thu 6:17:35 UTC+9 Bram Moolenaar wrote:
> > >
> > >
> > > Patch 8.1.2389
> > > Problem:Using old C style comments.
> > &
/xdiff/xemit.h, src/xdiff/xinclude.h, src/xdiff/xmacros.h,
> src/xdiff/xprepare.h, src/xdiff/xtypes.h, src/xdiff/xutils.h
>
Do we need to change the coding style of the files which are imported from
other projects?
Regards,
Ken Takata
--
--
You received this message from the
Hi Bram,
2019/12/3 Tue 12:20:00 UTC+9 Ken Takata wrote:
>
> Hi Bram,
>
> 2019/12/3 Tue 4:42:50 UTC+9 Bram Moolenaar wrote:
>>
>>
>> Ken Takata wrote:
>>
>> > I saw the latest version8.txt.
>> > In the "Vim script improvements"
Hi Bram,
2019/12/3 Tue 4:42:50 UTC+9 Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > I saw the latest version8.txt.
> > In the "Vim script improvements" section, the ".." operator is not
> described
> > explicitly. (It is described as
.2 are:
* Improved 'incsearch'.
* Support modifyOtherKeys.
* Support ConPTY on Windows 10.
Full colors are available in the terminal mode.
* Added /= and %= assignment operators.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not to
Hi,
I found some typos in version8.txt.
Please check the attached patch.
Regards,
Ken Takata
--
--
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
Hi,
2019/11/28 Thu 14:52:43 UTC+9 Ken Takata wrote:
>
> Hi,
>
> 2019/11/28 Thu 7:07:02 UTC+9 Ken Takata wrote:
>>
>> Hi,
>>
>> 2019/11/28 Thu 6:51:22 UTC+9 Christian Brabandt wrote:
>>>
>>>
>>> On Mi, 27 Nov 2019, Bram Moolenaar wrot
Hi,
2019/11/28 Thu 7:07:02 UTC+9 Ken Takata wrote:
>
> Hi,
>
> 2019/11/28 Thu 6:51:22 UTC+9 Christian Brabandt wrote:
>>
>>
>> On Mi, 27 Nov 2019, Bram Moolenaar wrote:
>>
>> > What was the error on FreeBSD? I thought it also suppored Posix.
>
> > Files:.cirrus.yml, README.md
>
> You are too fast ;)
>
This patch is not appeared in mercurial mirrors.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
If you still need to use 8.1.2300, you can disable the behavior by:
let &t_TI = ""
let &t_TE = ""
See `:help modifyOtherKeys` for detail.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type y
Hi,
2019/11/28 Thu 5:59:01 UTC+9 Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > 2019/11/27 Wed 3:34:01 UTC+9 Bram Moolenaar wrote:
> > >
> > >
> > > Patch 8.1.2350
> > > Problem:Other text for CTRL-V in Insert mode with modifyOth
> I think being specific is OK, thus checking for __FreeBSD__ would be OK.
> > Otherwise we would need a configure check of some kind.
> >
>
If we use __FreeBSD__, maybe we also need to add checks for other BSDs.
It seems that "BSD" is defined in sys/param.h, so how a
Hi,
2019/11/28 Thu 5:05:12 UTC+9 Christian Brabandt wrote:
>
>
> On Di, 26 Nov 2019, Bram Moolenaar wrote:
>
> > Patch 8.1.2344
> > Problem:Cygwin: warning for using strptime().
> > Solution: Move defining _XOPEN_SOURCE and __USE_XOPEN to vim.h. (Ken
>
t
when an opening bracket is typed:
:inoremap [ []
Then type CTRL-SHIFT-V CTRL-V in insert mode.
"^[[118;5u]" is inserted instead of "^[[118;5u". ("]" is automatically
added.)
Is this intentional? Isn't it better not to apply mappings to CTRL-SHIFT-V?
Regards,
Ke
l', [['leaf', 1075], ['row', [['leaf', 1074],
> ['leaf', 1073] but got ['row', [['col', [['leaf', 1075], ['leaf
> > ', 1074]]], ['leaf', 1073]]
>
> This is on i386 and powerps as
; InvalidateRect(s_hwnd, NULL, TRUE);
> DeleteObject(prevBrush);
> }
>
I don't remember when SetClassLongPtr() was added. At least, VC 2008 has
it, and VC 6 doesn't have it.
We already dropped support for Windows 9x, so I don't think we need to keep
support old comp
Hi Bram and the list,
I'd like to update Japanese translations.
Could you merge the contents from the attached file into Vim?
The same file is also available at the vim-jp/lang-ja repository:
https://github.com/vim-jp/lang-ja/releases/tag/2019
Regards,
Ken Takata
--
--
You received
>> > FWIW, "command -v ..." is specified in POSIX. "type" is as well, but as
>> > an XSI extension.
>>
>> In tcsh:
>>
>> $ command -v vim
>> command: Command not found.
>>
>> Perfect error message :-).
>>
>
&
Hi,
2019/11/4 Mon 1:47:22 UTC+9 Tony Mechelynck wrote:
>
> On Sun, Nov 3, 2019 at 5:42 PM Ken Takata > wrote:
> >
> > Hi,
> >
> > 2019/11/4 Mon 0:50:37 UTC+9 Tony Mechelynck wrote:
> >>
> >> After recompiling just 8.1.2245 there were
@if test -x $(VIMEXE); then $(VIMEXE) --clean -eX -u doctags.vim; \
+@if type $(VIMEXE) > /dev/null; then $(VIMEXE) -eX -u doctags.vim >
/dev/null; \
else echo "vim executable $(VIMEXE) not found"; fi
# Use "doctags" to generate the tags file. Only works f
ke_cyg_ming.mak, src/Make_mvc.mak
>
This fails to compile with MSVC. Please check the attached patch.
Regards,
Ken Takata
--
--
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, v
issue?
If you want to get more detail information on gdb, try adding the -g option
to CFLAGS by editing Make_cyg_ming.mak.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For m
t; nsis/gvim.nsi, src/INSTALLpc.txt, src/dosinst.c, src/dosinst.h
>
>
It looks that your change is not enough. Please check the attached patch.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
Hi,
I think 'packpath' should be used instead of 'rtp' for searching
colorschemes
in menu.vim. Please check the attached patch.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text
t; Reverting to an earlier version (in my case, 1694), resolves the issue and I
> can access those histories via the respective commands once more.
I confirmed that 8.1.1727 doesn't have the problem.
It seems that 8.1.1728 is the offending commit.
Regards,
Ken Takata
--
--
You received t
t; is TRUE for *{key: val}
+ * "literal" is TRUE for #{key: val}
* Return OK or FAIL. Returns NOTDONE for {expr}.
*/
int
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are r
Hi,
2019/7/16 Tue 16:26:55 UTC+9 Ken Takata wrote:
> Hi,
>
> 2019/7/16 Tue 15:27:48 UTC+9 Christian Brabandt wrote:
> > On Mo, 15 Jul 2019, Bram Moolenaar wrote:
> >
> > >
> > > I wrote:
> > >
> > > > Patch 8.1.1698
> >
d workaround isn't needed
> anymore, so I am confused whether this is still a problem?
>
> https://github.com/vim/vim-win32-installer/pull/139/commits/7212b47f60a58531b80b2edd6c146dc1f4b9bba7
The progress counter is not shown on the AppVeyor's Web interface, but it
remains in the log file downloaded from A
And I don't think that #{} have a
compatibility problem.
Regards,
Ken Takata
--
--
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
---
Y
ON3_OBJ) $(RUBY_OBJ) \
> - $(TCL_OBJ) $(CSCOPE_OBJ) $(TERM_OBJ) $(SOUND_OBJ)
> $(NETBEANS_OBJ) $(CHANNEL_OBJ) \
> - $(XPM_OBJ) $(OUTDIR)\version.obj $(LINKARGS2)
> + $(link) @<<
> +$(LINKARGS1) /subsystem:$(SUBSYSTEM) -out:$(VIM).exe $(OBJ) $(XDIFF_
gt; --- 2325,2331
> ui_may_remove_balloon();
> if (p_bevalterm)
> {
> + ch_log(NULL, "setting balloon timer");
> profile_setlimit(p_bdlay, &bevalexpr_due);
> bevalexpr_due_set = TRUE;
> }
> ***
Are
Hi,
2019/6/26 Wed 7:34:39 UTC+9 Bram Moolenaar wrote:
> Patch 8.1.1595
> Problem:MS-Windows with VIMDLL: colors wrong in console.
> Solution: Do not set the GUI colors when not using the GUI. (Ken Takata,
> closes #4588)
> Files:src/syntax.c
The co
Hi,
The patch 8.1.1574 added E996, however, it has been already used by the
:const patch. We should use a new number.
Regards,
Ken Takata
--
--
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 i
Hi,
2019/6/22 Sat 8:39:26 UTC+9 h_east wrote:
> Hi Bram and developers,
>
> Attach a patch to fix the typo of the document.
> Please confirm it.
One more patch here.
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Typ
gui.in_use &&
+# endif
+ vim_strchr(p_go, GO_TERMINAL) != NULL)
#endif
)
retval = mch_call_shell(cmd, opt);
Regards,
Ken Takata
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you
Hi,
2019/6/7 Fri 15:12:59 UTC+9 Christian Brabandt wrote:
> On Do, 06 Jun 2019, Ken Takata wrote:
>
> > Or, should we also mark gettext v0.19 to v0.19.6 as broken?
>
> I believe, when I tried to git bisect the issue yesterday, the first bad
> commit was around 0.19.3
>
Hi,
2019/6/7 Fri 12:05:15 UTC+9 Ken Takata wrote:
> Hi,
>
> 2019/6/7 Fri 5:51:02 UTC+9 Bram Moolenaar wrote:
> > > I see someone else posted earlier about the same issue.
> > > But those suggestions and also latest git rev do not resolve issue for me.
> >
>
then
- AC_MSG_RESULT([yes])
- MSGFMT_DESKTOP="gvim.desktop vim.desktop"
+ if "$MSGFMT" --version | grep '0.19.7$' >/dev/null; then
+ dnl GNU gettext 0.19.7's --desktop is broken.
+ AC_MSG_RESULT([no])
+ else
+ AC_MSG
ct symbolic links so there must some other method
> to distinguish that I am not aware of.
>
> I'll bounce over to GitHub to report this.
>
> TTFN
>
> Mike
I created a PR for this: https://github.com/vim/vim/pull/4492
Regards,
Ken Takata
--
--
You received th
ine + len, props, l);
+ len += l;
+}
for (i = 0; i < count - 1; ++i)
if (prop_lines[i] != NULL)
Regards,
Ken Takata
--
--
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 info
Hi,
Here are some fixes for comments and indents.
Please check.
Regards,
Ken Takata
--
--
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
---
Yo
Hi Bram,
2019/5/28 Tue 5:22:09 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > I found many typos and mistakes in version8.txt.
> > Please check the attached patch.
>
> I'll include it, thanks!
I found some more missing contributor names. Also found a
Hi,
Recently Vim supported binary numbers, but it was not written in usr_41.txt.
Please check the attached patch.
Regards,
Ken Takata
--
--
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 informat
Hi,
I found many typos and mistakes in version8.txt.
Please check the attached patch.
Regards,
Ken Takata
--
--
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://w
#x27;PFL_HIDDEN': macro redefinition
> C:\projects\vim-win32-installer\vim\src\vim.h(617): note: see previous
> definition of 'PFL_HIDDEN'
This occurs when if_perl is enabled. (We don't enable if_perl in the vim/vim
repository on AppVeyor.)
Regards,
Ken Takata
--
--
Y
Hi,
2019/5/23 Thu 9:36:27 UTC+9 Ken Takata wrote:
> That's too bad.
> Unfortunately, I cannot repoduce this yet.
> Does this simple case work?
>
> gvim --clean
> :echo system('dir')
>
> Does the problem occur only with gvim? not on vim.exe?
Ah! `
Hi,
2019/5/23 Thu 5:29:48 UTC+9 Bram Moolenaar wrote:
> > > 2019/5/16 Thu 15:50:40 UTC+9 Ni Va wrote:
> > > > Le mercredi 15 mai 2019 10:19:04 UTC+2, Ken Takata a écrit :
> > > > > Hi,
> > > > >
> > > > > 2019/5/15 Wed 16:07:17 UT
Hi,
2019/5/16 Thu 15:50:40 UTC+9 Ni Va wrote:
> Le mercredi 15 mai 2019 10:19:04 UTC+2, Ken Takata a écrit :
> > Hi,
> >
> > 2019/5/15 Wed 16:07:17 UTC+9 Ni Va wrote:
> > > Le vendredi 3 mai 2019 00:36:56 UTC+2, Blay263 a écrit :
> > > > On Tuesday, Ap
tem('which
> > > > > '.g:Explorer_RubyLibName),":p"),':..',':',"")
> > > >
> > > > Same problem with Vim.8.1.1239 patch
> > >
> > > Line 645:
> > > let g:startify_custom_header =
&
2,8 @@ color2index(VTermColor *color, int fg, i
if (color->ansi_index != VTERM_ANSI_INDEX_NONE)
{
+ if (t_colors == 256)
+ return color->ansi_index;
// The first 16 colors and default: use the ANSI index.
switch (color->ansi_index)
{
Regard
Hi,
Preprocessor directives in Make_cyg_ming.mak are not indented now.
The following patch indents them:
https://bitbucket.org/k_takata/vim-ktakata-mq/src/330d810f8c533c58a67a010d786cdbc37ea634f8/indent-make_cyg_ming.patch?at=default
Regards,
Ken Takata
--
--
You received this message from
Hi,
Preprocessor directives in Make_mvc.mak are not properly indented now.
The following patch indents them properly:
https://bitbucket.org/k_takata/vim-ktakata-mq/src/685efe556ac637c1df1961e758fbd68b74903ccb/indent-make_mvc.patch?at=default
Regards,
Ken Takata
--
--
You received this
1 - 100 din 1007 matches
Mail list logo
