Hi Ken!
On Mi, 03 Feb 2016, Ken Takata wrote:
> Hi Christian,
>
> 2016/2/3 Wed 18:25:06 UTC+9 Christian Brabandt wrote:
> > Am 2016-01-30 17:32, schrieb Bram Moolenaar:
> > > I'm awaiting feedback. If it looks OK I'll add a link on the download
> > > page.
> >
> > Here is some: it looks like t
Hi Christian,
2016/2/3 Wed 18:25:06 UTC+9 Christian Brabandt wrote:
> Am 2016-01-30 17:32, schrieb Bram Moolenaar:
> > I'm awaiting feedback. If it looks OK I'll add a link on the download
> > page.
>
> Here is some: it looks like that the compiled binaries are missing some
> kind of signature,
Am 2016-01-30 17:32, schrieb Bram Moolenaar:
I'm awaiting feedback. If it looks OK I'll add a link on the download
page.
Here is some: it looks like that the compiled binaries are missing some
kind of signature,
at least Windows 7 and 10 warn me before executing the binary (see
attached scre
Hi Bram,
2016/1/31 Sun 1:32:20 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > Hi Christian,
> >
> > 2016/1/28 Thu 18:10:37 UTC+9 Christian Brabandt wrote:
> > > Hi Ken!
> > >
> > > On Do, 28 Jan 2016, Ken Takata wrote:
> > >
> > > > Hi Christian,
> > > >
> > > > 2016/1/28 Thu 15:52:54
Christian Brabandt wrote:
> On So, 31 Jan 2016, Bram Moolenaar wrote:
>
> > A bit difficult to read an .md file patch...
>
> I can push the patch and then you can read the result at github.
Sure. You can always improve it later.
> > I think what's still missing is an explanation of how to in
On So, 31 Jan 2016, Bram Moolenaar wrote:
> A bit difficult to read an .md file patch...
I can push the patch and then you can read the result at github.
> I think what's still missing is an explanation of how to install those
> interfaces.
Yes, but I believe this is not part of Vim, but shou
Christian Brabandt wrote:
> On Sa, 30 Jan 2016, Bram Moolenaar wrote:
>
> > I'm awaiting feedback. If it looks OK I'll add a link on the download
> > page.
> >
> > There are links to the interfaces to install, but most people will need
> > some help doing the installation. A link to that woul
On So, 31 Jan 2016, Christian Brabandt wrote:
> - Nightly Vim Windows build snapshots [more
> information](http://vim.wikia.com/wiki/Where_to_download_Vim).
> + Nightly Vim Windows build snapshots ([more
> information](http://vim.wikia.com/wiki/Where_to_download_Vim)).
BTW: The wiki p
Hi Bram!
On Sa, 30 Jan 2016, Bram Moolenaar wrote:
> I'm awaiting feedback. If it looks OK I'll add a link on the download
> page.
>
> There are links to the interfaces to install, but most people will need
> some help doing the installation. A link to that would be helpful.
How about that pa
Ken Takata wrote:
> Hi Christian,
>
> 2016/1/28 Thu 18:10:37 UTC+9 Christian Brabandt wrote:
> > Hi Ken!
> >
> > On Do, 28 Jan 2016, Ken Takata wrote:
> >
> > > Hi Christian,
> > >
> > > 2016/1/28 Thu 15:52:54 UTC+9 Christian Brabandt wrote:
> > > > Hi Ken!
> > > >
> > > > On Mi, 27 Jan 2016
Hi Ken!
On Sa, 30 Jan 2016, Ken Takata wrote:
> Has the setup of https://github.com/vim/vim-win32-installer been completed?
> It seems almost perfect except that the appveyor badge is broken.
Yes I think it is completed now. I think Bram will announce it soon. I
also noticed the broken badge. C
Hi Christian,
2016/1/28 Thu 18:10:37 UTC+9 Christian Brabandt wrote:
> Hi Ken!
>
> On Do, 28 Jan 2016, Ken Takata wrote:
>
> > Hi Christian,
> >
> > 2016/1/28 Thu 15:52:54 UTC+9 Christian Brabandt wrote:
> > > Hi Ken!
> > >
> > > On Mi, 27 Jan 2016, Ken Takata wrote:
> > >
> > > > Now I can s
Hi Ken!
On Do, 28 Jan 2016, Ken Takata wrote:
> Hi Christian,
>
> 2016/1/28 Thu 15:52:54 UTC+9 Christian Brabandt wrote:
> > Hi Ken!
> >
> > On Mi, 27 Jan 2016, Ken Takata wrote:
> >
> > > Now I can see the vim/vim-win32-installer repository. I can see the
> > > latest
> > > tag v7.4.1187, b
Hi Christian,
2016/1/28 Thu 15:52:54 UTC+9 Christian Brabandt wrote:
> Hi Ken!
>
> On Mi, 27 Jan 2016, Ken Takata wrote:
>
> > Now I can see the vim/vim-win32-installer repository. I can see the latest
> > tag v7.4.1187, but the build is not started. I suppose it was because of
> > the GitHub
Hi Ken!
On Mi, 27 Jan 2016, Ken Takata wrote:
> Now I can see the vim/vim-win32-installer repository. I can see the latest
> tag v7.4.1187, but the build is not started. I suppose it was because of
> the GitHub server trouble. I hope that clicking "NEW BUILD" button on
> appveyor goes fine.
I
Hi Christian,
2016/1/28 Thu 5:32:52 UTC+9 Christian Brabandt wrote:
> Hi Bram!
>
> On Mi, 27 Jan 2016, Bram Moolenaar wrote:
>
> >
> > Christian Brabandt wrote:
> >
> > > On Sa, 23 Jan 2016, Ken Takata wrote:
> > >
> > > > > If Bram creates this sub-repository, I can create the daily upload
Christian Brabandt wrote:
> > > On Sa, 23 Jan 2016, Ken Takata wrote:
> > >
> > > > > If Bram creates this sub-repository, I can create the daily upload
> > > > > script. However I am not sure yet, how this is supposed to work. Am I
> > > > > right, that in theory, we'd only need to run the up
Hi Bram!
On Mi, 27 Jan 2016, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Sa, 23 Jan 2016, Ken Takata wrote:
> >
> > > > If Bram creates this sub-repository, I can create the daily upload
> > > > script. However I am not sure yet, how this is supposed to work. Am I
> > > > ri
Christian Brabandt wrote:
> On Sa, 23 Jan 2016, Ken Takata wrote:
>
> > > If Bram creates this sub-repository, I can create the daily upload
> > > script. However I am not sure yet, how this is supposed to work. Am I
> > > right, that in theory, we'd only need to run the upate-repo.sh script
Hi Ken!
On Sa, 23 Jan 2016, Ken Takata wrote:
> > If Bram creates this sub-repository, I can create the daily upload
> > script. However I am not sure yet, how this is supposed to work. Am I
> > right, that in theory, we'd only need to run the upate-repo.sh script
> > once per day?
>
> Yes, r
Hi,
2016/1/24 Sun 21:24:54 UTC+9 Olaf wrote:
> On 24-Jan-16, JohnBeckett wrote:
> > An alternative would be to use brief text like the following. We can put
> > information on the wiki page which would be rewritten.
> >
> > In the following "more information" would be a link to
> > http://vim.w
On 24-Jan-16, JohnBeckett wrote:
> An alternative would be to use brief text like the following. We can put
> information on the wiki page which would be rewritten.
>
> In the following "more information" would be a link to
> http://vim.wikia.com/wiki/Where_to_download_Vim
>
> ---start---
>
>
An alternative would be to use brief text like the following. We can put
information on the wiki page which would be rewritten.
In the following "more information" would be a link to
http://vim.wikia.com/wiki/Where_to_download_Vim
---start---
Nightly Vim Windows build snapshots (more informati
Ken Takata wrote:
> Maybe, adding a link to http://ftp.vim.org/pub/vim/patches/7.4/README
On a page dedicated to discussing installing Vim, that link would be useful.
However it is of no use for someone wanting to install Vim. Anyone wanting an
old version will know what they have to do. Your do
Hi John,
Thank you for the comment.
BTW, writing English is hard for me, PR is welcome for now.
(I'm not sure whether PRs are used when the repository becomes the official
one.)
2016/1/23 Sat 14:34:22 UTC+9 JohnBeckett wrote:
> Ken Takata wrote:
> > OK, I added a note:
> > https://github.com/k-
Hi Christian,
2016/1/24 Sun 4:48:32 UTC+9 Christian Brabandt wrote:
> Hi Ken!
>
> On Fr, 22 Jan 2016, Ken Takata wrote:
>
> > Hi Bram and Christian,
> >
> > 2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote:
> > > Ken Takata wrote:
> > >
> > > > Hi Bram,
> > > >
> > > > 2016/1/17 Sun 2:06:17 U
Christian Brabandt wrote:
> On Fr, 22 Jan 2016, Ken Takata wrote:
>
> > Hi Bram and Christian,
> >
> > 2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote:
> > > Ken Takata wrote:
> > >
> > > > Hi Bram,
> > > >
> > > > 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote:
> > > > > I am including th
Hi Ken!
On Fr, 22 Jan 2016, Ken Takata wrote:
> Hi Bram and Christian,
>
> 2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> > > Hi Bram,
> > >
> > > 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote:
> > > > I am including the changes to gvim.nsi. I also updated th
Ken Takata wrote:
> OK, I added a note:
> https://github.com/k-takata/vim-win32-installer/releases
>
> I think it's ready to set up the official installer repository.
Thanks for setting that up. It will be of great benefit. However, can the
explanatory text be improved? If each release has to hav
Hi Bram,
2016/1/23 Sat 6:58:13 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > Hi Bram and Christian,
> >
> > 2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote:
> > > Ken Takata wrote:
> > >
> > > > Hi Bram,
> > > >
> > > > 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote:
> > > > > I am
Ken Takata wrote:
> Hi Bram and Christian,
>
> 2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> > > Hi Bram,
> > >
> > > 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote:
> > > > I am including the changes to gvim.nsi. I also updated the code to look
> > > > for l
Hi Bram and Christian,
2016/1/20 Wed 1:48:07 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > Hi Bram,
> >
> > 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote:
> > > I am including the changes to gvim.nsi. I also updated the code to look
> > > for libintl-8.dll, since that one uses the ic
Ken Takata wrote:
> Hi Bram,
>
> 2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote:
> > I am including the changes to gvim.nsi. I also updated the code to look
> > for libintl-8.dll, since that one uses the iconv libraray. The one I
> > used so far was quite old.
> >
> > Please let me know if
Hi Bram,
2016/1/17 Sun 2:06:17 UTC+9 Bram Moolenaar wrote:
> I am including the changes to gvim.nsi. I also updated the code to look
> for libintl-8.dll, since that one uses the iconv libraray. The one I
> used so far was quite old.
>
> Please let me know if this doesn't work and further change
Ken Takata wrote:
> Hi Bram and Christian,
>
> 2016/1/10 Sun 23:46:57 UTC+9 Bram Moolenaar wrote:
> > Christian Brabandt wrote:
> >
> > > On So, 10 Jan 2016, Bram Moolenaar wrote:
> > > >
> > > > Ken Takata wrote:
> > > >
> > > > > Hi Bram and all,
> > > > >
> > > > > 2016/1/2 Sat 22:14:01 U
Hi Christian,
2016/1/12 Tue 20:40:37 UTC+9 Christian Brabandt wrote:
> On Fr, 08 Jan 2016, Ken Takata wrote:
>
> > Hi Bram and all,
> >
> > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > > Can we please gather the complete, step-by-step instructions? Probably
> > > the best place for thi
On Di, 12 Jan 2016, Ken Takata wrote:
> The problem is how to sync with the main repository (vim/vim).
> It would be good if we could change the Travis CI setting of vim/vim and make
> it automatically push a new change to the special repository.
> (I don't know how to do it.)
I am inclined to sa
Hi Christian,
2016/1/12 Tue 20:40:37 UTC+9 Christian Brabandt wrote:
> On Fr, 08 Jan 2016, Ken Takata wrote:
>
> > Hi Bram and all,
> >
> > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > > Can we please gather the complete, step-by-step instructions? Probably
> > > the best place for thi
On Tuesday, January 12, 2016 at 6:26:58 AM UTC-6, Ken Takata wrote:
> Then, how about creating a special repository for building Win32 installer?
> E.g. https://github.com/vim/vim-win32-installer
>
> The problem is how to sync with the main repository (vim/vim).
> It would be good if we could cha
Hi Bram,
2016/1/11 Mon 6:22:52 UTC+9 Bram Moolenaar wrote:
> Christian Brabandt wrote:
>
> > > > On So, 10 Jan 2016, Bram Moolenaar wrote:
> > > > >
> > > > > Ken Takata wrote:
> > > > >
> > > > > > Hi Bram and all,
> > > > > >
> > > > > > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> >
Hi Bram and Christian,
2016/1/10 Sun 23:46:57 UTC+9 Bram Moolenaar wrote:
> Christian Brabandt wrote:
>
> > On So, 10 Jan 2016, Bram Moolenaar wrote:
> > >
> > > Ken Takata wrote:
> > >
> > > > Hi Bram and all,
> > > >
> > > > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > > > > Can we
On Fr, 08 Jan 2016, Ken Takata wrote:
> Hi Bram and all,
>
> 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > Can we please gather the complete, step-by-step instructions? Probably
> > the best place for this is src/INSTALLpc.txt.
>
> I wrote it. Please review.
>
> I also updated the appv
Christian Brabandt wrote:
> > > On So, 10 Jan 2016, Bram Moolenaar wrote:
> > > >
> > > > Ken Takata wrote:
> > > >
> > > > > Hi Bram and all,
> > > > >
> > > > > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > > > > > Can we please gather the complete, step-by-step instructions?
> > >
Hi Bram!
On So, 10 Jan 2016, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On So, 10 Jan 2016, Bram Moolenaar wrote:
> > >
> > > Ken Takata wrote:
> > >
> > > > Hi Bram and all,
> > > >
> > > > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > > > > Can we please gather the c
Christian Brabandt wrote:
> On So, 10 Jan 2016, Bram Moolenaar wrote:
> >
> > Ken Takata wrote:
> >
> > > Hi Bram and all,
> > >
> > > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > > > Can we please gather the complete, step-by-step instructions? Probably
> > > > the best place for th
Hi Bram!
On So, 10 Jan 2016, Bram Moolenaar wrote:
>
> Ken Takata wrote:
>
> > Hi Bram and all,
> >
> > 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > > Can we please gather the complete, step-by-step instructions? Probably
> > > the best place for this is src/INSTALLpc.txt.
> >
> > I
Ken Takata wrote:
> Hi Bram and all,
>
> 2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> > Can we please gather the complete, step-by-step instructions? Probably
> > the best place for this is src/INSTALLpc.txt.
>
> I wrote it. Please review.
Great, thanks. Let me include this now. We c
On 09-Jan-16, Justin M. Keyes wrote:
> On Sat, Jan 9, 2016 at 7:29 PM, Olaf Dabrunz wrote:
> > On 09-Jan-16, Olaf Dabrunz wrote:
> >> Note that the existing diff tools that we all use every day bring in
> >> heuristical speed improvements, and do pre- and postprocessing to
> >> improve the results
On Sat, Jan 9, 2016 at 7:29 PM, Olaf Dabrunz wrote:
> On 09-Jan-16, Olaf Dabrunz wrote:
>> Note that the existing diff tools that we all use every day bring in
>> heuristical speed improvements, and do pre- and postprocessing to
>> improve the results.
>
> To clarify: the pre- and post-processing
On 09-Jan-16, Olaf Dabrunz wrote:
> Note that the existing diff tools that we all use every day bring in
> heuristical speed improvements, and do pre- and postprocessing to
> improve the results.
To clarify: the pre- and post-processing improve the result of the diff,
regardless of whether any spe
On 01-Jan-16, Bram Moolenaar wrote:
>
> I wrote:
>
> > Ken Takata wrote:
> >
> > > 2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > > > > 1. About diff.exe
> > > > >
> > > > > diff.exe from gnuwin32 is 32-bit binary, and it uses gettext and
> > > > > libiconv.
> > > > > Doesn't it conflict
Hi Bram and all,
2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> Can we please gather the complete, step-by-step instructions? Probably
> the best place for this is src/INSTALLpc.txt.
I wrote it. Please review.
I also updated the appveyor script:
https://github.com/k-takata/vim/tree/chrisbr
Ken Takata wrote:
> 2016/1/5 Tue 21:40:45 UTC+9 Ken Takata wrote:
> > > > > I tried Ruby 2.2, but it appears it doesn't work with MSVC.
> > > > > The config.h include file is in include/ruby-2.2.0/i386-mingw32.
> > > > > Trying to change the path for that results in a missing "strings.h"
> > > >
Hi,
I have updated the appveyor scripts:
https://github.com/k-takata/vim/tree/chrisbra-appveyor-build
Changes from my previous mail(*) are:
(*) https://groups.google.com/d/msg/vim_dev/dAXpcpHmVw4/D_s6iwajAQAJ
* Sync with v7.4.1051.
* Fix that forgetting to set TCL_VER_LONG.
* Skip building x64 i
Hi,
2016/1/5 Tue 21:40:45 UTC+9 Ken Takata wrote:
> > > > I tried Ruby 2.2, but it appears it doesn't work with MSVC.
> > > > The config.h include file is in include/ruby-2.2.0/i386-mingw32.
> > > > Trying to change the path for that results in a missing "strings.h"
> > > > include file, I assume
Hi Bram,
2016/1/2 Sat 22:14:01 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > 2016/1/2 Sat 6:30:39 UTC+9 Bram Moolenaar wrote:
> > > Ken Takata wrote:
> > >
> > > [...]
> > >
> > > > 3. Updated if_xx
> > > > ActivePerl 5.22
> > > > ActiveTcl 8.6
> > > > LuaBinaries 5.3
> > > > Py
On Di, 05 Jan 2016, Christian Brabandt wrote:
> Such ideas should be documented somewhere, so that people will find
> it easier,
> e.g. something like this:
> http://vim.wikia.com/wiki/Vim_GSoC_2011_Ideas
> (much of this still holds)
> I have tried to log in to create a new page, but it seems wik
Am 2016-01-01 16:53, schrieb Bram Moolenaar:
I wrote:
Ken Takata wrote:
> 2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > > 1. About diff.exe
> > >
> > > diff.exe from gnuwin32 is 32-bit binary, and it uses gettext and libiconv.
> > > Doesn't it conflict with 64-bit builds? diff.exe bund
Ken Takata wrote:
> 2016/1/2 Sat 6:30:39 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> > [...]
> >
> > > 3. Updated if_xx
> > > ActivePerl 5.22
> > > ActiveTcl 8.6
> > > LuaBinaries 5.3
> > > Python 2.7
> > > Python 3.4
> > > RubyInstaller 2.2
> >
> > I'm updating my Wind
On Fr, 01 Jan 2016, Bram Moolenaar wrote:
> There have been many discussions in the past about whether a 64-bit
> build was useful. The outcome is still that the 32-bit build works for
> everybody. It's simpler for users to not have to chose. I plan to only
> distribute a 32-bit version.
Can w
Hi Bram
2016/1/2 Sat 2:48:13 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > Hi Bram,
> >
> > 2016/1/1 Fri 23:19:41 UTC+9 Bram Moolenaar wrote:
> > > Ken Takata wrote:
> > >
> > > > 2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > > > > > 1. About diff.exe
> > > > > >
> > > > > > dif
Hi Bram,
2016/1/2 Sat 6:30:39 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> [...]
>
> > 3. Updated if_xx
> > ActivePerl 5.22
> > ActiveTcl 8.6
> > LuaBinaries 5.3
> > Python 2.7
> > Python 3.4
> > RubyInstaller 2.2
>
> I'm updating my Windows machine with these. I'll use Pyth
Bram Moolenaar schrob am Freitag, 1. Januar 2016 um 22:54 Zeit:
> I have never built Ruby on Windows, are there instructions to follow?
Yep: https://github.com/ruby/ruby/tree/trunk/win32
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the tex
Tux wrote:
> Bram Moolenaar schrob am Freitag, 1. Januar 2016 um 22:30 Zeit:
>
> > I tried Ruby 2.2, but it appears it doesn't work with MSVC.
>
> Right, you'll need a self-built Ruby for that. This was discussed on
> this mailing list:
>
> https://groups.google.com/d/msg/vim_dev/P8l30hk9hyE/c
Bram Moolenaar schrob am Freitag, 1. Januar 2016 um 22:30 Zeit:
> I tried Ruby 2.2, but it appears it doesn't work with MSVC.
Right, you'll need a self-built Ruby for that. This was discussed on
this mailing list:
https://groups.google.com/d/msg/vim_dev/P8l30hk9hyE/cG8wYjh3paMJ
--
--
You rece
Ken Takata wrote:
[...]
> 3. Updated if_xx
> ActivePerl 5.22
> ActiveTcl 8.6
> LuaBinaries 5.3
> Python 2.7
> Python 3.4
> RubyInstaller 2.2
I'm updating my Windows machine with these. I'll use Python 2.7.10
(since 2.7.11 has a problem).
Unfortunately, Vim can't load "python35.dll
Hi Bram!
On Fr, 01 Jan 2016, Bram Moolenaar wrote:
> Building once per day should be sufficient. Picking a version every
> week would even be fine.
I think the idea is once you merge this, that once you tag a commit,
appveyor will automatically build a new release and upload it to
https://git
Ken Takata wrote:
> Hi Bram,
>
> 2016/1/1 Fri 23:19:41 UTC+9 Bram Moolenaar wrote:
> > Ken Takata wrote:
> >
> > > 2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > > > > 1. About diff.exe
> > > > >
> > > > > diff.exe from gnuwin32 is 32-bit binary, and it uses gettext and
> > > > > libico
Hi Bram,
2016/1/1 Fri 23:19:41 UTC+9 Bram Moolenaar wrote:
> Ken Takata wrote:
>
> > 2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > > > 1. About diff.exe
> > > >
> > > > diff.exe from gnuwin32 is 32-bit binary, and it uses gettext and
> > > > libiconv.
> > > > Doesn't it conflict with 64-
I wrote:
> Ken Takata wrote:
>
> > 2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > > > 1. About diff.exe
> > > >
> > > > diff.exe from gnuwin32 is 32-bit binary, and it uses gettext and
> > > > libiconv.
> > > > Doesn't it conflict with 64-bit builds? diff.exe bundled with the
> > > > o
Ken Takata wrote:
> 2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > > 1. About diff.exe
> > >
> > > diff.exe from gnuwin32 is 32-bit binary, and it uses gettext and libiconv.
> > > Doesn't it conflict with 64-bit builds? diff.exe bundled with the
> > > official
> > > Vim 7.4 installer doe
Hi Bram,
2016/1/1 Fri 4:10:22 UTC+9 Bram Moolenaar wrote:
> > 1. About diff.exe
> >
> > diff.exe from gnuwin32 is 32-bit binary, and it uses gettext and libiconv.
> > Doesn't it conflict with 64-bit builds? diff.exe bundled with the official
> > Vim 7.4 installer doesn't depend on gettext and li
On Do, 31 Dez 2015, Bram Moolenaar wrote:
>
> Ken Takata wrote:
>
> > Happy New Year (in JST)!
>
> Still a few hours away here...
That means you have more time to push patches?
You are not supposed to work today, but rather take a break.
Best,
Christian
--
Die Dichter sind gegen ihre Erlebn
Ken Takata wrote:
> Happy New Year (in JST)!
Still a few hours away here...
> 2015/12/31 Thu 19:54:46 UTC+9 Christian Brabandt wrote:
> > On Mo, 28 Dez 2015, Christian Brabandt wrote:
> >
> > > Great work. With your help I updated the configuration like this:
> > > https://github.com/chrisbra/
Happy New Year (in JST)!
2015/12/31 Thu 19:54:46 UTC+9 Christian Brabandt wrote:
> On Mo, 28 Dez 2015, Christian Brabandt wrote:
>
> > Great work. With your help I updated the configuration like this:
> > https://github.com/chrisbra/vim/blob/appveyor-build/appveyor.yml
> > and
> > https://github.
On Mo, 28 Dez 2015, Christian Brabandt wrote:
> Great work. With your help I updated the configuration like this:
> https://github.com/chrisbra/vim/blob/appveyor-build/appveyor.yml
> and
> https://github.com/chrisbra/vim/blob/appveyor-build/src/appveyor.bat
I updated the build script a little. No
On Monday, December 28, 2015 at 2:37:20 PM UTC-6, Christian Brabandt wrote:
> >
> > Except that we use Vim to run the update script, thus it's running while
> > updating.
>
> Ah, I haven't thought about that. I rather thought, the :Update command
> checks, whether a new version is available and
Hi Bram!
On Mo, 28 Dez 2015, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On So, 27 Dez 2015, Bram Moolenaar wrote:
> >
> > > It's included in the distribution files. I can add it to the git files,
> > > if needed. Likewise for other binaries that are not so easy to obtain.
> >
Christian Brabandt wrote:
> On So, 27 Dez 2015, Bram Moolenaar wrote:
>
> > It's included in the distribution files. I can add it to the git files,
> > if needed. Likewise for other binaries that are not so easy to obtain.
>
> Can't you include and distribute the source?
Perhaps. I haven't
Hi Ken,
On Mo, 28 Dez 2015, Ken Takata wrote:
> 2015/12/28 Mon 7:24:24 UTC+9 Christian Brabandt wrote:
> > I will update to use OLE and DIRECTX. From a first try, a +perl enabled
> > build did not link and so did the ruby versions 193 and 200 so I will
> > leave this out. And since this is only
Hi Christian,
2015/12/28 Mon 7:24:24 UTC+9 Christian Brabandt wrote:
> I will update to use OLE and DIRECTX. From a first try, a +perl enabled
> build did not link and so did the ruby versions 193 and 200 so I will
> leave this out. And since this is only for daily Windows snapshots, I
> think
2015-12-28 1:24 GMT+03:00 Christian Brabandt :
> Hi Ken!
>
> On So, 27 Dez 2015, Ken Takata wrote:
>
> > 2015/12/28 Mon 0:53:53 UTC+9 Christian Brabandt wrote:
> > > Hi Ken!
> > >
> > > On So, 27 Dez 2015, Ken Takata wrote:
> > >
> > > > Hi Christian,
> > > >
> > > > Great work!
> > > > But unfort
Hi Bram!
On So, 27 Dez 2015, Bram Moolenaar wrote:
> It's included in the distribution files. I can add it to the git files,
> if needed. Likewise for other binaries that are not so easy to obtain.
Can't you include and distribute the source?
> e.g. gvimext64.dll.
What is that used for? Is t
Hi Ken!
On So, 27 Dez 2015, Ken Takata wrote:
> 2015/12/28 Mon 0:53:53 UTC+9 Christian Brabandt wrote:
> > Hi Ken!
> >
> > On So, 27 Dez 2015, Ken Takata wrote:
> >
> > > Hi Christian,
> > >
> > > Great work!
> > > But unfortunately some features are disabled:
> > > * DirectWrite
> >
> > What
2015-12-27 23:20 GMT+03:00 Bram Moolenaar :
>
> Ken Takata wrote:
>
> > Great work!
> > But unfortunately some features are disabled:
> > * DirectWrite
> > * OLE
> > * Lua
> > * Perl
> > * Ruby
> > * Tcl
> > * Build *.mo files
> > * vim.exe
>
> [...]
>
> > > I think, the Vim release from vim.org d
Ken Takata wrote:
> Great work!
> But unfortunately some features are disabled:
> * DirectWrite
> * OLE
> * Lua
> * Perl
> * Ruby
> * Tcl
> * Build *.mo files
> * vim.exe
[...]
> > I think, the Vim release from vim.org did bundle a diff.exe, but I don't
> > know how this was build, so this is
On 2015-12-27, Christian Brabandt wrote:
> Is OLE really needed today?
David Fishburn's OutlookVim plugin uses OLE.
Regards,
Gary
--
--
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:
Hi Christian,
2015/12/28 Mon 0:53:53 UTC+9 Christian Brabandt wrote:
> Hi Ken!
>
> On So, 27 Dez 2015, Ken Takata wrote:
>
> > Hi Christian,
> >
> > Great work!
> > But unfortunately some features are disabled:
> > * DirectWrite
>
> What feature is this?
Please check v7.4.393.
Currently, Dire
Hi Ken!
On So, 27 Dez 2015, Ken Takata wrote:
> Hi Christian,
>
> Great work!
> But unfortunately some features are disabled:
> * DirectWrite
What feature is this?
> * OLE
> * Lua
> * Perl
> * Ruby
> * Tcl
Hm, perl is available as version 5.20.1.2000 in x86. So no x64 version.
Is that the co
Hi Christian,
Great work!
But unfortunately some features are disabled:
* DirectWrite
* OLE
* Lua
* Perl
* Ruby
* Tcl
* Build *.mo files
* vim.exe
2015/12/27 Sun 7:42:23 UTC+9 Christian Brabandt wrote:
> On Mi, 23 Dez 2015, Christian Brabandt wrote:
>
> > On Do, 24 Dez 2015, Nikolay Aleksandrovi
On Mi, 23 Dez 2015, Christian Brabandt wrote:
> On Do, 24 Dez 2015, Nikolay Aleksandrovich Pavlov wrote:
> > The main reason why your scripts have such value is that they yield an
> > installer. Hosting is much less of a problem: e.g. GH provides hosting and
> > appveyor has http://www.appveyor.co
On Wed, Dec 23, 2015 at 4:10 AM, Christian J. Robinson
wrote:
> On Tue, 22 Dec 2015, James McCoy wrote:
>
>> On Tue, Dec 22, 2015 at 08:09:47PM -0500, Jonathan Newton wrote:
>>>
>>> I guess the use case for :RuntimeUpdate is not clear to me. Do you really
>>> want a user (perhaps inexperienced at
On Wed, Dec 23, 2015 at 4:09 PM, Nikolay Aleksandrovich Pavlov
wrote:
>
> (not worth the hassle IMO, just migrate out of that junk).
Exactly.
I've just asked github to check my username in case that is an option.
(Someone appears to be squatting it.) I'd like to put Cream somewhere
else, too.
On Do, 24 Dez 2015, Nikolay Aleksandrovich Pavlov wrote:
> The main reason why your scripts have such value is that they yield an
> installer. Hosting is much less of a problem: e.g. GH provides hosting and
> appveyor has http://www.appveyor.com/docs/deployment/github, there are other
> deployment
2015-12-23 23:44 GMT+03:00 Steve Hall :
> On Wed, Dec 23, 2015 at 2:23 PM, Nikolay Aleksandrovich Pavlov <
> zyx@gmail.com> wrote:
> >
> [...]
> > Vim without Cream definitely has some automation I think, don’t know
> > whether it is or can be public or not.
>
> I'm glad to share my scripts, b
On Wed, Dec 23, 2015 at 2:23 PM, Nikolay Aleksandrovich Pavlov <
zyx@gmail.com> wrote:
>
[...]
> Vim without Cream definitely has some automation I think, don’t know
> whether it is or can be public or not.
I'm glad to share my scripts, but I think what we all want is a secure
system with only
2015-12-23 21:16 GMT+03:00 Jonathan Newton :
> On Wed, Dec 23, 2015 at 11:53 AM, Bram Moolenaar
> wrote:
>
>>
>> Jonathan Newton wrote:
>>
>> > How are the installer packages from vim.org produced? Could something
>> be
>> > setup to trigger production of these files at regular cadence?
>>
>> It'
Jonathan Newton wrote:
> On Wed, Dec 23, 2015 at 11:53 AM, Bram Moolenaar wrote:
>
> > Jonathan Newton wrote:
> >
> > > How are the installer packages from vim.org produced? Could something be
> > > setup to trigger production of these files at regular cadence?
> >
> > It's a sequence of comman
On Wed, Dec 23, 2015 at 11:53 AM, Bram Moolenaar wrote:
>
> Jonathan Newton wrote:
>
> > How are the installer packages from vim.org produced? Could something be
> > setup to trigger production of these files at regular cadence?
>
> It's a sequence of commands that need to be executed on a prepar
Hirohito Higashi wrote:
> Hi Bram and Vimmers!
>
> 2015-12-22(Tue) 5:44:27 UTC+9 Bram Moolenaar:
> > Since Vim is very stable, it does not happen often that a new version is
> > released. Mostly it's fine to run an older version. Unless you run into
> > a bug there is no pressing reason to upda
1 - 100 din 129 matches
Mail list logo
