Re: [vim] Crash while mouse-selecting in two-buffer mode (#486)

On Thursday, November 19, 2015 at 10:19:23 PM UTC+13, Kirill Ivashov wrote: > if I click as far right as possible > > Issue title states not "clicking" but "selecting" which means "Hold left > mouse down and move cursor". There's confusion here, or at least I am. There are two "cursors": the

Re: [vim] Crash while mouse-selecting in two-buffer mode (#486)

I can't reproduce this, though I am seeing incorrect behaviour. > click as right as possible (terminal size should be larger than column size * > column count I don't know what "column size" and "column count" refer to, sorry. Making my konsole 248 columns wide, if I click as far right as

Re: [patch] Longest match does not support multi-byte in command-line.

Hirohito Higashi wrote: > Hi Bram and List! > > How to reproduce: > - Prepare vimrc for reproduce. > $ cat xxx.vim > function! CustomComplete(lead, line, pos) >return ['あたし', 'あたま', 'あたりめ'] > endfunction > command -nargs=1 -complete=customlist,CustomComplete Test : > > - Run pure vim

Patch 7.4.927

Patch 7.4.927 Problem:Ruby crashes when there is a runtime error. Solution: Use ruby_options() instead of ruby_process_options(). (Damien) Files: src/if_ruby.c *** ../vim-7.4.926/src/if_ruby.c2015-11-02 15:27:03.438325506 +0100 --- src/if_ruby.c 2015-11-19

Re: Patch 7.4.925

On Thu, Nov 19, 2015 at 5:56 PM, Bram Moolenaar wrote: > Patch 7.4.925 > + static void > + recording_mode(attr) > + int attr; > + { > + MSG_PUTS_ATTR(_("recording"), attr); > + if (!shortmess(SHM_RECORDING)) > + { > + char_u s[4]; > +

Patch 7.4.930

Patch 7.4.930 Problem:MS-Windows: Most users appear not to like the window border. Solution: Remove WS_EX_CLIENTEDGE. (Ian Halliday) Files: src/gui_w32.c *** ../vim-7.4.929/src/gui_w32.c2015-08-27 22:25:03.464318030 +0200 --- src/gui_w32.c 2015-11-19 20:20:37.224433622

Re: Patch 7.4.926

Hi Christian! 2015-11-20(Fri) 6:37:46 UTC+9 Christian Brabandt: > Hi Bram! > > On Do, 19 Nov 2015, Bram Moolenaar wrote: > > > > > Patch 7.4.926 > > Problem:Completing the longest match doesn't work properly with > > multi-byte > > characters. > > Solution: When using

Re: Patch 7.4.926

Hi Bram! On Do, 19 Nov 2015, Bram Moolenaar wrote: > > Patch 7.4.926 > Problem:Completing the longest match doesn't work properly with multi-byte > characters. > Solution: When using multi-byte characters use another way to find the > longest match. (Hirohito

Re: [vim] Vim removes last newline (#488)

Laurent Lyaudet wrote: > > Hi, > > I have found the following bug. When I open a file in Vim the last > newline disappears. > Hence it is impossible to see it is there and to remove it (suppress > or backspace doesn't work). > The problem occurs both with Linux '\n' and Windows '\r\n'. > > I join

Patch 7.4.928

Patch 7.4.928 Problem:A clientserver message interrupts handling keys of a mapping. Solution: Have mch_inchar() send control back to WaitForChar when it is interrupted by server message. (James Kolb) Files: src/os_unix.c *** ../vim-7.4.927/src/os_unix.c2015-09-15

Patch 7.4.929

Patch 7.4.929 Problem:"gv" after paste selects one character less if 'selection' is "exclusive". Solution: Increment the end position. (Christian Brabandt) Files: src/normal.c, src/testdir/test94.in, src/testdir/test94.ok *** ../vim-7.4.928/src/normal.c 2015-09-25

Re: Patch 7.4.925

On Do, 19 Nov 2015, Christ van Willegen wrote: > On Thu, Nov 19, 2015 at 5:56 PM, Bram Moolenaar wrote: > > Patch 7.4.925 > > > + static void > > + recording_mode(attr) > > + int attr; > > + { > > + MSG_PUTS_ATTR(_("recording"), attr); > > + if

Re: [vim] comments inside parentheses mess up the syntax coloring of shell script (#487)

Christian Brabandt wrote: > > Please discuss this with the maintainer of the current indentation > file. See Contributing.md > > > I see no problems. Try the latest

Re: Patch 7.4.925

On Thu, Nov 19, 2015 at 10:45 PM, Christian Brabandt wrote: > On Do, 19 Nov 2015, Christ van Willegen wrote: >> Is it (perhaps remotely...) possible to record into a register that >> internally translates to a 2-byte value, overflowing the buffer >> allocated to be 4 bytes? >

Re: words counting and select mode.

Christian Brabandt wrote: > On Fr, 13 Nov 2015, Christian Brabandt wrote: > > On Di, 10 Nov 2015, hermi...@free.fr wrote: > > > Could we have a countword() function that would avoid such dirty tricks? > > I'll look into this. > > Attached is a patch. Thanks. I think the help should mention

Patch 7.4.924

Patch 7.4.924 Problem:DEVELOPER_DIR gets reset by configure. Solution: Do not reset DEVELOPER_DIR when there is no --with-developer-dir argument. (Kazuki Sakamoto, closes #482) Files: src/configure.in, src/auto/configure *** ../vim-7.4.923/src/configure.in 2015-09-09

Patch 7.4.923

Patch 7.4.923 Problem:Prototypes not always generated. Solution: Change #if to OR with PROTO. Files: src/window.c *** ../vim-7.4.922/src/window.c 2015-08-11 19:13:55.146175594 +0200 --- src/window.c2015-11-19 13:12:37.441097266 +0100 *** *** 5580,5586 }

Re: [vim] Crash while mouse-selecting in two-buffer mode (#486)

Hi, 2015-11-20(Fri) 6:43:29 UTC+9 Christian Brabandt: > Which one is line 5790? Can you print the value ofr fr and curfr? (use p fr > and p curfr on the gdb prompt at frame 7) I can reproduced it. (fedora21 + konsole) and make a patch. Please check this. -- Best regards, Hirohito Higashi

Re: [vim] Crash while mouse-selecting in two-buffer mode (#486)

Hi, 2015-11-20(Fri) 14:20:48 UTC+9 h_east: > Hi, > > 2015-11-20(Fri) 6:43:29 UTC+9 Christian Brabandt: > > Which one is line 5790? Can you print the value ofr fr and curfr? (use p fr > > and p curfr on the gdb prompt at frame 7) > > I can reproduced it. (fedora21 + konsole) > and make a

[patch] Longest match does not support multi-byte in command-line.

Hi Bram and List! How to reproduce: - Prepare vimrc for reproduce. $ cat xxx.vim function! CustomComplete(lead, line, pos) return ['あたし', 'あたま', 'あたりめ'] endfunction command -nargs=1 -complete=customlist,CustomComplete Test : - Run pure vim with above resource file. $ vim -N -u xxx.vim -

Patch 7.4.925

Patch 7.4.925 Problem:User may yank or put using the register being recorded in. Solution: Add the recording register in the message. (Christian Brabandt, closes #470) Files: runtime/doc/options.txt, runtime/doc/repeat.txt, src/ops.c, src/option.h, src/screen.c

Re: [vim] Yanking into the same registry slot as the macro's currently being recorded cause macro to be yanked instead. (#470)

Christian Brabandt wrote: > On Mo, 16 Nov 2015, Christian Brabandt wrote: > > So how about adding some warning into the documentation that putting > > from the same register that is used for recording won't likely work as > > one would expect and perhaps also mention in the status line which > >