Has remove() always thrown an error if idx is beyond the end of list?
Either way, what's the reasoning behind it doing so? If the items
aren't there to begin with, then great, that's precisely what I want.
The documentation should be updated to reflect this state of affairs.
Here's a patch:
On 21/10/08 13:53, Nikolai Weibull wrote:
Has remove() always thrown an error if idx is beyond the end of list?
Either way, what's the reasoning behind it doing so? If the items
aren't there to begin with, then great, that's precisely what I want.
The documentation should be updated to
On Tue, Oct 21, 2008 at 4:29 PM, Tony Mechelynck wrote:
On 21/10/08 13:53, Nikolai Weibull wrote:
Here's a patch:
Please apply your patches to the latest version of the file. In eval.txt
dated 2008 Sep 14, line, 4482 to 4489 are
...
within the help for remote_send(); IOW your pointer is 14
On Tue, Oct 21, 2008 at 22:29, Tony Mechelynck
[EMAIL PROTECTED] wrote:
On 21/10/08 13:53, Nikolai Weibull wrote:
Has remove() always thrown an error if idx is beyond the end of list?
Either way, what's the reasoning behind it doing so? If the items
aren't there to begin with, then great,
On 21/10/08 23:49, Matt Wozniski wrote:
On Tue, Oct 21, 2008 at 4:29 PM, Tony Mechelynck wrote:
On 21/10/08 13:53, Nikolai Weibull wrote:
Here's a patch:
Please apply your patches to the latest version of the file. In eval.txt
dated 2008 Sep 14, line, 4482 to 4489 are
...
within the help
Hi
The following vim script leaks memory at each iteration, using
latest Vim-7.2.25:
:set spell
:while 1
:copen
:bd
:endwhile
Run this script with 'vim -u NONE -S leak.vim' and watch memory
increasing steadily. Valgrind reports this leak:
$ valgrind
