Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Enno
Le lundi 1 décembre 2014 20:42:50 UTC+1, v...@googlecode.com a écrit : Comment #3 on issue 290 by chrisbr...@googlemail.com: gVim does not jump to given linennumber if already at end of file https://code.google.com/p/vim/issues/detail?id=290 Vim 7.4 works correctly with +[number] here (if

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Enno
Le mardi 2 décembre 2014 10:06:59 UTC+1, Enno a écrit : Le lundi 1 décembre 2014 20:42:50 UTC+1, v...@googlecode.com a écrit : Comment #3 on issue 290 by chrisbr...@googlemail.com: gVim does not jump to given linennumber if already at end of file

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Enno
Le mardi 2 décembre 2014 10:09:36 UTC+1, Enno a écrit : Le mardi 2 décembre 2014 10:06:59 UTC+1, Enno a écrit : Le lundi 1 décembre 2014 20:42:50 UTC+1, v...@googlecode.com a écrit : Comment #3 on issue 290 by chrisbr...@googlemail.com: gVim does not jump to given linennumber if

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Jürgen Krämer
Hi, Enno schrieb am 02.12.2014 um 10:06: Le lundi 1 décembre 2014 20:42:50 UTC+1, v...@googlecode.com a écrit : Comment #3 on issue 290 by chrisbr...@googlemail.com: gVim does not jump to given linennumber if already at end of file https://code.google.com/p/vim/issues/detail?id=290 Vim

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Enno
Le mardi 2 décembre 2014 10:44:13 UTC+1, jott...@googlemail.com a écrit : Hi, Enno schrieb am 02.12.2014 um 10:06: Le lundi 1 décembre 2014 20:42:50 UTC+1, v...@googlecode.com a écrit : Comment #3 on issue 290 by chrisbr...@googlemail.com: gVim does not jump to given linennumber if

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Enno
Le mardi 2 décembre 2014 11:38:10 UTC+1, Enno a écrit : Le mardi 2 décembre 2014 10:44:13 UTC+1, jott...@googlemail.com a écrit : Hi, Enno schrieb am 02.12.2014 um 10:06: Le lundi 1 décembre 2014 20:42:50 UTC+1, v...@googlecode.com a écrit : Comment #3 on issue 290 by

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Jürgen Krämer
Hi Enno schrieb am 02.12.2014 um 11:39: Le mardi 2 décembre 2014 11:38:10 UTC+1, Enno a écrit : Le mardi 2 décembre 2014 10:44:13 UTC+1, jott...@googlemail.com a écrit : Hi, Enno schrieb am 02.12.2014 um 10:06: Le lundi 1 décembre 2014 20:42:50 UTC+1, v...@googlecode.com a écrit : Comment

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Enno
Le mardi 2 décembre 2014 12:00:30 UTC+1, jott...@googlemail.com a écrit : Hi Enno schrieb am 02.12.2014 um 11:39: Le mardi 2 décembre 2014 11:38:10 UTC+1, Enno a écrit : Le mardi 2 décembre 2014 10:44:13 UTC+1, jott...@googlemail.com a écrit : Hi, Enno schrieb am 02.12.2014 um 10:06:

Re: Issue 287 in vim: Newline substitution behaviour

2014-12-02 Fir de Conversatie vim
Comment #12 on issue 287 by eliseoma...@gmail.com: Newline substitution behaviour https://code.google.com/p/vim/issues/detail?id=287 Okay. I've made some other tests and it seems the after interpretation is the one taken elsewhere. We agree on your last patch as the definitive one, then.

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Enno
Le lundi 1 décembre 2014 12:39:10 UTC+1, v...@googlecode.com a écrit : Status: New Owner: Labels: Type-Defect Priority-Medium New issue 290 by enno.na...@gmail.com: gVim does not jump to given linennumber if already at end of file https://code.google.com/p/vim/issues/detail?id=290

Re: Patch 7.4.530

2014-12-02 Fir de Conversatie Matteo Cavalleri
I think I've tracked down the remaining problem. CoffeeCompile is defined as: command! -buffer -range=% -bar -nargs=* \ -complete=customlist,s:CoffeeComplete \ CoffeeCompile call s:CoffeeCompile(line1, line2, q-args) and it still gives me the invalid range error. If i remove the -buffer

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Enno
Le mardi 2 décembre 2014 15:34:09 UTC+1, Enno a écrit : Le lundi 1 décembre 2014 12:39:10 UTC+1, v...@googlecode.com a écrit : Status: New Owner: Labels: Type-Defect Priority-Medium New issue 290 by enno.na...@gmail.com: gVim does not jump to given linennumber if already at

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie Jürgen Krämer
Hi, Enno schrieb am 02.12.2014 um 16:13: Le mardi 2 décembre 2014 15:34:09 UTC+1, Enno a écrit : Le lundi 1 décembre 2014 12:39:10 UTC+1, v...@googlecode.com a écrit : Status: New Owner: Labels: Type-Defect Priority-Medium New issue 290 by enno.na...@gmail.com: gVim does not jump to

Re: Issue 290 in vim: gVim does not jump to given linennumber if already at end of file

2014-12-02 Fir de Conversatie vim
Comment #4 on issue 290 by enno.na...@gmail.com: gVim does not jump to given linennumber if already at end of file https://code.google.com/p/vim/issues/detail?id=290 Thanks for your feedback. This was discussed on vim_dev at https://groups.google.com/forum/#!topic/vim_dev/49jGSpM4I7I The

Re: Vim crashes with list range assign.

2014-12-02 Fir de Conversatie Bram Moolenaar
Yukihiro Nakadaira wrote: Vim crashes with list range assign. Steps to reproduce: $ vim -u NONE :let x = [0] :let x[:] = [1, 2] Vim: Caught deadly signal SEGV Vim: Finished. Please check the following patch. Thanks! Especially for also writing a test. -- If you don't

