Richard Emberson wrote:
In the following I am creating a dictionary, associating a function
with the dictionary and then reassociating a new function
with the name of the original function.
Try this without the fix and you get:
ADD
n=9
Error detected while processing
Eric Arnold wrote:
When compiled with this patch, Vim will allow the strings delivered
via the 'tabline' option to wrap onto new lines. It is up to the
'tabline' string or function to limit itself. See TabLineSet.vim for
an example of a script which does this.
The default behavior, ie.
On 6/15/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Eric Arnold wrote:
When compiled with this patch, Vim will allow the strings delivered
via the 'tabline' option to wrap onto new lines. It is up to the
'tabline' string or function to limit itself. See TabLineSet.vim for
an example of
Attached is a patch file. Is this what you wanted?
Its been almost 20 years since I programmed in 'c'
and the vim 'c' code is rather hard to grok if one
is looking at it for the first time, so I do not
claim that my patch is the best way to do it.
It seems that after the function is defined, it
I think Bram was asking you to use diff -c or diff -u to create
the patch file.
On 6/15/06, Richard Emberson [EMAIL PROTECTED] wrote:
Attached is a patch file. Is this what you wanted?
Its been almost 20 years since I programmed in 'c'
and the vim 'c' code is rather hard to grok if one
is
Bram Moolenaar wrote:
In my opinion the tabline should be one line. When it wraps the UI
looks ugly. Esp. if the currently selected tab page is in the first
line.
Maybe if lines would swap, so that line with selected tab would alway be
the lowest one it would look nicer?
Richard Emberson wrote:
The attached file was produced with diff -c eval.c eval.c.original.
That's easier to understand, thanks.
--
hundred-and-one symptoms of being an internet addict:
246. You use up your free 100 hours in less than a week.
/// Bram Moolenaar -- [EMAIL PROTECTED] --
