On 7/2/06, Mikolaj Machowski [EMAIL PROTECTED] wrote:
Dnia niedziela, 2 lipca 2006 12:06, Nikolai Weibull napisał:
On 7/1/06, justin constantino [EMAIL PROTECTED] wrote:
E706: Variable type mismatch
As a minor improvement, I think it would be nice if you could do:
let foo =
On 6/21/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Eric Arnold wrote:
I've added a v:variable which is a dict type. When I set it in a
script, and echo it, everything is fine:
let v:timertable[ 'TstTimer' ] = 1000
echo string( v:timertable )
However, it is trashed (garbage in the hash
I've added a v:variable which is a dict type. When I set it in a
script, and echo it, everything is fine:
let v:timertable[ 'TstTimer' ] = 1000
echo string( v:timertable )
However, it is trashed (garbage in the hash table) by the next time I
access it later in the Vim C code.
Can anybody give
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
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
.)
Eric Arnold wrote:
I'm trying to understand what I'm seeing with the msec timing on win32
(cygwin). Inside the debugger, I'm seeing:
(gdb) p tm_delta
$1 = {u = {LowPart = 2434313347, HighPart = 896}, {LowPart = 2434313347,
HighPart = 896}, QuadPart = 3850725010563}
(gdb) n
180
I found that the contents of a particular ordinal tab number was too
fluid to be of much use to me, so I concentrated on making relative
navigation easier, but I could be alone in that.
The way it stands, you can make a macro sequence from inside the script using:
{m}isc menu - {ma}cro keys
On 6/9/06, Ilya [EMAIL PROTECTED] wrote:
Eric Arnold wrote:
I found that the contents of a particular ordinal tab number was too
fluid to be of much use to me, so I concentrated on making relative
navigation easier, but I could be alone in that.
The way it stands, you can make a macro
I wrote the WinWalker.vim script partly with this sort of thing in
mind. Combining window layouts with sessions and macro keys (both
supported from inside the plugin), and Vim7 tabs should do what I
think you mean.
http://vim.sourceforge.net/scripts/script.php?script_id=1522
On 6/8/06,
It appears that the first key of any incremental search to a point far
enough down in the file (i.e. a page below the displayed area) will
cause it. Typing any additional key brings the tabline back.
I fiddled around with TabLineSet.vim, but it appears that the bug is
in the code that decides
I'm making a function which moves the mouse pointer using
gui_mch_setmouse( x, y );
It does set the mouse pointer correctly, but I also end up with a
second pointer, which is maintained at the last position, that I can't
find out how to get rid of. Changing the hide setting, redrawing,
Blah. I spent two days looking for this, and it was the mouse
driver's pointer trails option malfunctioning. :-(
On 5/30/06, Eric Arnold [EMAIL PROTECTED] wrote:
I'm making a function which moves the mouse pointer using
gui_mch_setmouse( x, y );
It does set the mouse pointer correctly
Try expanding it.
au SourcePre *.vim echomsg afile= . expand(afile)
au SourcePre *.vim let g:sfile = afile
On 5/26/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
I'd like to before :sourc'ing a file to execute
one of my scripts (always the same).
I though the autocmd 'SourcePre' event will
help
On 5/26/06, Eric Arnold [EMAIL PROTECTED] wrote:
Try expanding it.
au SourcePre *.vim echomsg afile= . expand(afile)
au SourcePre *.vim let @a = afile
au SourcePre *.vim let @a = expand(afile )
On 5/26/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
I'd like to before :sourc'ing a file
On 5/26/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
-Original Message-
From: Charles E Campbell Jr [mailto:[EMAIL PROTECTED]
Sent: 26 May 2006 16:19
To: Zdenek Sekera
Cc: vim-dev@vim.org
Subject: Re: source, runtime and all that
Zdenek Sekera wrote:
I also thought 'runtime' is
On 5/24/06, Zdenek Sekera [EMAIL PROTECTED] wrote:
-Original Message-
From: Eric Arnold [mailto:[EMAIL PROTECTED]
Sent: 23 May 2006 18:12
To: Yakov Lerner
Cc: Zdenek Sekera; vim-dev@vim.org
Subject: Re: set readonly - strange?
As far as I can tell, there are several instances
On 5/24/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 5/24/06, Eric Arnold [EMAIL PROTECTED] wrote:
I think 'readonly' does not belong in the .vimrc since it is a
buffer-local-only option.
If you try to set any other buffer-local option in .vimrc,
you'll see that it works just fine.
I tried
I wouldn't expect that to work. There is no defined loaded buffer
when the -u vimrc is run. 'readonly' is local to buffers only, so in
your example, it has no buffer to be applied to.
If you want everything to be readonly, try setting a BufEnter autocommand.
If you want just one file to be
As far as I can tell, there are several instances where there are
transitory buffers as vim is starting, opening a new tab, probably
some in closing op.s.
I don't know if I used the right word by saying the buffer is
undefined, but I don't think it it's guaranteed to be usable until a
certain
belongs somewhere.
On 5/12/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Eric Arnold wrote:
It wasn't handling certain keys. This works now:
echo strtrans(\c-s-cr,\s-tab,\c-space,\c-s-up,\c-s-2leftmouse\c=
-notakey)
That already worked. You apparently have wrong expectations of what
strtrans
-CEscC-S-CR,S-Tab,C-Space,C-S-Up,C-S-2-LeftMousec-notakey
trans
e=\C-C\Esc\C-S-CR,\S-Tab,\C-Space,\C-S-Up,\C-S-2-LeftMousec-notakey
raw2=031b€ü060d,€kB,€ü04 ,€ü04€ý04,€ü€ý,c-notakey
On 5/12/06, Eric Arnold [EMAIL PROTECTED] wrote:
The doc page really only talks about regular control chars
I've uploaded a new version to the sourceforge script area. It now
can read and react to the text in the statusline and tabline as it
appears on the screen.
On 5/12/06, Eric Arnold [EMAIL PROTECTED] wrote:
Here is my first working version of a mouse function option, i.e.
:set mousefunc
How do I get the key name, i.e. leftmouse from the 3 byte keycode
returned by getchar()?
strtrans() doesn't seem to deal with these.
^Qkey does this, but I was looking for a functional method.
Let me know if I've missed something, otherwise please consider the
following patch to make
I think the mailer daemon may have bounced this.
-- Forwarded message --
From: Eric Arnold [EMAIL PROTECTED]
Date: May 8, 2006 1:06 AM
Subject: get key name from keycode
To: vim.org user list vim@vim.org, vim-dev@vim.org
How do I get the key name, i.e. leftmouse from the 3 byte
On 5/6/06, Mikolaj Machowski [EMAIL PROTECTED] wrote:
Dnia sobota, 6 maja 2006 00:01, Eric Arnold napisał:
On 5/5/06, Mikolaj Machowski [EMAIL PROTECTED] wrote:
Dnia piątek, 5 maja 2006 14:35, Eric Arnold napisał:
I think vim-dev@vim.org is probably a place to start...
I've been
On 5/7/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 5/7/06, Eric Arnold [EMAIL PROTECTED] wrote:
On 5/7/06, Yakov Lerner [EMAIL PROTECTED] wrote:
On 5/7/06, Eric Arnold [EMAIL PROTECTED] wrote:
Can you clarify coulpe of points.
1.
a) Is this event fired when getchar() or vim extract
Can I assign to v:getchar a string like \F1 ?
Yes
Assuming it is translated to a 3 byte func key string in the context you use it,
I don't know if it's supported to do this, but I'm crashing VIm70g,
WinXP by doing a new in a TabEnter autocommand. The crash doesn't
immediately follow the new command, but soon after when other
functions start looking through the windows.
I can't get a crash in a test case, but if you run the
BTW, I can't get WinDbg to recognize the .pdb files, although I've set
the Symbol path to the directory containing them. Is there some trick
to this?
29 matches
Mail list logo
