On Mon, Mar 20, 2017 at 05:42:44PM -0700, Yegappan Lakshmanan wrote:
> On Mon, Mar 20, 2017 at 4:46 PM, James McCoy wrote:
> > Why keep shoe-horning things into the set{qf,loc}list functions? This
> > just makes it an awkward API to use.
> >
> > I would suggest alternatives of
> >
> > qflistdel
Hi James,
On Mon, Mar 20, 2017 at 4:46 PM, James McCoy wrote:
> On Mon, Mar 20, 2017 at 08:26:27AM -0700, Yegappan Lakshmanan wrote:
>> Hi all,
>>
>> When developing additional tests for the quickfix functionality,
>> I found that some part of the code checks whether the quickfix
>> or location l
On Mon, Mar 20, 2017 at 08:26:27AM -0700, Yegappan Lakshmanan wrote:
> Hi all,
>
> When developing additional tests for the quickfix functionality,
> I found that some part of the code checks whether the quickfix
> or location list stack is empty. To test for these conditions, we
> need a function
I wrote:
> Kazunobu Kuriyama wrote:
>
> > 2017-03-20 5:24 GMT+09:00 Bram Moolenaar :
> >
> > >
> > > Please note that I changed the client-server test to use timeouts,
> > > instead oa a timer with an abort. The main reason is that if the abort
> > > kicks in there is no way to rerun the test,
Hi Bram,
On Mon, Mar 20, 2017 at 1:47 PM, Bram Moolenaar wrote:
>
> Yegappan wrote:
>
>> When developing additional tests for the quickfix functionality,
>> I found that some part of the code checks whether the quickfix
>> or location list stack is empty. To test for these conditions, we
>> need
Kazunobu Kuriyama wrote:
> 2017-03-20 5:24 GMT+09:00 Bram Moolenaar :
>
> >
> > Please note that I changed the client-server test to use timeouts,
> > instead oa a timer with an abort. The main reason is that if the abort
> > kicks in there is no way to rerun the test, thus adding it to the lis
Yegappan wrote:
> When developing additional tests for the quickfix functionality,
> I found that some part of the code checks whether the quickfix
> or location list stack is empty. To test for these conditions, we
> need a function to delete the quickfix and location list stacks.
>
> What abou
Christian Brabandt wrote:
> Hi,
> is this supposed to work or not?
>
> let a='foobar'
> let c={}
> let c.{a} = 10
>
> Currently this gives E713: Cannot use empty key for Dictionary
>
> However reading :h curly-braces-
Patch 8.0.0495
Problem:The quotestar test uses a timer instead of a timeout, thus it
cannot be rerun like a flaky test.
Solution: Remove the timer and add a timeout. (Kazunobu Kuriyama)
Files: src/testdir/test_quotestar.vim
*** ../vim-8.0.0494/src/testdir/test_quotestar.vi
2017-03-20 16:29 GMT+03:00 Christian Brabandt :
> Hi,
> is this supposed to work or not?
>
> let a='foobar'
> let c={}
> let c.{a} = 10
>
> Currently this gives E713: Cannot use empty key for Dictionary
>
> However reading :h curly-braces-names makes it sound like it should
> work?
No, it should n
Hi all,
When developing additional tests for the quickfix functionality,
I found that some part of the code checks whether the quickfix
or location list stack is empty. To test for these conditions, we
need a function to delete the quickfix and location list stacks.
What about extending the setqf
2017-03-20 5:24 GMT+09:00 Bram Moolenaar :
>
> Please note that I changed the client-server test to use timeouts,
> instead oa a timer with an abort. The main reason is that if the abort
> kicks in there is no way to rerun the test, thus adding it to the list
> of flaky tests has no effect.
>
> I
Hi,
is this supposed to work or not?
let a='foobar'
let c={}
let c.{a} = 10
Currently this gives E713: Cannot use empty key for Dictionary
However reading :h curly-braces-names makes it sound like it should
work?
Best
hmmm...
The issue is not resolved after all. It still happens, but much more rarely. If
I manage to reliably reproduce it I will let you know. I will probably open a
ticket on awesome too.
thanks for the help anyway :)
all the best
Panos
--
--
You received this message from the "vim_dev" m
14 matches
Mail list logo
