> On Sep 1, 2017 11:22, "Taro MURAOKA" <koron@gmail.com> wrote:
> Hi list and Bram.
>
>
>
> When I try to access www.vim.org,
>
> it returns 302 (redirect to) vim.sourceforge.io.
>
>
>
> > $ curl -I http://www.vim.org
>
> &
Hi list and Bram.
When I try to access www.vim.org,
it returns 302 (redirect to) vim.sourceforge.io.
> $ curl -I http://www.vim.org
> HTTP/1.1 302 Found
> Server: nginx
> Date: Fri, 01 Sep 2017 15:16:22 GMT
> Content-Type: text/html; charset=iso-8859-1
> Connection: keep-alive
> Location:
> I'm building vim on Windows 7 with MinGW. After compiling the latest
> pull I get:
>
>
> [...]
> gobjZi686/if_ruby.o:if_ruby.c:(.text+0x862): undefined reference to
> `ruby_sysinit'
> gobjZi686/if_ruby.o:if_ruby.c:(.text+0x23fa): undefined reference to
> `ruby_sysinit'
>
2016/8/27 17:22:49 UTC+9 Urtica dioica:
> I do like the idea for the feature. I tried it, it has some bugs, but they'll
> get ironed out eventually.
I have the same problem.
Procedure to reproduce the problem is like this:
1. With enabling 'incsearch'
2. Enter search mode by hitting `/`
3.
Hi Bram and the list.
I have wrote a patch and make a PR for it.
https://github.com/vim/vim/pull/590
Please check this.
Best.
--
--
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
I wrote:
> We may be able to use "Platform" environment variable for this purpose.
> It get one of values: "x64", "X64", "X86" or "ARM" as cross compiling target,
> in all of VS10, 11, 12, 14 environments.
Hi Mike and Ken.
I have wrote a patch to use PLATFORM for this purpose.
Please try
Mike Williams wrote
> Hi,
>
> Just done my first build of VIM on an old Windows 7 32bit machine
> upgraded to Windows 10 using VC. The link stage was failing due to
> mixed machine targets being used in the make file - 32 and 64 bit! I
> tracked this down to some fun with the
I wrote:
> So we should try/find another way.
We may be able to use "Platform" environment variable for this purpose.
It get one of values: "x64", "X64", "X86" or "ARM" as cross compiling target,
in all of VS10, 11, 12, 14 environments.
You can see these variables at VC\bin\**\vcvars*.bat in
Hi list and Bram.
Continue from reported problem:
https://groups.google.com/d/msg/vim_dev/G9KD895VTxw/ch5R5nqDBQAJ
Problem:
After 7.4.851, on Windows7, when using vim.exe with msys or msys2,
conhost.exe (console window provider on Windows7) will freeze or crash.
It can be reproduced by this
Thank you so much!
--
--
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 subscribed to the Google Groups
This patch breaks Windows build.
Because, there are no "server_parse_messages" symbol defined for Windows.
It is used in misc2.c.
You could see failed log here:
https://ci.appveyor.com/project/koron/vim/build/19#L95
--
--
You received this message from the "vim_dev" maillist.
Do not top-post!
Hi list.
This patch (7.4.851) causes a problem with Windows 7.
It crashes test47 (not fail).
I built vim.exe using VS10 and 11 compiler,
and both of them crash on test47.
We vim-jp disscussing this at https://github.com/vim-jp/issues/issues/764
(sorry, disscussing in Japanese).
And Ken Takata
I want to known the date to switch Vim's main repository to github.
AFAIK https://github.com/vim/vim is just try out.
According to this blog
http://google-opensource.blogspot.jp/2015/03/farewell-to-google-code.html
code.google.com will become readonly mode at August 24, 2015.
It remains less a
Hi Bram and list.
Visual Studio 2015 was released.
It have another version of nmake (14.00.23026.0),
So I need this attached patch to compile vim with it.
Please check it.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are
2015年6月26日金曜日 0時48分10秒 UTC+9 Bram Moolenaar:
It works fine on Linux, what could be different on MS-Windows?
It is caused by `initmappings` in getchar.c
https://github.com/vim-jp/vim/blob/318083ec08ce7b586ba564deccd0a59256e632d9/src/getchar.c#L5308-L5356
It should be unmapped or disabled for
2015年6月26日金曜日 0時48分10秒 UTC+9 Bram Moolenaar:
Ken Takata wrote:
2015/6/25 Thu 20:58:52 UTC+9 Bram Moolenaar wrote:
Patch 7.4.754
Problem:Using CTRL-A in Visual mode does not work well. (Gary Johnson)
Solution: Make it increment all numbers in the Visual area. (Christian
I do have the tags in my local git repository. Do they not get pushed
to the repository with git push ? v7-4-678 would be the last one that
was imported, the patches after that I pushed from my git repository.
Please try --tags option to push. Like this:
$ git push --tags
Regards
--
I have a suggestion.
We should create/obtain an organization which have good simple name like vim
on bitbucket/github, for accesibility and convenience of end-users.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
It is not difficult to migrate/sync the repository from mercurial to git.
We (vim-jp) have been maintaining a mirror on github already.
https://github.com/vim-jp/vim
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
Subject of this mail is wrong.
It would be Patch 7.4.618.
And this patch is not in mercurial repo yet.
https://code.google.com/p/vim/source/list
Are there any relations?
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
This broke small and tiny builds.
Please check https://travis-ci.org/vim-jp/vim-ci/builds/42544356 for details
ex_docmd.c:2132:22: error: use of undeclared identifier 'CMD_USER'
if (ea.cmdidx != CMD_USER ea.cmdidx != CMD_SIZE)
--
--
You received this message from the vim_dev maillist.
It seems very nice!
Thank you Ken.
2014年9月25日木曜日 21時50分47秒 UTC+9 Ken Takata:
Hi Taro,
2013/7/6 Sat 15:43:27 UTC+9 Taro MURAOKA wrote:
Hi list.
When using vim's mercurial repository on Windows,
executing tests has some problems and is very very very stressfull
Related to 7.4.421
https://groups.google.com/d/msg/vim_dev/e95YWigigyQ/DMvHGRiAOo8J
New error code E888 was introduced.
But it appears twice in doc/pattern.txt.
https://code.google.com/p/vim/source/browse/runtime/doc/pattern.txt#832
Related to 7.4.421
https://groups.google.com/d/msg/vim_dev/e95YWigigyQ/DMvHGRiAOo8J
New error code E888 was introduced.
But it appears twice in doc/pattern.txt.
https://code.google.com/p/vim/source/browse/runtime/doc/pattern.txt#832
Hi list and Bram.
I wrote a patch to fix a problem related if_python.
Please check attached.
Problem:
When python 2.7 can't find site module, vim is exit.
For example, on Windows which not installed official python 2.7,
but installed Mecurial or so (py2exe'ed binary),
Vim will try to load
Taro MURAOKA:
Hi.
Is loading the site module done by all versions of Python, or was it
added recently?
I don't think all version.
But as I can check, python 2.0-7 are loading the site module.
2.0 -
http://svn.python.org/view/python/branches/release20-maint/Python
Hi list and Bram.
I found a problem test_listlbr is never executed on Windows.
And I wrote an attached patch to fix it.
Please check it.
Best
--
--
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,
After this patch test 86 and 87 are failed.
It may be forgotten to fix typos in those tests.
I have wrote a patch to fix this.
Please check it
Thanks!
--
--
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
This patch has caused a linking failure under Cygwin:
objects/if_python.o: In function `InsertBufferLines':
/usr/src/vim/src/if_py_both.h:4018: undefined reference to `find_win_for_buf'
/usr/src/vim/src/if_py_both.h:4076: undefined reference to `find_win_for_buf'
objects/if_python3.o: In
After this patch, build was failed like this
Mismatching error/warning code in line 3006
make[2]: *** [nl.ck] Error 1
make[2]: Leaving directory `/home/travis/build/vim-jp/vim-ci/vim/src/po'
make[1]: *** [test] Error 2
Check this for details: https://travis-ci.org/vim-jp/vim-ci/jobs/8886799
Hi list.
When using vim's mercurial repository on Windows,
executing tests has some problems and is very very very stressfull.
* converting 'ff' of *.ok and *.in causes messy status for hg.
* executing single test is failed often,
because of forgetting convert 'ff'.
* debugging and
I'm going to make a beta release today.
Wow! It's so great! I'm very exiting!
--
--
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
I'm going to make a beta release today.
Wow! It's so great! I'm very exciting!
--
--
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
Hi Bram.
On mercurial repositry, the patch number 1 is duplicated.
Please check here
https://code.google.com/p/vim/source/browse/src/version.c?r=0ddba00c204d855c0b3da30cb338d9bdb0ded847#732
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the
Hi list.
test87 is failed because of python 3.3 shows different messages of
exceptions from python 3.2.
I have made workaround for it. Please check an attached patch.
Best.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are
Vim 7.3.1302 fails about test89 on DOS/Windows.
I wrote an attached patch, please check 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
So we probably need to use an #ifdef.
Indeed. I have updated the patch.
--
--
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
I have found and fixed compile failures of 7.3.1237 on MSVC10.
It seems failures of macro expansion, but I don't know the reason.
Please check attached patch.
Best.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
I have found and fix a warning when compile for 64bit environment.
It was happend for *dynamic* Python2 and 64bit environment,
because third parameter of PyString_AsStringAndSize is expected as Py_ssize_t*,
but it is defined as int* by stub macro of dynamic Python.
Please check attached patch.
I could reproduce it on travis-ci at past.
Failed build:
https://travis-ci.org/vim-jp/vim-ci/builds/8117238
Its build and test log:
https://s3.amazonaws.com/archive.travis-ci.org/jobs/8117240/log.txt
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
Hi list.
There are tests failed on DOS/Windows environment.
I have fixed two of them.
Please check attached patches.
test50: Short name seems depending on OS version.
On my Win7, c:/x.x.y has short name c:/XX9B80~1.Y, it will not be matched.
So I made it flexible.
test77: failed when cksum
Hi list.
I have implemented test report feature for DOS/Windows.
test report is implemented for UNIX, so I made DOS/Windows equivalent.
Please check an attached patch.
Best.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are
Hi list.
On Windows which MinGW or Cygwin is installed,
rmdir in Make_dos.mak invokes MinGW/Cygwin's rmdir.exe.
It expected to invoke built-in rmdir of cmd.exe.
We can avoid this by just using rd instead rmdir easily.
Please check attached patch.
Thanks.
--
--
You received this message
Yeah, basic C is missing containers. There are libraries for them, but
there doesn't seem to be one clear winner.
How about define common containers for Vim by C?
And rewriting Vim by using that containers gradually.
Absence of common containers in Vim, have caused duplication of
Hi list.
Vim can't complete commands which starts with 'py3'
when typing ':py3tab' in command line.
I wrote a patch: https://gist.github.com/koron/5685200
Please check it.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are
+1
--
--
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 subscribed to the Google Groups
vim_dev group.
To
I wrote a patch to make NFA state dump more pretty.
Before patch:
(11) NFA_MOPEN(0) (-991) (id=11)
(10) NFA_SPLIT (-1024) (id=10)
( 8) NFA_MOPEN(1) (-990) (id=8)
( 7) NFA_SPLIT (-1024) (id=7)
( 1) CHAR(f) (102) (id=1)
( 2)
Name of regexp debug log files are very general.
NFA Engine: list.log
BT Engine: debug.log
I change those as self describing, like this:
NFA Engine: list.log - nfa_regexp_debug.log
BT Engine: debug.log - bt_regexp_debug.log
Please check attached patch.
I also added two flags to
This makes vim (debug build) slow to startup.
New NFA engine seems to write huge log files in debug build.
And it causes this terrible slow down.
Added files are generated like this:
gvim -u NONE -U NONE --noplugin --startuptime startuptime-7.3.XXX.txt
I'll look into source codes later, but
I got a report that 970 causes crash when do this:
:echo search([^A-z])
# reported at here in Japanese - https://github.com/vim-jp/issues/issues/386
Yasuhiro Matsumoto try to write a patch to fix this,
but it seems that there are some other similar problems.
--
--
You received this
Hi list.
Windows GUI version doesn't support -f starting option.
So I add a note about it to starting.txt.
Please check attached patch.
Thanks.
--
--
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 added license notation for new files which I have wrote.
Of course, those are under VIM LICENSE! ;-)
--
--
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
---
2. Include the fast regexp engine patch that has been floating around
for a long time. With some clever logic to fall back to the old
regexp engine for patterns that might not work with the new one.
I want to look into this patch from view point of multibyte characters.
Where can I
After this patch, build on MSVC with Python3 is failed.
Attached patch fix this, please check it.
Error cause is variable declaration order violation in strict C language.
Best.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are
Hi list.
Golang has very good plugins for vim. See this URL:
https://code.google.com/p/go/source/browse/#hg%2Fmisc%2Fvim
It would be great that if those are included in vim (7.4 maybe), wouldn't it?
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
Hi list.
When 'enc' is utf-8 and 'fencs' includes ucs-2,
and open a file which is not ucs-2 encoding,
then fencs trial is terminated at ucs-2 unexpectedly.
For example:
:set enc=utf-8
:set fencs=ucs-2
:e abc.txt
It is failed when opening attached abc.txt.
I wrote an attached patch to fix
Leong
Please check your DPI of screen on your both machines, and tell me those.
Best.
--
--
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
Thank you! And please give me more time to fix 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
Thank you Ken!
It seems OK for me.
And I merged your patch and updated mine.
Please check 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
What other information you'd require for you to diagnose?
Please verify your installed font files: Consolas and NSimSun.
Check those hashes between OK and NG machine, or some method.
I doubt fonts are cause of this issue.
Best.
--
--
You received this message from the vim_dev maillist.
Do
Hi Leong.
I and k-takata tried to reproduce your report on last week end.
But we cannot reproduce it.
To understand cause of your report, please try the binary which I
have compiled.
http://files.kaoriya.net/var/vim73-kaoriya-dw96e-20130401.zip
This archive include both of 32bit and 64bit
Hi Leong:
I have one questions:
Which a patch did you use? patch-direct_write-r3d.diff?
Thanks.
--
--
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
---
Mike Williams wrote:
There is a bug in gui_mch_set_rendering_options() when setting
param.textAntialiasMode, the test is on dx_taamode instead of dx_flags.
Thank you reporting this!
I have fixed my patch about that. You can get it from here.
I updated the patch which attached. I have changed these:
* Add document which describe enum values.
* Rename mode to renmode.
* Add taamode for text antialising mode.
there needs to be a call to SetTextAntialiasMode() to specify if
grayscale or ClearType anti-aliasing should be done.
I have corrected indentations of ifdef/endif pair,
which might be just mistake.
Please check attached patch.
Thanks.
--
--
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
I have wrote a script to correct indentations with considering
ifdef/endif nests.
https://gist.github.com/koron/5250637
USAGE:
1. open a source file.
2. :source fix-ifdef-indent.vim
3. check and save.
This script will correct indents and show line numbers which were
corrected.
Thanks.
I have updated the patch.
I have got a report from k-takata that previous one breaks cygwin build.
Please check this new version.
--
--
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
Mike, thank you for reporting!
However, the patch does not work with bitmap fonts such as Courier - all
the text just disappears. The code needs to check the font format to
decide whether to use DirectX for font rendering.
Please tell me your 'guifont' setting, about this.
--
--
You
Thanks!
set guifont=Courier:h10:cANSI
This is on Windows 7 x64 Professional.
I can reproduce it, will investigate.
--
--
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
I have updated the patch. What are changed:
* support raster fonts.
* delay to load DirectX dlls until enabled first time.
What are not changed yet:
* make switching option generic.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the
I have a build warning for you
Thank you reporting it!
The definition of p_directx in options.h is wrong.
It was int pointer, must be int correctly.
I'll fix later.
--
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying
Hi Ingo.
How about recycle an existing 'antialias' option for this purpose.
It is an option for MacOSX to control font rendering.
I know this is not good idea, but there is a platform depended option already.
Why can't we recycle it?
# 'antialias' maybe added by me so long ago, and I forgot it
When using 'guifontwide', it causes slow down of drawing wide characters,
because gui_mch_draw_string() draws only one wide character in a call.
I wrote a patch: https://gist.github.com/4608418
It make drawing with grouping characters by its width.
Please check it.
--
--
You received this
2012年7月11日水曜日 1時03分21秒 UTC+9 Bram Moolenaar:
I wrote:
gt; Patch 7.3.598
gt; Problem:Cannot act upon end of completion. (Taro Muraoka)
gt; Solution: Add an autocommand event that is triggered when completion
has
gt; finished. (Idea by Florian Klein)
gt; Files: src/edit.c
Thank you very much John!
I'm impressed by your speedy work!
--
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 list.
We holds translated Vim's documentation in Japanese at here.
http://vim-jp.org/vimdoc-ja/
Please add a link for it to http://www.vim.org/translations.php
Or who are best to ask it?
Thanks.
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply
There is an unbalanced endif at here on the mercurial repos.
http://code.google.com/p/vim/source/browse/runtime/autoload/netrw.vim#327
May it be a problem on the mercurial repos only?
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you
This break vim build, what happens are
1. can't be compiled with Lua 5.1
2. can't be compiled with dyn/dll
I wrote a patch please check it.
https://gist.github.com/2315325
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are
I wrote a patch for that against latest 7.3.401.
https://gist.github.com/1600566
And measure benchmarks with this script (by MATSUMOTO Yasuhiro).
https://gist.github.com/1599910
Then it makes about 90 times faster in my environment!
Original benchmark scores:
0.048741
0.049043
Hi Luis Carvalho.
wouldn't a simpler solution be to just
avoid checking if the value is interned?
I think it will cause some problems.
Checking interned has two important meanings at least.
1st one is efficiency as you wrote.
2nd one is avoiding infinite loop for cyclic refrenced value.
Sorry, previous patch has problems on system which without dynamic lua.
Attached new patch have fixed it. Please check 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
81 matches
Mail list logo
