Issue 123 in vim: Windows gui: window position is changed when invoking :vert & :tab under certain conditions

2013-03-13 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 123 by minilith: Windows gui: window position is changed when invoking :vert & :tab under certain conditions http://code.google.com/p/vim/issues/detail?id=123 I sometimes use gvim 7.3 @ win7 (64 bit). When I move the gvim w

Patch 7.3.861

2013-03-13 Fir de Conversatie Bram Moolenaar
Patch 7.3.861 Problem:":setlocal number" clears global value of 'relativenumber'. Solution: Do it properly. (Markus Heidelberg) Files: src/testdir/test89.in, src/testdir/test89.ok, src/option.c *** ../vim-7.3.860/src/testdir/test89.in2013-02-14 20:10:28.0 +0100 --- sr

Patch 7.3.860

2013-03-13 Fir de Conversatie Bram Moolenaar
Patch 7.3.860 Problem:When using --remote-expr try/catch does not work. (Andrey Radev) Solution: Set emsg_silent instead of emsg_skip. Files: src/main.c *** ../vim-7.3.859/src/main.c 2013-03-13 19:29:24.0 +0100 --- src/main.c 2013-03-13 19:46:03.0 +0100

Re: Problem with --remote-expr and error checking

2013-03-13 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > Hi Андрей! > > On Sa, 09 Mär 2013, Андрей Радев wrote: > > > While trying to evaluate commands on a remote server and get their > > output, I've ran into a problem with error checking -- it seems like > > with remote-expr there's no error-checking at all. > > > > Th

Patch 7.3.859

2013-03-13 Fir de Conversatie Bram Moolenaar
Patch 7.3.859 Problem:'ambiwidth' must be set by the user. Solution: Detects East Asian ambiguous width (UAX #11) state of the terminal at the start-up time and 'ambiwidth' accordingly. (Hayaki Saito) Files: src/main.c, src/option.c, src/term.c, src/term.h, src/

Patch 7.3.858

2013-03-13 Fir de Conversatie Bram Moolenaar
Patch 7.3.858 Problem:"gv" selects the wrong area after some operators. Solution: Save and restore the type of selection. (Christian Brabandt) Files: src/testdir/test66.in, src/testdir/test66.ok, src/normal.c *** ../vim-7.3.857/src/testdir/test66.in2010-08-15 21:57:29.

Patch 7.3.857

2013-03-13 Fir de Conversatie Bram Moolenaar
Patch 7.3.857 Problem:The QuitPre autocommand event does not trigger for :qa and :wq. Solution: Trigger the event. (Tatsuro Fujii) Files: src/ex_docmd.c *** ../vim-7.3.856/src/ex_docmd.c 2013-02-26 17:21:15.0 +0100 --- src/ex_docmd.c 2013-03-13 18:14:56.0 +0

Re: C syntax file #warn

2013-03-13 Fir de Conversatie Nirk Niggler
Bram: that page reads > #warn and #warning preprocessor directives > The #warn and #warning preprocessor directives display a string on standard > error and continue compilation. Their syntax is: > #warn string > #warning string > Example: > #warn "Feature not yet implemented." There appears to

Patch 7.3.856

2013-03-13 Fir de Conversatie Bram Moolenaar
Patch 7.3.856 Problem:When calling system() multi-byte clipboard contents is garbled. Solution: Save and restore the clipboard contents. (Yukihiro Nakadaira) Files: src/gui_gtk_x11.c, src/proto/gui_gtk_x11.pro, src/ops.c, src/proto/ops.pro, src/os_unix.c, src/proto/ui.pro,

Re: what happened to luxi mono?

2013-03-13 Fir de Conversatie Charles Campbell
Charles Campbell wrote: Hello! I seem to have run into a font problem -- as in the font I was using, "Luxi Mono 10", is no longer a valid font. Here's what happened: * used gvim with Luxi Mono 10 * broke for lunch * returned * updated vim from 7.3.784 to 7.3.796 * Luxi mono font no longer avai

Patch 7.3.855

2013-03-13 Fir de Conversatie Bram Moolenaar
Patch 7.3.855 Problem:Compiler warnings. Solution: Add type casts. (Mike Williams) Files: src/misc1.c *** ../vim-7.3.854/src/misc1.c 2013-03-07 13:13:45.0 +0100 --- src/misc1.c 2013-03-13 16:58:12.0 +0100 *** *** 5468,5474 for (i = 0; i < (

Re: Issue 120 in vim: folds are displayed incorrectly after uncaught error in try/endtry

2013-03-13 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > >> I think, this happens, because after the error, did_emsg isn't reset yet > >> when calling the foldtext() function. I am not sure, if it is safe to > >> reset did_emsg in main_loop() earlier, but at the very least, we > >> can guard updatescreen(0) by temporarily re

Re: Issue 121 in vim: cursor jumps to the end of closed fold when executing a register

2013-03-13 Fir de Conversatie Vlad Irnov
On 3/12/13, glts <676c7...@gmail.com> wrote: > Hi Christian, > > On Tuesday, March 12, 2013 9:16:04 PM UTC+1, Christian Brabandt wrote: >> Ah, I see, this only happens when sourcing as a script. The problem here >> is, that there is a subtle difference between the :@ command and the >> :normal! @ c

Re: Issue 120 in vim: folds are displayed incorrectly after uncaught error in try/endtry

2013-03-13 Fir de Conversatie Christian Brabandt
On Wed, March 13, 2013 11:55, Bram Moolenaar wrote: > > Christian Brabandt wrote: >> I think, this happens, because after the error, did_emsg isn't reset yet >> when calling the foldtext() function. I am not sure, if it is safe to >> reset did_emsg in main_loop() earlier, but at the very least, we

Re: system() break clipboard text.

2013-03-13 Fir de Conversatie Bram Moolenaar
Yukihiro Nakadaira wrote: > On Fri, Mar 8, 2013 at 2:02 AM, Bram Moolenaar wrote: > > > ... > > The only other solution I can think of is saving the owned selection and > > restoring it after system() finishes. We would need to check that the > > command executed by system() did not change the

Re: Issue 120 in vim: folds are displayed incorrectly after uncaught error in try/endtry

2013-03-13 Fir de Conversatie Bram Moolenaar
Christian Brabandt wrote: > On Tue, March 12, 2013 13:49, v...@googlecode.com wrote: > > Status: New > > Owner: > > Labels: Type-Defect Priority-Medium > > > > New issue 120 by vlad.ir...@gmail.com: folds are displayed incorrectly > > after uncaught error in try/endtry > > http://code.google