On 06/06/10 22:26, Bram Moolenaar wrote:
[...]
What do others think about removing support for GTK 1? It makes sense,
any system where you would try to build Vim 7.3 should be able to
install GTK 2 libraries. It will clean up the Vim source code.
Well, if we find any bug in GTK1, we're on ou
On Mon, 7 Jun 2010, Lech Lorens wrote:
On 06-Jun-2010 Bram Moolenaar wrote:
What do others think about removing support for GTK 1? It makes
sense, any system where you would try to build Vim 7.3 should be
able to install GTK 2 libraries. It will clean up the Vim source
code.
I like the
On 06-Jun-2010 Bram Moolenaar wrote:
> What do others think about removing support for GTK 1? It makes sense,
> any system where you would try to build Vim 7.3 should be able to
> install GTK 2 libraries. It will clean up the Vim source code.
I like the idea - remove it.
--
Cheers,
Lech
--
On Sunday 06 June 2010 15:26:58 Bram Moolenaar wrote:
> What do others think about removing support for GTK 1? It
> makes sense, any system where you would try to build Vim 7.3
> should be able to install GTK 2 libraries. It will clean up
> the Vim source code.
you'll get no argument from me
Dominique Pelle wrote:
> The following command crashes vim-7.3a (2249:4620acaf4814):
>
> $ vim -u NONE --noplugin -c ':ownsyntax foo'
>
> ==2575== Invalid read of size 1
> ==2575==at 0x80FB394: vim_strsave (misc2.c:1234)
> ==2575==by 0x8084FA1: set_internal_string_var (eval.c:994)
> ==2
Hi
The following command crashes vim-7.3a (2249:4620acaf4814):
$ vim -u NONE --noplugin -c ':ownsyntax foo'
==2575== Invalid read of size 1
==2575==at 0x80FB394: vim_strsave (misc2.c:1234)
==2575==by 0x8084FA1: set_internal_string_var (eval.c:994)
==2575==by 0x81710CA: ex_ownsyntax (
James Vega wrote:
> On Sat, Jun 05, 2010 at 10:37:39PM +0200, Patrick Texier wrote:
> > Le Sat, 05 Jun 2010 16:16:06 +0200, Bram Moolenaar a écrit dans le
> > message <201006051416.o55eg6to002...@masaka.moolenaar.net>Â :
> >
> > > Patch 7.2.442 (after 7.2.201)
> >
> > Using Linux/GCC 3.2/GTK 1
Dominique Pelle wrote:
> On Linux x86_64 (GUI athena), I see the following compilation warnings:
>
> gui_athena.c:2257:65: warning: cast to pointer from integer of different size
>
> gui_at_sb.c:823:60: warning: cast to pointer from integer of different size
> gui_at_sb.c:897:50: warning: cast
Under ":help +cmd" in doc/editing.txt, I think something should be added
or changed to mention that +/pattern positions the cursor, not on the
*first* line matching /pattern/ (from the top of the file), but on the
*next* matching line after wherever the cursor ends up after (at least)
BufReadPo
On 05/06/10 21:04, ZyX wrote:
There are some things that my 2html from stable vim (7.2.303, USE="acl bash-
completion cscope nls perl python ruby vim-pager vim-with-x") does not support,
so I ended in writing my own format.vim script:
- 'list' and 'listchars' (lcs:tab, lcs:eol and lcs:trail)
On Sat, Jun 05, 2010 at 10:37:39PM +0200, Patrick Texier wrote:
> Le Sat, 05 Jun 2010 16:16:06 +0200, Bram Moolenaar a écrit dans le
> message <201006051416.o55eg6to002...@masaka.moolenaar.net> :
>
> > Patch 7.2.442 (after 7.2.201)
>
> Using Linux/GCC 3.2/GTK 1, I can't compile this patch. I thin
Hi
On Linux x86_64 (GUI athena), I see the following compilation warnings:
gui_athena.c:2257:65: warning: cast to pointer from integer of different size
gui_at_sb.c:823:60: warning: cast to pointer from integer of different size
gui_at_sb.c:897:50: warning: cast to pointer from integer of differ
Dominique Pelle wrote:
> Attached patch fixes a build error and a warning when building vim7.3a with:
>
> $ ./configure --with-features=tiny --enable-gui=no --enable-perlinterp
> $ make
> ...
> if_perl.xs:699:9: warning: unused variable ‘safe’
> ...
> home/pel/sb/vim/src/if_perl.xs:1261: undefin
On 06/06/10 15:12, björn wrote:
Hi,
Lately I've been getting the following warning (on Mac OS X 10.6, 64 bit):
fileio.c: In function ‘msg_add_lines’:
fileio.c:5230: warning: format ‘%ld’ expects type ‘long int’, but
argument 6 has type ‘off_t’
fileio.c:5247: warning: format ‘%ld’ expects type ‘
Hi
Attached patch fixes a build error and a warning when building vim7.3a with:
$ ./configure --with-features=tiny --enable-gui=no --enable-perlinterp
$ make
...
if_perl.xs:699:9: warning: unused variable ‘safe’
...
home/pel/sb/vim/src/if_perl.xs:1261: undefined reference to `update_curbuf'
-- D
Sorry, I have seen older installed help file not vim73 repository's.
I installed vim73 to my system so that problem was solved. Thanks.
On Jun 6, 9:23 pm, Bram Moolenaar wrote:
> Tyru wrote:
> > The definition of MAX_MSG_HIST_LEN in feature.h,
> > is 200 in +small or higher version.
>
> > --- quo
Hi,
Lately I've been getting the following warning (on Mac OS X 10.6, 64 bit):
fileio.c: In function ‘msg_add_lines’:
fileio.c:5230: warning: format ‘%ld’ expects type ‘long int’, but
argument 6 has type ‘off_t’
fileio.c:5247: warning: format ‘%ld’ expects type ‘long int’, but
argument 5 has type
Tyru wrote:
> The definition of MAX_MSG_HIST_LEN in feature.h,
> is 200 in +small or higher version.
>
> --- quote ---
> /*
> * Message history is fixed at 100 message, 20 for the tiny version.
> */
> #ifdef FEAT_SMALL
> # define MAX_MSG_HIST_LEN 200
> #else
> # define MAX_MSG_HIST_LEN 20
> #e
Dominique Pelle wrote:
> I see the following compilation warning when compiling
> Vim-7.3a (2245:1bac28a53fae):
>
> syntax.c:4506: warning: suggest braces around empty body in an =91else=92 s=
> tatement
>
> It happens when FEAT_MBYTE is defined & FEAT_CONCEAL is undefined
> which is the case w
Dominique Pelle wrote:
> I can reproduce a crash "Floating point exception"
> in Vim-7.3a (2245:1bac28a53fae) as follows:
>
> $ cd /tmp
> $ echo "set cryptmethod=1 undodir=/tmp undofile" > vimrc
> $ rm -f foo .foo*
> $ vim --noplugin -u vimrc -c 'call
> feedkeys("ifoo\:X\foo\foo\:wq\")' foo
> $
Dominique Pelle wrote:
> Building Vim-7.3a (2245:1bac28a53fae) with:
>
> $ ./configure --with-features=3Dtiny --enable-gui=3Dmotif --enable-workshop
> $ make
>
> I see the following compilation warnings:
>
> menu.c:2534:1: warning: =91menu_unescape_name=92 defined but not used
>
> gui_beval.c
Hi
Building Vim-7.3a (2245:1bac28a53fae) with:
$ ./configure --with-features=tiny --enable-gui=motif --enable-workshop
$ make
I see the following compilation warnings:
menu.c:2534:1: warning: ‘menu_unescape_name’ defined but not used
gui_beval.c:31:12: warning: unused variable ‘save_curbuf’
gu
Ответ на сообщение «Re: Progress indicator for :TOhtml command»,
присланное в 13:03:23 06 июня 2010, Воскресенье,
отправитель ZyX:
Yes, buffer switching is the problem: attached patch uses my technique (save
everything in a list, not in a buffer) and here are the results:
My script:
1:05,09 w/o
Ответ на сообщение «Re: Progress indicator for :TOhtml command»,
присланное в 10:59:42 06 июня 2010, Воскресенье,
отправитель Benjamin Fritz:
It is odd: the only problem in your script is redrawstatus which is called only
100 times (without styles, 109 with) (>21 seconds), while in my script
re
Hi.
The definition of MAX_MSG_HIST_LEN in feature.h,
is 200 in +small or higher version.
--- quote ---
/*
* Message history is fixed at 100 message, 20 for the tiny version.
*/
#ifdef FEAT_SMALL
# define MAX_MSG_HIST_LEN 200
#else
# define MAX_MSG_HIST_LEN 20
#endif
--- quote ---
But above com
Ответ на сообщение «Re: Progress indicator for :TOhtml command»,
присланное в 10:59:42 06 июня 2010, Воскресенье,
отправитель Benjamin Fritz:
The reason why I say that progress bar is too slow is that my script does not
suffer from performance decrease unless you make it redraw on each line. I w
Hi
I see the following compilation warning when compiling
Vim-7.3a (2245:1bac28a53fae):
syntax.c:4506: warning: suggest braces around empty body in an ‘else’ statement
It happens when FEAT_MBYTE is defined & FEAT_CONCEAL is undefined
which is the case when configuring Vim with:
./configure -w
27 matches
Mail list logo
