Re: Weird behaviour with the 'gN' command

2016-10-15 Thread Osman Koçak
Hi Christian, I don't know if this is a bug or not, but imho this behaviour is inconsistent with the forward search and needs to be documented. Anyway, I won't open an issue if you think it is not necessary, you probably know Vim's internals better than I do. Also, this is not an issue for me

Re: Weird behaviour with the 'gN' command

2016-10-15 Thread Christian Brabandt
Hi Osman! On Sa, 15 Okt 2016, Osman Koçak wrote: > any update regarding this issue ? As I explained before, I think there is nothing to "fix" here, since it is not clear where a previous/next match starts. Best, Christian -- Liegt des Bauern Uhr im Mist, weiß er nicht wie spät es ist. --

Re: Weird behaviour with the 'gN' command

2016-10-15 Thread Igor Forca
@kocakosm, I advice you to open a bug report in vim's github. I know Christian wrote bug report is not needed, but people get distracted with some other tasks and if bug is not reported it can be overlooked. I advice to report a bug on github and also point to this discussion. -- -- You

Re: Weird behaviour with the 'gN' command

2016-10-14 Thread Osman Koçak
Hi, any update regarding this issue ? ++ Osman 2016-10-09 23:25 GMT+02:00 Osman Koçak : > Hmmm, I see... > However, I think it should be possible to fix it since the forward search > ('/') don't mess up in such cases. > I also have a "workaround" (in Vimscript) that

Re: Weird behaviour with the 'gN' command

2016-10-09 Thread Osman Koçak
Hmmm, I see... However, I think it should be possible to fix it since the forward search ('/') don't mess up in such cases. I also have a "workaround" (in Vimscript) that **seems** to work (I wrote and tested it quite quickly, so I'm not sure): function! Select_match() abort if == 'exclusive'

Re: Weird behaviour with the 'gN' command

2016-10-09 Thread Christian Brabandt
On So, 09 Okt 2016, Osman Koçak wrote: > OK, can you please let me know when the patch eventually gets into Vim. > Thanks again! Hm, that is a tricky one and I am not sure how to solve that one. If you take this text (here with line numbers:) 1 test test test test 2 test test test test 3 test

Re: Weird behaviour with the 'gN' command

2016-10-09 Thread Osman Koçak
OK, can you please let me know when the patch eventually gets into Vim. Thanks again! ++ Osman 2016-10-09 15:34 GMT+02:00 Christian Brabandt : > Hi Osman! > > On So, 09 Okt 2016, Osman Koçak wrote: > > > This is great news :) Thank you very much ! > > Do you want me to file

Re: Weird behaviour with the 'gN' command

2016-10-09 Thread Christian Brabandt
Hi Osman! On So, 09 Okt 2016, Osman Koçak wrote: > This is great news :) Thank you very much ! > Do you want me to file a bug on github ?  Not needed, I already reproduced the problem. Best, Christian -- Arbeiter arbeiten hart. Mein Geld auch. Sogar härter, als mancher Arbeiter. -- -- You

Re: Weird behaviour with the 'gN' command

2016-10-09 Thread Osman Koçak
Hi Christian, This is great news :) Thank you very much ! Do you want me to file a bug on github ? ++ Osman 2016-10-09 12:57 GMT+02:00 Christian Brabandt : > Hi Osman! > > On Sa, 08 Okt 2016, Osman Koçak wrote: > > > Hi, > > > > I am facing a very strange behaviour with

Re: Weird behaviour with the 'gN' command

2016-10-09 Thread Christian Brabandt
Hi Osman! On Sa, 08 Okt 2016, Osman Koçak wrote: > Hi, > > I am facing a very strange behaviour with the 'gN' command... > It's quite difficult to describe, so let me explain how to reproduce it > instead > First, enter the following text in Vim: > test test test test > test test test test

Weird behaviour with the 'gN' command

2016-10-09 Thread Osman Koçak
Hi, I am facing a very strange behaviour with the 'gN' command... It's quite difficult to describe, so let me explain how to reproduce it instead First, enter the following text in Vim: test test test test test test test test test test test test test test test test Put the cursor on the