-DFEAT_NETBEANS_INTG
-DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME
-DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -w -march=i386 -Wall -g -fstack-check
-mwindows -o gvimd.exe -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32
-lcomctl32 -lversion -lwsock32 -lole32 -luuid
--
Dasn
--
You received
-DFEAT_GUI_W32 -DFEAT_CLIPBOARD -DFEAT_MBYTE -DFEAT_MBYTE_IME
-DDYNAMIC_IME -DDYNAMIC_ICONV -pipe -w -march=i686 -Wall -g -fstack-check
-mwindows -o gvimd.exe -lkernel32 -luser32 -lgdi32 -ladvapi32 -lcomdlg32
-lcomctl32 -lversion -lwsock32 -lole32 -luuid
--
Dasn
--
You received
conditional. Stop.
--
Dasn
--
You received this message from the vim_dev maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
On Sat, 13 Mar 2010 10:42:47 +0800, Tony Mechelynck wrote:
On 13/03/10 02:05, Dasn wrote:
Hello guys.
I am using mingw32 to build vim on WinXP
D:\src\vim7\srcmake -v
GNU Make version 3.78.1, by Richard Stallman and Roland McGrath.
Built for Windows32
Copyright (C) 1988, 89, 90, 91, 92, 93
Sat, 15 Aug 2009 17:56:40 +0800，Sergey Vakulenko
it is possible disable switchbuf option?
when i set set switchbuf=, vim continue jumping to buffer.
Would you mind describing it (your problem) in more detail?
--
Dasn
--~--~-~--~~~---~--~~
You received
is , but vim will continue work like bufswitch is
useopen option.
There is no difference between and useopen option.
I find some strange things with these options too, when using :sb
command, (maybe I don't get idea of them), I'll try to collect them and
report it later.
--
Dasn
Hi guys,
When compiling Vim on obsd, the linker always complains:
objects/netbeans.o(.text+0x3f00): In function `coloncmd':
/home/dasn/pool/src/vim7/src/netbeans.c:2588: warning: vsprintf() is often
misused, please use vsnprintf()
/usr/local/lib/libpython2.6.so.1.0: warning: tmpnam
) n
..
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
sys/statfs.h \
poll.h sys/poll.h pwd.h utime.h sys/param.h libintl.h \
libgen.h util/debug.h util/msg18n.h frame.h \
! sys/acl.h sys/access.h sys/sysctl.h sys/sysinfo.h wchar.h wctype.h)
-- snipped --
With the patch, warnings gone.
Thank you.
--
Dasn
namelen, void *oldp, size_t *oldlenp,
void *newp, size_t newlen);
The missing prerequisite header is sys/param.h.
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org
}
static struct vimvar
{
It doesn't trigger any on OpenBSD 4.4 (i386), which uses a derivative of
gcc 3.3.5.
$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-unknown-openbsd4.4/3.3.5/specs
Configured with:
Thread model: single
gcc version 3.3.5 (propolice)
--
Dasn
' buffers are not displayed.
2) Both Refuse to die lines goes into one buffer, but I think they
should be dispatched to each buffer (I mean one line per buffer) before
they are being wiped out.
Vim-7.2-166
Thanks.
--
Dasn
--~--~-~--~~~---~--~~
You received
have got moved.
endif
endfun
call Test()
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
the 50th line got moved.
call append('$', Log: Where is the 50th line? )
exe normal G
endif
endfun
call Test()
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org
: This command will triger the problem
call append('$', Log: Where is the 50th line? )
exe normal G
endif
endfun
call Test()
redraw!
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http
On 11/05/08 08:32 +0800, Dasn wrote:
On 08/05/08 17:40 -0700, Gary Johnson wrote:
I don't know the history or rationale behind the current
implementation of sh_vimglob_func, but it seems odd that the first
echo is given the -n option to suppress the final newline, then a
second echo
On 02/05/08 22:23 +0200, Bram Moolenaar wrote:
Dasn wrote:
It seems highlighted wrong in Visual Line mode with:
vim -u NONE -c se sbr=+ smd wrap co=80 lines=25|pu! =repeat('k',2000)|
norm $
Then press 'V' to see the problem.
Highlighting starts at the cursor, instead
On 02/05/08 01:10 +0200, Tony Mechelynck wrote:
On 02/05/08 00:01, Dasn wrote:
On 01/05/08 20:42 +1000, Ben Schmidt wrote:
$ cat test.c
#define MAX 12
#define PIPE_SIZE (12)
$ vim -Nu NONE +syn on test.c
Please note the PIPE_SIZE.
It works fine for me. Both MAX
On 02/05/08 07:49 +0800, Dasn wrote:
On 02/05/08 01:10 +0200, Tony Mechelynck wrote:
On 02/05/08 00:01, Dasn wrote:
On 01/05/08 20:42 +1000, Ben Schmidt wrote:
$ cat test.c
#define MAX 12
#define PIPE_SIZE (12)
$ vim -Nu NONE +syn on test.c
Please note
It seems highlighted wrong in Visual Line mode with:
vim -u NONE -c se sbr=+ smd wrap co=80 lines=25|pu! =repeat('k',2000)| norm $
Then press 'V' to see the problem.
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more
$ cat test.c
#define MAX 12
#define PIPE_SIZE (12)
$ vim -Nu NONE +syn on test.c
Please note the PIPE_SIZE.
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
On 01/05/08 11:04 +1000, Ben Schmidt wrote:
Dasn wrote:
$ cat test.c
#define MAX 12
#define PIPE_SIZE (12)
$ vim -Nu NONE +syn on test.c
Please note the PIPE_SIZE.
Looks fine to me. What do you see?
I get the MAX highlighted as Macro (which is fine), while
Well, it seems the new line continuation can be placed weirdly, which
will make the vim script syntax file even messy when considering the
line continuation. Any comments?
$ cat test.vim
e
\c
\h
\o
\ l
\e
\n(hello)
q
$ ex -Nu NONE -S test.vim
5
--
Dasn
is workable on all platforms.
$ cat test.vim
#!/usr/bin/env vim -S
echo this is a Vim script
quit
$ chmod +x test.vim
$ ./test.vim
env: vim -S: No such file or directory
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information
should be ignored, what about in a descriptive manner? e.g:
#!/real-path-to-vim/vim -S
echo this is a Vim script
quit
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
matches)
:n a\'b/DS\TAB
:n a\'b/DS\*
Adri (Vim 7.1 + patches 1-200 plus Bram's Patch for Unix filename expansion)
I can't reproduce this with 1-229. Patch 223 has been released, have a
try?
--
Dasn
--~--~-~--~~~---~--~~
You received this message from
and a Linux
$ for i in * ; do env printf %s\0 $i; done
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
platforms. :)
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
carefully interacting with various shells.
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
sfile:p:h/c.vim
syn match manCFuncDefinition display \\h\w*\\s*(me=e-1 contained
! syn region manSynopsis start=^SYNOPSIShs=s+8 end=^\u\+\s*$he=e-12
keepend contains=manSectionHeading,@cCode,manCFuncDefinition
endif
--
Dasn
--~--~-~--~~~---~--~~
You
via shell directly. e.g:
:echo glob('`for i in ~/{bin,tmp,\,}; do echo $i; done`')
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
On 13/11/07 17:25 +0800, Dasn wrote:
On 12/11/07 22:45 +0100, Nikolai Weibull wrote:
On Nov 12, 2007 10:34 PM, Bram Moolenaar [EMAIL PROTECTED] wrote:
Nikolai Weibull wrote:
Another issue is that there's doesn't seem to be a way to escape a
comma inside a brace expansion. Neither two
system(sh -c ' . 'printf aaa\000bbb' . ')
or even:
:let tmpfile=tempname()
:call system(sh -c ' . 'printf aaa\000bbb ' . tmpfile . ')
:exec sp tmpfile
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http
'csh' instead
whose glob command is better than the 'echo' of POSIX sh.
Or maybe you are interested in the patch I post to dev sometime ago.
--
Dasn
--~--~-~--~~~---~--~~
You received this message from the vim_dev maillist.
For more information, visit http
On 24/09/07 09:34 +0800, Dasn wrote:
Hi, guys.
I've posted on vim_use some days before:
$ vim -c q 'foo ~ foo'
$ vim -c normal '0
E20: Mark not set
Filename contains '~' character which is around with path separators
(i.e. ' ' and ',') has such problem.
And the patch:
Index: mark.c
35 matches
Mail list logo
