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 ru
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?
If you really care about case, you can use \c and \C to specify case
inside the pattern.
On 5/5/06, NEANG Vissale <[EMAIL PROTECTED]> wrote:
It seems that the substitute() function depends on the user ignorecase setting
but there is no indication about this in the help. The help says also the
A couple of doc patches I forgot to include:
*** autocmd.txtFri May 5 14:37:12 2006
--- autocmd.txt.newFri May 5 14:37:24 2006
***
*** 795,800
--- 795,811
WinLeave autocommands (but not for ":new").
Not used for ":qa" or ":q" wh
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 hacking the statusline for a long time to do various things
> a keystroke at a time. I
One more try, got a mailer daemon error.
On 5/6/06, Eric Arnold <[EMAIL PROTECTED]> wrote:
Thanks. It works great when entering existing tabs, but there is still
something odd when a tab is entered via "tabnew". I am able to open a new
window in the new tab, but I end up
On 5/6/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Suresh Govindachar wrote:
> Please consider supporting expressions for syntax matching.
> An example of usage is indicated below:
I don't quite get it. ":syn match" commands use a pattern. You can use
":exec" to get the pattern from an
On 5/6/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Eric Arnold wrote:
One more try, got a mailer daemon error.
> On 5/6/06, Eric Arnold <[EMAIL PROTECTED]> wrote:
> > Thanks. It works great when entering existing tabs, but there is still
> > something odd when a
I'm pretty rusty, but I've run into something that I don't understand.
for( str = vimvars[VV_GETCHARTYPE].vv_str; *str != NUL ; str++ )
*str = tolower( *str );
In gdb, it tells me "cannot access memory at address " whenever I
try to set to *str.
The memory at
vimvars[VV_GETCH
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.or
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 event
from typeahead buffer for processing ?, or
yes
b) only when getchar() is in
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 point
>
> Can I assign to v:getchar a string like "\" ?
Yes
Assuming it is translated to a 3 byte func key string in the context you use it,
How do I get the key name, i.e. 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 strtrans() retu
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-dev@vim.org
How do I get the key name, i.e. from th
On 5/8/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Eric Arnold wrote:
> How do I get the key name, i.e. 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 m
Here's another version with a check for obscure cases where a bad key
string is given.
charset.c.patch
Description: Binary data
I was wondering if anybody has thought about having an unsupported
version of Vim which has various enhancements and patches that aren't
yet approved for the official version of Vim?
I was thinking this would be a way of getting stability and testing
feedback within the Vim-dev community or whoev
It wasn't handling certain keys. This works now:
echo
strtrans("\,\,\,\,\\")
charset.c.patch
Description: Binary data
Yes, I'll be doing that. However, I was thinking of having a
deliverable version of the R&D stuff for those who would be interested
in trying things out, but don't have a compile env.
On 5/12/06, Yakov Lerner <[EMAIL PROTECTED]> wrote:
On 5/12/06, Eric Arnold <[EMAIL PRO
option?
Since there currently isn't a clean way of doing this in Vim, is seems
like 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("\,\,\,\,\\ -notake
;"'
" Output:
"
"
" raw=<03><1b>€ü<06><0d>,€kB,€ü<04> ,€ü<04>€ý<04>,€ü&€ý,
" trans=<03><1b>€ü<06><0d>,€kB,€ü<04> ,€ü<04>€ý<04>,€ü&€ý,
" trans
l=
" trans
e=\
On 5/12/06, Steve Hall <[EMAIL PROTECTED]> wrote:
From: Eric Arnold, May 12, 2006 7:51 AM
>
> I was wondering if anybody has thought about having an unsupported
> version of Vim which has various enhancements and patches that
> aren't yet approved for the official version
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.
:se
I'm wondering if there were any error messages prior to the ones you
included, especially ones complaining about not finding perl
directories or .h files. It looks like it might be failing in the
pass where it runs perl on if_perl.xs. It seems to be most concerned
about finding ExtUtils in this
On 5/13/06, Georg Dahn <[EMAIL PROTECTED]> wrote:
Hi!
> I'm wondering if there were any error messages prior to the ones you
> included, especially ones complaining about not finding perl
> directories or .h files. It looks like it might be failing in the
> pass where it runs perl on if_perl.xs
ld Vim with Perl support. I will fiddle around with this. What seems
so strange to me, is, that I could build Vim 6.4 with Perl support and
the same settings, but with an older version of ActivePerl.
Best wishes and many thanks for your help!
Georg
Eric Arnold schrieb:
> On 5/13/06, Georg Dah
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 rea
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 p
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
he
reaonly property several ways for files actually loaded into buffers.
On 5/24/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> -Original Message-
> From: Eric Arnold [mailto:[EMAIL PROTECTED]
> Sent: 24 May 2006 11:21
> To: Zdenek Sekera
> Cc: Yakov Lerner; vim
On 5/24/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> -Original Message-
> From: Eric Arnold [mailto:[EMAIL PROTECTED]
> Sent: 24 May 2006 12:38
> To: Zdenek Sekera
> Cc: vim-dev@vim.org
> Subject: Re: set readonly - strange?
>
> I think 'readonly'
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'l
Try expanding it.
au SourcePre *.vim echomsg "afile=" . expand("")
au SourcePre *.vim let g:sfile =
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 nut I
On 5/26/06, Eric Arnold <[EMAIL PROTECTED]> wrote:
Try expanding it.
au SourcePre *.vim echomsg "afile=" . expand("")
au SourcePre *.vim let @a =
au SourcePre *.vim let @a = expand("" )
On 5/26/06, Zdenek Sekera <[EMAIL PROTECTED]> wrote:
> I&
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
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,
sett
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 se
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 wh
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, Mark
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 s
WinWalker.vim is also using 'mksession'. You can certainly use it
from a regular mapping. The main advantage from using the call
supported from within the script is that additional settings useful
for WinWalker are saved in a ...x.vim session compliment file (i.e. it
saves information about wind
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 n1 = tm_delta.HighPar
;[EMAIL PROTECTED]> wrote:
(Moving the non-developer list to BCC.)
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, High
On 6/14/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Eric Arnold wrote:
> What should be returned by the reltime() call? If Vim script only
> handles "int" types, the values returned are apparently inconsisent.
> Am I missing something, or is reltime() on windows cu
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 i
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 on
Here is a snapshot of how I'm using tabline wrapping:
http://www.geocities.com/eric_p_arnold/tabline_wrap_eg.html
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/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 )
&g
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 fo
52 matches
Mail list logo
