2016-04-27 18:30 GMT+03:00 Jacky Liu :
> On Tuesday, April 26, 2016 at 4:29:07 PM UTC+8, Markus Meskanen wrote:
>> While I don't expect Vim to become an easy-to-use text editor for beginners
>> or anything, the current Python support simply isn't enough for a standard
>>
Charles Campbell wrote:
> Bram Moolenaar wrote:
>> Charles Campbell wrote:
>>
>>> Bram Moolenaar wrote:
Patch 7.4.1770
Problem:Cannot use true color in the terminal.
Solution: Add the 'guicolors' option. (Nikolai Pavlov)
Files: runtime/doc/options.txt,
When a 'make test' fails, the subsequent 'make test' often succeeds.
Though I'm not sure the comparison between those two cases could be
helpful, I'm sending you two channellogs --- the first 'make test' failed
(channellog.failed) but the second 'make test' succeeded
(channellog.success)
2016-04-28 4:47 GMT+09:00 Bram Moolenaar :
>
> Kazunobu Kuriyama wrote:
>
> > 2016-04-28 0:42 GMT+09:00 Bram Moolenaar :
> >
> > >
> > > Kazunobu Kuriyama wrote:
> > >
> > > > 2016-04-27 17:51 GMT+09:00 Bram Moolenaar :
> > > >
> > > > >
Kazunobu Kuriyama wrote:
> 2016-04-28 0:42 GMT+09:00 Bram Moolenaar :
>
> >
> > Kazunobu Kuriyama wrote:
> >
> > > 2016-04-27 17:51 GMT+09:00 Bram Moolenaar :
> > >
> > > >
> > > > Christian Brabandt wrote:
> > > >
> > > > > Am 2016-04-26 19:01, schrieb
Ken Takata wrote:
> 2016/4/27 Wed 5:48:41 UTC+9 Heptite wrote:
> > Something went wrong with this patch. Most of my colors are wrong.
> >
> > How it looks now:
> > https://www.dropbox.com/s/q8wc4vzkg8r0uj2/vimwrongcolors.png?dl=0
> >
> > How it should look:
> >
Patch 7.4.1796 (after 7.4.1795)
Problem:Colors are wrong on MS-Windows. (Christian Robinson)
Solution: Use existing RGB macro if it exists. (Ken Takata)
Files: src/term.c
*** ../vim-7.4.1795/src/term.c 2016-04-26 22:33:11.913443804 +0200
--- src/term.c 2016-04-27 20:35:31.865622983
Hi Bram!
On Mi, 27 Apr 2016, Bram Moolenaar wrote:
> I noticed the travis build also failed with this error, but then passed
> later. For me it always passes, thus it's hard to find out why it would
> sometimes fail. It looks like the callback is invoked twice, but I
> don't know why/when that
2016-04-28 0:42 GMT+09:00 Bram Moolenaar :
>
> Kazunobu Kuriyama wrote:
>
> > 2016-04-27 17:51 GMT+09:00 Bram Moolenaar :
> >
> > >
> > > Christian Brabandt wrote:
> > >
> > > > Am 2016-04-26 19:01, schrieb Bram Moolenaar:
> > > > > Patch 7.4.1789
> > > >
>
Kazunobu Kuriyama wrote:
> 2016-04-27 17:51 GMT+09:00 Bram Moolenaar :
>
> >
> > Christian Brabandt wrote:
> >
> > > Am 2016-04-26 19:01, schrieb Bram Moolenaar:
> > > > Patch 7.4.1789
> > >
> > > I think this patch broke the vim-win32-installer build
> > >
> > > From
On Tuesday, April 26, 2016 at 4:29:07 PM UTC+8, Markus Meskanen wrote:
> While I don't expect Vim to become an easy-to-use text editor for beginners
> or anything, the current Python support simply isn't enough for a standard
> coder. Vim doesn't support multiple Python versions, so you have to
Bram Moolenaar wrote:
> Charles Campbell wrote:
>
>> Bram Moolenaar wrote:
>>> Patch 7.4.1770
>>> Problem:Cannot use true color in the terminal.
>>> Solution: Add the 'guicolors' option. (Nikolai Pavlov)
>>> Files: runtime/doc/options.txt, runtime/doc/term.txt,
>>>
> On 26 Apr 2016, at 8:38 pm, Bram Moolenaar wrote:
>
> You can now use ch_status() for that. If it returns "open" or
> "buffered" there may be more to read. When "closed" then it's done.
>
> I have added this example in the help:
>
> func! CloseHandler(channel)
>
2016-04-27 17:51 GMT+09:00 Bram Moolenaar :
>
> Christian Brabandt wrote:
>
> > Am 2016-04-26 19:01, schrieb Bram Moolenaar:
> > > Patch 7.4.1789
> >
> > I think this patch broke the vim-win32-installer build
> >
> > From test_channel.vim:
> > Found errors in
Charles Campbell wrote:
> Bram Moolenaar wrote:
> > Patch 7.4.1770
> > Problem:Cannot use true color in the terminal.
> > Solution: Add the 'guicolors' option. (Nikolai Pavlov)
> > Files: runtime/doc/options.txt, runtime/doc/term.txt,
> > runtime/doc/various.txt,
Christian Brabandt wrote:
> Am 2016-04-26 19:01, schrieb Bram Moolenaar:
> > Patch 7.4.1789
>
> I think this patch broke the vim-win32-installer build
>
> From test_channel.vim:
> Found errors in Test_out_close_cb():
> function RunTheTest[9]..Test_out_close_cb line 23: Expected 1 but got 2
>
Hi Bram, Ken and list,
2016-4-25(Mon) 19:04:59 UTC+9 h_east:
> Hi Ken!
>
> 2016-4-25(Mon) 18:58:05 UTC+9 Ken Takata:
> > Hi h_east,
> >
> > 2016/4/25 Mon 6:51:36 UTC+9 h_east wrote:
> > > Hi Bram and List!
> > >
> > > 2016-4-25(Mon) 5:03:24 UTC+9 Bram Moolenaar:
> > > > Hirohito Higashi wrote:
Am 2016-04-26 19:01, schrieb Bram Moolenaar:
Patch 7.4.1789
I think this patch broke the vim-win32-installer build
From test_channel.vim:
Found errors in Test_out_close_cb():
function RunTheTest[9]..Test_out_close_cb line 23: Expected 1 but got 2
function RunTheTest[9]..Test_out_close_cb
Am 2016-04-27 08:33, schrieb Kazunobu Kuriyama:
On Windows 2000 or later, there has already been a macro called RGB
[1], which conflicts with ours in term.c.
This caused a compiler warning on Windows as reported by John
Marriott.
Thus Patch 1795 renamed ours from RGB to TORGB to avoid the name
On Windows 2000 or later, there has already been a macro called RGB [1],
which conflicts with ours in term.c.
This caused a compiler warning on Windows as reported by John Marriott.
Thus Patch 1795 renamed ours from RGB to TORGB to avoid the name conflict.
Now we have wrong colors on Windows as
Hi,
2016/4/27 Wed 15:03:06 UTC+9 Marius Gedminas wrote:
> On Tue, Apr 26, 2016 at 02:48:48PM -0600, Christian J. Robinson wrote:
> >
> > Something went wrong with this patch. Most of my colors are wrong.
> >
> > How it looks now:
> >
On Tue, Apr 26, 2016 at 02:48:48PM -0600, Christian J. Robinson wrote:
>
> Something went wrong with this patch. Most of my colors are wrong.
>
> How it looks now:
> https://www.dropbox.com/s/q8wc4vzkg8r0uj2/vimwrongcolors.png?dl=0
>
> How it should look:
>
22 matches
Mail list logo