[...]
> >
>
> The floating point patch is really bloating Vim. This "feature" was not
> asked
> by many people before this. Some of the features like running a shell
> inside Vim were requested many times before and were rejected with
> a reasoning that they will un-necessarily bloat Vim.
>
Yes,
When 'sessionoptions' contains 'globals', a regular variable, say
"Font", gets saved fine. But something like "Globals.font" does not.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/mailli
On 23-Jun-08 14:46, Ron wrote:
> When 'sessionoptions' contains 'globals', a regular variable, say
> "Font", gets saved fine. But something like "Globals.font" does not.
I think this is by design; :help 'sessionoptions' mentions:
globals global variables that start with an upperc
On 20-Jun-08 18:34, Ingo Karkat wrote:
> On 20-Jun-08 17:59, Ben Fritz wrote:
>> I have a script that creates files like this:
>>
>> file.ext -> file.ext.ann_out.ext
>>
>> I don't want to see these files when I do filename completion, because
>> they clutter up my wildmenu. For this reason, I put:
Hello you guys-making-the-most-useful-tool-in-VR (of course I am not
speaking only of myself),
proud to have found a little thing that, be fixed, would improve the
improved vi even a nearly unsubstantial-tiny bit more:
If you use syntax highlighting, and programm shell scripts, then there
is
Bill McCarthy wrote:
> Ben, Bram & Tony,
>
> I sent the following to the list yesterday, but forgot to
> copy you - the recipients of the initial draft of this
> function. I've enhanced it by making it more customizable -
> something the default fp output should be.
The original still hasn't app
On 23/06/08 18:19, Ben Schmidt wrote:
> Bill McCarthy wrote:
>> Ben, Bram & Tony,
>>
>> I sent the following to the list yesterday, but forgot to
>> copy you - the recipients of the initial draft of this
>> function. I've enhanced it by making it more customizable -
>> something the default fp out
> Nobody has commented yet; are there any opinions? Bram?
Bram did comment. He's added it to his to do list (don't know whether an
updated version of that has hit ftp yet, though).
Ben.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist
Ben Schmidt wrote:
>> Nobody has commented yet; are there any opinions? Bram?
>
> Bram did comment. He's added it to his to do list (don't know whether an
> updated version of that has hit ftp yet, though).
Actually, I might be wrong about that...I thought he did, but I can't
spot the post in t
While working on the Float printing function, I also noted an odd Vim
behaviour: it won't let you assign a Float to a variable that was
previously a Number, and vice-versa. Or for that matter, it won't let
you change the type of a variable at all with an assignment.
The trouble is in the set_var()
Tony Mechelynck wrote:
> On 21/06/08 09:17, Matt Tolton wrote:
>>> see ":help exception-handling"
>> I scanned that and I'm not seeing how it helps me...it's all talking
>> about vimscript. Could you please elaborate?
>>
>> Thanks,
>>
>> Matt
>
> So? I thought you were writing a Vim function.
N
On Mon, Jun 23, 2008 at 18:31, Ben Schmidt
<[EMAIL PROTECTED]> wrote:
> Actually, I might be wrong about that...I thought he did, but I can't
> spot the post in the archives now, so maybe I am going crazy!
He did:
On Fri, Jun 20, 2008 at 18:51, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> I can r
Hi, Bram,
Another oddity I've recently discovered is that str2nr won't accept an
explicitly
positive number, such as '+3'.
This is unexpected. Would you be willing to adjust the behaviour? I can't think
of
any negative/compatibility-breaking side effects this would have, but I also
don't
kn
On 23 Jun 2008, at 18:28, Ben Schmidt wrote:
> diff -r 64942db7407d src/charset.c
> --- a/src/charset.c Sat Jun 21 23:24:54 2008 +1000
> +++ b/src/charset.c Tue Jun 24 03:24:33 2008 +1000
> @@ -1799,6 +1799,7 @@
> unsigned long un = 0;
> int n;
>
> +if (ptr[0] =
On Mon, Jun 23, 2008 at 06:30:58PM +0100, Andy Armstrong wrote:
>> diff -r 64942db7407d src/charset.c
>> --- a/src/charset.c Sat Jun 21 23:24:54 2008 +1000
>> +++ b/src/charset.c Tue Jun 24 03:24:33 2008 +1000
>> @@ -1799,6 +1799,7 @@
>> unsigned long un = 0;
>> int n;
On 23/06/08 18:40, Ben Schmidt wrote:
> While working on the Float printing function, I also noted an odd Vim
> behaviour: it won't let you assign a Float to a variable that was
> previously a Number, and vice-versa. Or for that matter, it won't let
> you change the type of a variable at all with
On 23 Jun 2008, at 18:34, Gautam Iyer wrote:
>> Doesn't that allow '+-3' ?
>
> This seems to go unnoticed in some other languages too (e.g. Python).
I assume that's because they support unary '+' as an operator. It's
not part of the numeric constant:
>>> print +(1+2)
3
>>> print ++(1+2)
Mikael Jansson wrote:
> Hi,
>
> I'm not very familiar with the Vim code base, so I couldn't quite find
> my way around, so I'm asking here instead:
>
> Will the range for % (the entire file) always be 1 for line1 and
> number-of-lines-in-file for line2?
Yes.
:tag do_one_cmd | /%
There is a co
On 23/06/08 19:28, Ben Schmidt wrote:
> Hi, Bram,
>
> Another oddity I've recently discovered is that str2nr won't accept an
> explicitly
> positive number, such as '+3'.
>
> This is unexpected. Would you be willing to adjust the behaviour? I can't
> think of
> any negative/compatibility-breakin
On Mon, Jun 23, 2008 at 8:28 PM, Ben Schmidt <[EMAIL PROTECTED]>
wrote:
> Hi, Bram,
>
> Another oddity I've recently discovered is that str2nr won't accept an
> explicitly
> positive number, such as '+3'.
>
> This is unexpected. Would you be willing to adjust the behaviour? I can't
> think of
> an
On 23/06/08 19:37, Andy Armstrong wrote:
> On 23 Jun 2008, at 18:34, Gautam Iyer wrote:
>>> Doesn't that allow '+-3' ?
>> This seems to go unnoticed in some other languages too (e.g. Python).
>
>
> I assume that's because they support unary '+' as an operator. It's
> not part of the numeric consta
Andy Armstrong wrote:
> On 23 Jun 2008, at 18:28, Ben Schmidt wrote:
>> diff -r 64942db7407d src/charset.c
>> --- a/src/charset.c Sat Jun 21 23:24:54 2008 +1000
>> +++ b/src/charset.c Tue Jun 24 03:24:33 2008 +1000
>> @@ -1799,6 +1799,7 @@
>> unsigned long un = 0;
>> int
Tony Mechelynck wrote:
> On 23/06/08 19:28, Ben Schmidt wrote:
>> Hi, Bram,
>>
>> Another oddity I've recently discovered is that str2nr won't accept an
>> explicitly
>> positive number, such as '+3'.
>>
>> This is unexpected. Would you be willing to adjust the behaviour? I can't
>> think of
>>
On 23-Jun-08 18:58, François Ingelrest wrote:
> On Mon, Jun 23, 2008 at 18:31, Ben Schmidt
> <[EMAIL PROTECTED]> wrote:
>> Actually, I might be wrong about that...I thought he did, but I can't
>> spot the post in the archives now, so maybe I am going crazy!
>
> He did:
>
> On Fri, Jun 20, 2008 a
Tony Mechelynck wrote:
> On 23/06/08 18:40, Ben Schmidt wrote:
>> While working on the Float printing function, I also noted an odd Vim
>> behaviour: it won't let you assign a Float to a variable that was
>> previously a Number, and vice-versa. Or for that matter, it won't let
>> you change the ty
Bram Moolenaar wrote:
> Chris Sutcliffe wrote:
>> There is a small issue with this patch:
>>
>>> *** ../vim-7.1.327/src/os_unix.cFri Jun 20 11:58:27 2008
>>> --- src/os_unix.c Sat Jun 21 13:06:45 2008
>>> ***
>>> *** 2278,2283
>>> --- 2278,2287
>>> char_u
On 2008-06-24, Ben Schmidt <[EMAIL PROTECTED]> wrote:
> Bram Moolenaar wrote:
> > Chris Sutcliffe wrote:
> >> There is a small issue with this patch:
> >>
> >>> *** ../vim-7.1.327/src/os_unix.cFri Jun 20 11:58:27 2008
> >>> --- src/os_unix.c Sat Jun 21 13:06:45 2008
> >>> ***
Gary Johnson wrote:
> On 2008-06-24, Ben Schmidt <[EMAIL PROTECTED]> wrote:
>> Bram Moolenaar wrote:
>>> Chris Sutcliffe wrote:
There is a small issue with this patch:
> *** ../vim-7.1.327/src/os_unix.cFri Jun 20 11:58:27 2008
> --- src/os_unix.c Sat Jun 21 13:06:45
On Tue 17 Jun 2008 at 10:44:50 -0400, James Vega wrote:
> I have to agree with Chip here that the upstream version should default
> to Bourne as that is most likely to cause people to actually configure
> the highlighting to work properly for the variant of /bin/sh that *they*
> are using.
But th
On 23/06/08 19:48, Ben Schmidt wrote:
> Mikael Jansson wrote:
>> Hi,
>>
>> I'm not very familiar with the Vim code base, so I couldn't quite find
>> my way around, so I'm asking here instead:
>>
>> Will the range for % (the entire file) always be 1 for line1 and
>> number-of-lines-in-file for line
On Mon, Jun 23, 2008 at 09:47:15PM +0200, Rhialto wrote:
>
> On Tue 17 Jun 2008 at 10:44:50 -0400, James Vega wrote:
> > I have to agree with Chip here that the upstream version should default
> > to Bourne as that is most likely to cause people to actually configure
> > the highlighting to work p
Vim is leaking memory when doing 'set keymap='
You can reproduce the memory leak by running the
following script and observe memory usage (with 'top')
which keeps increasing continuously:
:while 1
: set keymap=esperanto
: set keymap=
:endwhile
The leak happens regardless of the keymap,
It seems that the latest doc/help txt contains spurious lines.
I suggest the attached patch.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
18. Your wife drapes a blond wig over your monitor to remind you of what she
looks like.
--~--~-~--~~--
Ben Schmidt wrote:
> While working on the Float printing function, I also noted an odd Vim
> behaviour: it won't let you assign a Float to a variable that was
> previously a Number, and vice-versa. Or for that matter, it won't let
> you change the type of a variable at all with an assignment.
>
Ben Schmidt wrote:
> Another oddity I've recently discovered is that str2nr won't accept an
> explicitly positive number, such as '+3'.
>
> This is unexpected. Would you be willing to adjust the behaviour? I
> can't think of any negative/compatibility-breaking side effects this
> would have, bu
Bill McCarthy wrote:
> On Sun 22-Jun-08 2:49pm -0600, Tony Mechelynck wrote:
>
> > On 21/06/08 13:56, Bram Moolenaar wrote:
>
> >> Ben Schmidt wrote:
>
> >>> - Furthermore, on investigation, it seems there is an interesting
> >>> definition of 'significant figures' in the library docs, an
On Mon 23 Jun 2008 at 16:14:51 -0400, James Vega wrote:
> On Mon, Jun 23, 2008 at 09:47:15PM +0200, Rhialto wrote:
> >
> > On Tue 17 Jun 2008 at 10:44:50 -0400, James Vega wrote:
> > > I have to agree with Chip here that the upstream version should default
> > > to Bourne as that is most likely t
On Mon, Jun 23, 2008 at 10:47 PM, Rhialto <[EMAIL PROTECTED]> wrote:
> On Mon 23 Jun 2008 at 16:14:51 -0400, James Vega wrote:
>> On Mon, Jun 23, 2008 at 09:47:15PM +0200, Rhialto wrote:
>> >
>> > On Tue 17 Jun 2008 at 10:44:50 -0400, James Vega wrote:
>> > > I have to agree with Chip here that t
Dominique Pelle wrote:
> Vim is leaking memory when doing 'set keymap='
>
> You can reproduce the memory leak by running the
> following script and observe memory usage (with 'top')
> which keeps increasing continuously:
>
> :while 1
> : set keymap=esperanto
> : set keymap=
> :endwhi
Tony Mechelynck wrote:
> It seems that the latest doc/help txt contains spurious lines.
>
> I suggest the attached patch.
Thanks. I usually check for that when making a new release, not often
in between.
--
hundred-and-one symptoms of being an internet addict:
87. Everyone you know asks why
Bram Moolenaar wrote:
>
> Ben Schmidt wrote:
>
>> Another oddity I've recently discovered is that str2nr won't accept an
>> explicitly positive number, such as '+3'.
>>
>> This is unexpected. Would you be willing to adjust the behaviour? I
>> can't think of any negative/compatibility-breaking si
Ben Schmidt wrote:
> Bram Moolenaar wrote:
>> Ben Schmidt wrote:
>>
>>> Another oddity I've recently discovered is that str2nr won't accept an
>>> explicitly positive number, such as '+3'.
>>>
>>> This is unexpected. Would you be willing to adjust the behaviour? I
>>> can't think of any negative/c
Bram Moolenaar wrote:
> Ben Schmidt wrote:
>> While working on the Float printing function, I also noted an odd Vim
>> behaviour: it won't let you assign a Float to a variable that was
>> previously a Number, and vice-versa. Or for that matter, it won't let
>> you change the type of a variable at
On 24/06/08 05:02, Ben Schmidt wrote:
> Bram Moolenaar wrote:
>> Ben Schmidt wrote:
>>> While working on the Float printing function, I also noted an odd Vim
>>> behaviour: it won't let you assign a Float to a variable that was
>>> previously a Number, and vice-versa. Or for that matter, it won't
>>> It's called sticky type checking. Not everybody likes it, but that's
>>> the way it is.
>> I guess it has analogies with languages such as C that use static
>> typing.
>>
>> But does it actually have any benefit in Vim script? I can't think of
>> one. I mean, do people actually see this error
On Mon 23-Jun-08 11:19am -0600, Ben Schmidt wrote:
You gave the following example from my missing email:
> :" Inaccurate due to underflow
> :echo PG(1.0e-323)
> 9.88131291682e-324
> :" Negative zero incorrect
> :echo PG(-0.0)
> 0
> :" Too many digits
> :ech
On Mon 23-Jun-08 3:33pm -0600, Bram Moolenaar wrote:
> I get the feeling we are splitting hairs here. Anyway, current Vim does
> like the above. Except:
>
> :echo PG(-0.00123)
> -1.23e-3
>
> I would prefer to see -0.00123, as Vim does now.
You can now control the number of zeros you
Hi,
I'm here to report a bug, i'll try to give as much information as i can
think of, but i'm available to give more information about my
version/platform.
My platform :
Ubuntu 8.04 Hardy i386
I filled in the :source $VIMRUNTIME/bugreport.vim and i generated this
file :
http://thibault.tailla
48 matches
Mail list logo
