Re: Has remove() always thrown an error if idx is beyond the end of list?

2008-10-22 Fir de Conversatie Doug Kearns
Nikolai, On 10/21/08, Nikolai Weibull [EMAIL PROTECTED] 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. Ignoring the

Re: Has remove() always thrown an error if idx is beyond the end of list?

2008-10-22 Fir de Conversatie Nikolai Weibull
On Wed, Oct 22, 2008 at 13:19, Doug Kearns [EMAIL PROTECTED] wrote: On 10/21/08, Nikolai Weibull [EMAIL PROTECTED] 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,

Re: Has remove() always thrown an error if idx is beyond the end of list?

2008-10-22 Fir de Conversatie Tony Mechelynck
On 22/10/08 13:57, Nikolai Weibull wrote: [...] I really dislike this tendency computers have to not adhering to the mantra do as I mean, not as I say.[...] Well, nothing irks me more than when a stupid program tries to second-guess me and does something else than what I told it, on the

Gvim for Windows doesn't handle non-BMP characters when interchanging data with Windows OS

2008-10-22 Fir de Conversatie JiaYanwei
When interchanging data with Windows such as clipboard operation, gvim will convert the text into UCS-2 encoding, but different from UTF-16, UCS-2 can't encode non-BMP characters. For example, when paste a non-BMP character U+248BB from Windows clipboard, it will insert two separated

Re: Has remove() always thrown an error if idx is beyond the end of list?

2008-10-22 Fir de Conversatie Tony Mechelynck
On 22/10/08 16:25, James Vega wrote: On Wed, Oct 22, 2008 at 03:54:23PM +0200, Nikolai Weibull wrote: On Wed, Oct 22, 2008 at 15:16, Tony Mechelynck [EMAIL PROTECTED] wrote: On 22/10/08 13:57, Nikolai Weibull wrote: [...] I really dislike this tendency computers have to not adhering to

Re: Gvim for Windows doesn't handle non-BMP characters when interchanging data with Windows OS

2008-10-22 Fir de Conversatie Tony Mechelynck
On 22/10/08 15:55, JiaYanwei wrote: When interchanging data with Windows such as clipboard operation, gvim will convert the text into UCS-2 encoding, but different from UTF-16, UCS-2 can't encode non-BMP characters. For example, when paste a non-BMP character U+248BB from Windows clipboard,

Re: Has remove() always thrown an error if idx is beyond the end of list?

2008-10-22 Fir de Conversatie James Vega
On Wed, Oct 22, 2008 at 05:06:55PM +0200, Tony Mechelynck wrote: On 22/10/08 16:25, James Vega wrote: On Wed, Oct 22, 2008 at 03:54:23PM +0200, Nikolai Weibull wrote: On Wed, Oct 22, 2008 at 15:16, Tony Mechelynck [EMAIL PROTECTED] wrote: On 22/10/08 13:57, Nikolai Weibull wrote:

Re: Has remove() always thrown an error if idx is beyond the end of list?

2008-10-22 Fir de Conversatie Nikolai Weibull
On Wed, Oct 22, 2008 at 16:25, James Vega [EMAIL PROTECTED] wrote: On Wed, Oct 22, 2008 at 03:54:23PM +0200, Nikolai Weibull wrote: If I say remove(list, 8, -1) I expect it to give me a list of the first 8 elements in list. This is odd since, as pointed out earlier, Bram modelled the List

Re: Has remove() always thrown an error if idx is beyond the end of list?

2008-10-22 Fir de Conversatie Nikolai Weibull
On Wed, Oct 22, 2008 at 17:06, Tony Mechelynck [EMAIL PROTECTED] wrote: It has everything to do with syntax. What you're talking about is semantics. There's a difference. The documented syntax (at :help remove()) says if {end} is before {idx} it's an error. (Blurb condensed to the fact

Re: Has remove() always thrown an error if idx is beyond the end of list?

2008-10-22 Fir de Conversatie James Vega
On Wed, Oct 22, 2008 at 03:54:23PM +0200, Nikolai Weibull wrote: On Wed, Oct 22, 2008 at 15:16, Tony Mechelynck [EMAIL PROTECTED] wrote: On 22/10/08 13:57, Nikolai Weibull wrote: [...] I really dislike this tendency computers have to not adhering to the mantra do as I mean, not as I

Re: Gvim for Windows doesn't handle non-BMP characters when interchanging data with Windows OS

2008-10-22 Fir de Conversatie JiaYanwei
Hello Tony, It's really to be the similar problem, but this one only arise under Windows operating system, the UTF-16le BOM problem is platform independence. I was uncertain wherher a combined patch was convenient. On 2008-10-22 23:21:11, Tony Mechelynck wrote: I expect this is related with

Re:Re: Gvim for Windows doesn't handle non-BMP characters when interchanging data with Windows OS

2008-10-22 Fir de Conversatie JiaYanwei
Oh, I had made a mistake, I want to say They're really similar problems the first sentence. On 2008-10-23 00:16:20, JiaYanwei Hello Tony, It's really to be the similar problem, but this one only arise under Windows operating system, the UTF-16le BOM problem is platform independence. I was

Re: vim 7 ex-mode behavior

2008-10-22 Fir de Conversatie Gary Johnson
On 2008-10-23, d tbsky [EMAIL PROTECTED] wrote: hi: i have some old vim ex-mode scripts which can not work under vim 7.0 and 7.2. after some checking, i found command like below didn't work under vim 7: a 1 \\ 2 \\ . w q the command above can create two line 1\\ and 2\\ under

RE: vim 7 ex-mode behavior

2008-10-22 Fir de Conversatie John Beckett
d tbsky wrote: after some checking, i found command like below didn't work under vim 7: a 1 \\ 2 \\ . It works here on Vim 7.2 as well, although I had to use help to see how. Use ':help :a' and see what it says about Watch out for lines starting with a backslash. The above lines work,

Re: Gvim for Windows doesn't handle non-BMP characters when interchanging data with Windows OS

2008-10-22 Fir de Conversatie Tony Mechelynck
On 22/10/08 18:25, JiaYanwei wrote: **Oh, I had made a mistake, I want to say They're really similar problems the first sentence. On 2008-10-23 00:16:20, JiaYanwei Hello Tony, It's really to be the similar problem, but this one only arise under Windows operating system, the

Re: vim 7 ex-mode behavior

2008-10-22 Fir de Conversatie d tbsky
hi: i am sorry that i didn't describe the steps in detail. there are some old apps in our system which use ex in their scripts. and ex in link to vim in these system. so ex is like vim -e in the situation. vim 5 and vim 6 are fine for these scripts. but vim 7.0 and 7.2 is not. i found