Re: Patch 7.4.530

2014-12-02 Fir de Conversatie Marcin Szamotulski
On 07:13 Tue 02 Dec , Matteo Cavalleri wrote: I think I've tracked down the remaining problem. CoffeeCompile is defined as: command! -buffer -range=% -bar -nargs=* \ -complete=customlist,s:CoffeeComplete \ CoffeeCompile call s:CoffeeCompile(line1, line2, q-args) and it still

Issue 291 in vim: Unicode showbreak character causes mispositioned cursor

2014-12-02 Fir de Conversatie vim
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 291 by meta...@gmail.com: Unicode showbreak character causes mispositioned cursor https://code.google.com/p/vim/issues/detail?id=291 What steps will reproduce the problem? 1. :set showbreak=» 2. Edit a file with long

Re: Issue 291 in vim: Unicode showbreak character causes mispositioned cursor

2014-12-02 Fir de Conversatie vim
Comment #1 on issue 291 by chrisbr...@googlemail.com: Unicode showbreak character causes mispositioned cursor https://code.google.com/p/vim/issues/detail?id=291 Should already be fixed by 7.4.478. Please confirm. -- You received this message because this project is configured to send all

Re: Issue 291 in vim: Unicode showbreak character causes mispositioned cursor

2014-12-02 Fir de Conversatie vim
Comment #2 on issue 291 by mged...@gmail.com: Unicode showbreak character causes mispositioned cursor https://code.google.com/p/vim/issues/detail?id=291 I think this was fixed in 7.4.478. At any rate I cannot reproduce this with 7.4.525. -- You received this message because this project is

Re: Patch 7.4.530

2014-12-02 Fir de Conversatie Marcin Szamotulski
On 18:21 Tue 02 Dec , Marcin Szamotulski wrote: On 07:13 Tue 02 Dec , Matteo Cavalleri wrote: I think I've tracked down the remaining problem. CoffeeCompile is defined as: command! -buffer -range=% -bar -nargs=* \ -complete=customlist,s:CoffeeComplete \ CoffeeCompile

incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Troy Sankey
I noticed a bug with viewport positioning when incsearch and scrolloff are set. It's rare and difficult to reproduce, but can be reproduced with vim 7.3.547-7 (debian) and 7.4.537-1 (arch). I'm pretty sure this bug is not present in gvim. I've been able to reproduce this bug using a specific

Re: incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Christian Brabandt
Hi Troy! On Di, 02 Dez 2014, Troy Sankey wrote: I noticed a bug with viewport positioning when incsearch and scrolloff are set. It's rare and difficult to reproduce, but can be reproduced with vim 7.3.547-7 (debian) and 7.4.537-1 (arch). I'm pretty sure this bug is not present in gvim.

Re: Patch 7.4.530

2014-12-02 Fir de Conversatie Bram Moolenaar
Marcin Szamotulski wrote: On 18:21 Tue 02 Dec , Marcin Szamotulski wrote: On 07:13 Tue 02 Dec , Matteo Cavalleri wrote: I think I've tracked down the remaining problem. CoffeeCompile is defined as: command! -buffer -range=% -bar -nargs=* \

Re: incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Troy Sankey
On 2014-12-02 14:26:42 -0800, Christian Brabandt wrote: What is the debian version again? debian 7.7 (stable) I am sorry, I can't reproduce that. If your physical terminal is smaller than than 141 columns, make sure to widen it (or reduce font size) since tmux will only go as wide as the

Re: incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Renning
i'm able to reproduce this in both debian 7.7 (7.3.547) and ubuntu 12.04 (7.3.429) (but both using vagrant virtual box images) as well as arch linux (7.4.537) (my desktop). -- -- You received this message from the vim_dev maillist. Do not top-post! Type your reply below the text you are

Re: incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Troy Sankey
On 2014-12-02 15:08:49 -0800, Renning wrote: i'm able to reproduce this in [...] ubuntu 12.04 (7.3.429) Yea...me too. I take back what I said about not being able to reproduce in ubuntu 12.04. Just to be clear, 7.4.52 (ubuntu 14.04) is also affected. Troy -- -- You received this message

Re: incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Marius Gedminas
On Tue, Dec 02, 2014 at 02:03:07PM -0800, Troy Sankey wrote: I noticed a bug with viewport positioning when incsearch and scrolloff are set. It's rare and difficult to reproduce, but can be reproduced with vim 7.3.547-7 (debian) and 7.4.537-1 (arch). I cannot reproduce with vim 7.4.540.

Re: incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Christian Brabandt
Am 2014-12-03 00:01, schrieb Troy Sankey: On 2014-12-02 14:26:42 -0800, Christian Brabandt wrote: What is the debian version again? debian 7.7 (stable) I meant the debian Vim version. There is no 7.4.547 version yet. I am sorry, I can't reproduce that. If your physical terminal is

Re: incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Christian Brabandt
Am 2014-12-03 08:32, schrieb Christian Brabandt: Am 2014-12-03 00:01, schrieb Troy Sankey: On 2014-12-02 14:26:42 -0800, Christian Brabandt wrote: What is the debian version again? debian 7.7 (stable) I meant the debian Vim version. There is no 7.4.547 version yet. (Nevermind. You meant

Re: incsearch+scrolloff causes incorrect viewport positioning

2014-12-02 Fir de Conversatie Troy Sankey
On 2014-12-02 23:32:36 -0800, Christian Brabandt wrote: I meant the debian Vim version. There is no 7.4.547 version yet. 7.3.547 Troy -- -- 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