Mike Williams wrote:
> I have just tried to bring my windows VIM builds up to date and find the
> gvim build is failing with the following error:
>
> gui_dwrite.cpp(41) : fatal error C1083: Cannot open include file:
> 'dwrite_2.h': No such file or directory
>
> This started with patch 1343
Hi
On 14/12/2017 12:15, Bram Moolenaar wrote:
Mike Williams wrote:
I have just tried to bring my windows VIM builds up to date and find the
gvim build is failing with the following error:
gui_dwrite.cpp(41) : fatal error C1083: Cannot open include file:
'dwrite_2.h': No such file or
Am 13.12.2017 um 22:43 schrieb Gary Johnson:
To follow up, here is what I did to fix the problematic function in
my plugin. I added code above and below this line, which had been
modifying every line in a closed fold instead of just l:lnum,
silent exe l:lnum.'s/:.*/:\t'.strftime("%Y-%m-%d
On 2017-12-14, 'Andy Wokula' via vim_dev wrote:
> Am 13.12.2017 um 22:43 schrieb Gary Johnson:
> >To follow up, here is what I did to fix the problematic function in
> >my plugin. I added code above and below this line, which had been
> >modifying every line in a closed fold instead of just
On Thu, Dec 14, 2017 at 08:12:49PM +0100, Bram Moolenaar wrote:
>
> Marius Gedminas wrote:
>
> > I git pull vim's master a few times a week to test the latest features.
> > Unfortunately it has recently become painful to use due to netrw's bugs.
> > I keep finding my options (like 'nohidden',
Marius Gedminas wrote:
> I git pull vim's master a few times a week to test the latest features.
> Unfortunately it has recently become painful to use due to netrw's bugs.
> I keep finding my options (like 'nohidden', but sometimes even 'readonly',
> 'nomodifiable' and 'buftype') blatantly
On Wednesday, December 13, 2017 at 7:27:59 PM UTC-8, David Kotchan wrote:
> OK I have re-pulled, and am now on the "optimize-directx" branch, which has
> latest commit 9af94dbea8389a5e31a946f53d9d7a11561d1456, one commit after the
> 0e7d0764 commit you mention above. I will try this branch (at
As long as Dr. Chip works on a Windows pc for a week, he will find netrw is
totally crap on Windows.
在 2017年12月15日星期五 UTC+8上午11:31:48，K.Takata写道：
> Hi Dr. Chip,
>
> There are more than 20 issues related to netrw in this repository.
>
> You can easily find them by searching the plugin-netrw
On Do, 14 Dez 2017, Wei Zhang wrote:
> As long as Dr. Chip works on a Windows pc for a week, he will find netrw is
> totally crap on Windows.
Perhaps you have a more constructive feedback?
Christian
--
Falten machen einen Mann männlicher, eine Frau älter.
-- Jeanne Moreau
--
Hi David,
2017/12/15 Fri 3:20:16 UTC+9 David Kotchan wrote:
> On Wednesday, December 13, 2017 at 7:27:59 PM UTC-8, David Kotchan wrote:
>
> > OK I have re-pulled, and am now on the "optimize-directx" branch, which has
> > latest commit 9af94dbea8389a5e31a946f53d9d7a11561d1456, one commit after
Hi!
I git pull vim's master a few times a week to test the latest features.
Unfortunately it has recently become painful to use due to netrw's bugs.
I keep finding my options (like 'nohidden', but sometimes even 'readonly',
'nomodifiable' and 'buftype') blatantly changed behind my back, and
11 matches
Mail list logo
