I found this email still waiting as an unsent "draft" — and the
compiler warning in question is still there at the current patchlevel.
Sorry.
On Tue, Dec 29, 2015 at 6:56 PM, Bram Moolenaar wrote:
>
> Patch 7.4.995
> Problem:gdk_pixbuf_new_from_inline() is deprecated.
> Solution: Generate a
Hi tot-to,
2016/1/2 Sat 13:19:05 UTC+9 tot-to wrote:
> https://bugs.gentoo.org/show_bug.cgi?id=559800
>
> Previously, I haven't set textwidth in .vimrc and it was no
> autowrapping by default in all files.
>
> At some point (probably after an upgrade) it stared to do autowrap, but
> only for *.t
On Wednesday, December 30, 2015 at 1:49:59 AM UTC-6, titus65 wrote:
> Hi,
>
>
> Since upgrading from 74488 to 74963 my custom highlighting
>
> rules are no longer effective
>
>
> Here is the vimrctest that demonstrates the problem:
>
> " comment this should appear in DarkCyan
> set nocomp
https://bugs.gentoo.org/show_bug.cgi?id=559800
Previously, I haven't set textwidth in .vimrc and it was no
autowrapping by default in all files.
At some point (probably after an upgrade) it stared to do autowrap, but
only for *.txt files, i.e. if I open such file and enter the
command :set tw I g
Hi Ken,
On Thu, Dec 31, 2015 at 10:15 PM, Ken Takata wrote:
> 2016/1/1 Fri 11:13:23 UTC+9 Steve Hall wrote:
> >
> > This was Ruby 1.9.x (http://rubyinstaller.org). I just upgraded to
> > 2.1.7 and tried again:
>
> I tested RubyInstaller 1.9.3 with Make_cyg.mak and it successfully
> compiled. (7.4
> Patch 7.4.995
> Problem:gdk_pixbuf_new_from_inline() is deprecated.
I was pleased to see this patch come, the deprecation warning is annoying if
one is in the habit of watching out for warnings. However, I still got the
warning; my version of gdk-pixbuf-2.0 is 2.31.3, with Ubuntu 15.04.
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
On Fri, Jan 1, 2016 at 4:35 PM, wrote:
> Last night, just at the New Year, I have discovered for myself a stenotyping
> with Plover:
> http://stenoknight.com/wiki/FAQ
> http://www.openstenoproject.org/
> http://stenoknight.com/kws.html
> and I think it is great!
>
> I do not need or want to lear
On Thu, Dec 31, 2015 at 7:39 PM, Bram Moolenaar wrote:
>
> Yasuhiro Matsumoto wrote:
>
>> https://i.gyazo.com/4b7219eee71af32831e4f3662075bea7.png
>
> Unfortunately color schemes can make this look ugly.
> Like the idea though.
>
The version in the current Vim is just the sunny face I need in the
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
Patch 7.4.1022
Problem:The README file contains some outdated information.
Solution: Update the information about supported systems.
Files: README.txt, README.md
*** ../vim-7.4.1021/README.txt 2015-10-25 13:54:55.295855322 +0100
--- README.txt 2016-01-01 18:33:18.881427028 +0100
***
Ahh ... that does the trick. Thank you! :)
--
--
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 t
Hi tux,
(My previous message should point this:
https://github.com/vim/vim/issues/526#issuecomment-164958769 )
2016/1/2 Sat 1:59:29 UTC+9 tux. wrote:
> Renaming the registry key does not fix the issue for me though :/
Which python do you use, 32-bit or 64-bit?
If you use 32-bit python on 64-bi
Renaming the registry key does not fix the issue for me though :/
--
--
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
Patch 7.4.1021
Problem:Some makefiles are outdated.
Solution: Add a note to warn developers.
Files: src/Make_manx.mak, src/Make_bc3.mak, src/Make_bc5.mak,
src/Make_djg.mak, src/Make_w16.mak
*** ../vim-7.4.1020/src/Make_manx.mak 2014-08-10 16:31:47.372709213 +0200
--- src
Hi tux,
2016/1/2 Sat 1:37:50 UTC+9 tux. wrote:
> I updated my Python 2.7.10 to 2.7.11 and compiled Vim (Make_mvc, my
> compile.bat is available online [1]) again, now I get "the Python's
> site module is not available" every time I type :python (something).
>
> Has anything relevant changed in Py
Patch 7.4.1020
Problem:On MS-Windows there is no target to run tests with gvim.
Solution: Add the testgvim target.
Files: src/Make_mvc.mak
*** ../vim-7.4.1019/src/Make_mvc.mak2015-12-31 20:54:16.254494780 +0100
--- src/Make_mvc.mak2016-01-01 17:30:39.016224840 +0100
**
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 updated my Python 2.7.10 to 2.7.11 and compiled Vim (Make_mvc, my
compile.bat is available online [1]) again, now I get "the Python's
site module is not available" every time I type :python (something).
Has anything relevant changed in Python itself or was one of the last
few dozen patches quirk
Last night, just at the New Year, I have discovered for myself a stenotyping
with Plover:
http://stenoknight.com/wiki/FAQ
http://www.openstenoproject.org/
http://stenoknight.com/kws.html
and I think it is great!
I do not need or want to learn stenotyping in full (at least because it does
not exi
Patch 7.4.1019
Problem:Directory listing of "src" is too long.
Solution: Rename the resources file to make it shorter.
Files: src/gui_gtk_gresources.xml, src/gui_gtk_res.xml, src/Makefile,
Filelist
*** ../vim-7.4.1018/src/gui_gtk_gresources.xml 2015-12-29 18:52:33.3480543
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
Patch 7.4.1018 (after 7.4.1017)
Problem:Failure running tests.
Solution: Add missing change to list of old style tests.
Files: src/testdir/Make_all.mak
*** ../vim-7.4.1017/src/testdir/Make_all.mak2015-12-30 15:58:58.858914450
+0100
--- src/testdir/Make_all.mak2016-01-01 14:55
Patch 7.4.1017
Problem:When there is a backslash in an option ":set -=" doesn't work.
Solution: Handle a backslash better. (Jacob Niehus) Add a new test, merge
in old test.
Files: src/testdir/test_cdo.vim, src/testdir/test_set.vim,
src/testdir/test_alot.vim, src
Jacob Niehus wrote:
> After a single backslash is added as an item in a comma-separation
> option, the items after the backslash can't be removed without removing
> the backslash first.
>
> For example:
>
> set iskeyword+=\\,!
> --> iskeyword=@,48-57,_,192-255,\,!
> set iskeyword-=!
> --> iskey
On 12/31/2015 1:49 AM, Tony Mechelynck wrote:
I see. Sounds like we need to:
(a) make langmaps apply to command-line mode by default, so Russian,
Greek, etc. users can type ex-commands by using them;
I agree. keymap applies to non-':'-cmdline. Since langmap is the inverse
of keymap, langmap shou
33 matches
Mail list logo
