Christian Brabandt wrote:
> On Do, 26 Jan 2017, Christian Brabandt wrote:
>
> > Hi Bram!
> >
> > On Do, 26 Jan 2017, Bram Moolenaar wrote:
> >
> > >
> > > Christian Brabandt wrote:
> > >
> > > [...]
> > >
> > > > > So is this ready to include now?
> > > >
> > > > I would say so.
> > >
>
Hi vim_dev!
On Do, 26 Jan 2017, Christian Brabandt wrote:
> Hi Bram!
>
> On Do, 26 Jan 2017, Bram Moolenaar wrote:
>
> >
> > Christian Brabandt wrote:
> >
> > [...]
> >
> > > > So is this ready to include now?
> > >
> > > I would say so.
> >
> > I included your change, but I see this
Hi Bram!
On Do, 26 Jan 2017, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> [...]
>
> > > So is this ready to include now?
> >
> > I would say so.
>
> I included your change, but I see this error:
>
> ImportError:
>
Christian Brabandt wrote:
[...]
> > So is this ready to include now?
>
> I would say so.
I included your change, but I see this error:
ImportError: /home/travis/.local/lib/python2.7/site-packages/_cffi_backend.so:
undefined symbol: llvm_gcda_end_file
Not sure if it is related, it comes
Hi Bram!
On Do, 26 Jan 2017, Bram Moolenaar wrote:
>
> Christian Brabandt wrote:
>
> > On Mi, 25 Jan 2017, Dominique Pellé wrote:
> >
> > > Christian Brabandt wrote:
> > >
> > > > Hi Dominique!
> > > >
> > > > On Mi, 25 Jan 2017, Dominique Pellé wrote:
> > > >
> > > >>
Christian Brabandt wrote:
> On Mi, 25 Jan 2017, Dominique Pellé wrote:
>
> > Christian Brabandt wrote:
> >
> > > Hi Dominique!
> > >
> > > On Mi, 25 Jan 2017, Dominique Pellé wrote:
> > >
> > >> Christian Brabandt wrote:
> > >>
> > >> > On Di, 24 Jan 2017, Christian
Hi Dominique!
On Mi, 25 Jan 2017, Dominique Pellé wrote:
> Christian Brabandt wrote:
>
> > Hi Dominique!
> >
> > On Mi, 25 Jan 2017, Dominique Pellé wrote:
> >
> >> Christian Brabandt wrote:
> >>
> >> > On Di, 24 Jan 2017, Christian Brabandt wrote:
> >> >
> >> >> On Di, 24
Christian Brabandt wrote:
> Hi Dominique!
>
> On Mi, 25 Jan 2017, Dominique Pellé wrote:
>
>> Christian Brabandt wrote:
>>
>> > On Di, 24 Jan 2017, Christian Brabandt wrote:
>> >
>> >> On Di, 24 Jan 2017, Dominique Pellé wrote:
>> >> > How about an address sanitizer build in
Hi Dominique!
On Mi, 25 Jan 2017, Dominique Pellé wrote:
> Christian Brabandt wrote:
>
> > On Di, 24 Jan 2017, Christian Brabandt wrote:
> >
> >> On Di, 24 Jan 2017, Dominique Pellé wrote:
> >> > How about an address sanitizer build in Travis to catch
> >> > this kind of bugs earlier in CI?
> >
Christian Brabandt wrote:
> On Di, 24 Jan 2017, Christian Brabandt wrote:
>
>> On Di, 24 Jan 2017, Dominique Pellé wrote:
>> > How about an address sanitizer build in Travis to catch
>> > this kind of bugs earlier in CI?
>
> Here is a patch.
>
> Sample logfiles here:
>
On Di, 24 Jan 2017, Christian Brabandt wrote:
> On Di, 24 Jan 2017, Dominique Pellé wrote:
> > How about an address sanitizer build in Travis to catch
> > this kind of bugs earlier in CI?
Here is a patch.
Sample logfiles here:
https://travis-ci.org/chrisbra/vim/builds/194982196
This was with
I wrote:
> Dominique Pellé wrote:
>
> > Bram Moolenaar <b...@moolenaar.net> wrote:
> >
> > > Patch 8.0.0224
> > > Problem:When 'fileformats' is changed in a BufReadPre auto command, it
> > > does not take effect in readfile(
Dominique Pellé wrote:
> Bram Moolenaar <b...@moolenaar.net> wrote:
>
> > Patch 8.0.0224
> > Problem:When 'fileformats' is changed in a BufReadPre auto command, it
> > does not take effect in readfile(). (Gary Johnson)
> > Solution: Ch
Christian Brabandt wrote:
> > Hi Bram!
> >
> > On Mo, 23 Jan 2017, Bram Moolenaar wrote:
> >
> > > + func Test_fileformat_autocommand()
> > > + let filecnt=['', 'foobar', 'eins', '', 'zwei', 'drei', 'vier',
> > > 'fünf', '']
> >
> > That looks wrong. The first five items should have
> Hi Bram!
>
> On Mo, 23 Jan 2017, Bram Moolenaar wrote:
>
> > + func Test_fileformat_autocommand()
> > + let filecnt=['', 'foobar', 'eins', '', 'zwei', 'drei', 'vier', 'fünf',
> > '']
>
> That looks wrong. The first five items should have an explicit CR '^M'
> inside it. Did this test
Hi Dominique!
On Di, 24 Jan 2017, Dominique Pellé wrote:
> > Running tests with vim-8.0.225 built with asan, I see the
> > following crash (head-buffer-overflow). Since I see fileio.c
> > in the stack, I assume that the bug is caused by patch 8.0.224:
Could it be, that this happens because of
Hi Bram!
On Mo, 23 Jan 2017, Bram Moolenaar wrote:
> + func Test_fileformat_autocommand()
> + let filecnt=['', 'foobar', 'eins', '', 'zwei', 'drei', 'vier', 'fünf',
> '']
That looks wrong. The first five items should have an explicit CR '^M'
inside it. Did this test actually fail before
Dominique Pellé <dominique.pe...@gmail.com> wrote:
> Bram Moolenaar <b...@moolenaar.net> wrote:
>
>> Patch 8.0.0224
>> Problem:When 'fileformats' is changed in a BufReadPre auto command, it
>> does not take effect in readfile(). (Gary Joh
Bram Moolenaar <b...@moolenaar.net> wrote:
> Patch 8.0.0224
> Problem:When 'fileformats' is changed in a BufReadPre auto command, it
> does not take effect in readfile(). (Gary Johnson)
> Solution: Check the value of 'fileformats' after execu
Patch 8.0.0224
Problem:When 'fileformats' is changed in a BufReadPre auto command, it
does not take effect in readfile(). (Gary Johnson)
Solution: Check the value of 'fileformats' after executing auto commands.
(Christian Brabandt)
Files: src/fileio.c, src
20 matches
Mail list logo