Bug#763631: less: -j option yields n-1 spurious lines before the file when going to line 1

2020-11-19 Thread Vincent Lefevre
Control: tags -1 upstream fixed-upstream On 2020-11-17 23:33:03 +0100, Vincent Lefevre wrote: > I've updated my patch to avoid this issue. But now the spurious > empty lines before the beginning of the file are avoided only > when going to the beginning of the file, more precisely to the >

Bug#763631: less: -j option yields n-1 spurious lines before the file when going to line 1

2020-11-17 Thread Vincent Lefevre
Control: tags -1 patch On 2020-11-17 03:03:03 +0100, Vincent Lefevre wrote: > On 2020-11-17 02:07:08 +0100, Vincent Lefevre wrote: > > I've attached a simple patch. The idea is that the line number for > > the A_GOLINE command must not be smaller than the -j value, except > > when this value is

Bug#763631: less: -j option yields n-1 spurious lines before the file when going to line 1

2020-11-16 Thread Vincent Lefevre
Control: tags -1 upstream Control: forwarded -1 https://github.com/gwsw/less/issues/93 I can reproduce the bug with upstream's master branch. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer

Bug#763631: less: -j option yields n-1 spurious lines before the file when going to line 1

2020-11-16 Thread Vincent Lefevre
Control: tags -1 - patch On 2020-11-17 02:07:08 +0100, Vincent Lefevre wrote: > I've attached a simple patch. The idea is that the line number for > the A_GOLINE command must not be smaller than the -j value, except > when this value is larger than the screen height (this is probably > an

Bug#763631: less: -j option yields n-1 spurious lines before the file when going to line 1

2020-11-16 Thread Vincent Lefevre
Control: found -1 551-2 Control: tags -1 patch On 2014-10-01 16:15:52 +0200, Vincent Lefevre wrote: > When the -j option is used with a value larger than 1 (the purpose of > this option), n-1 spurious lines appear before the file when going to > line 1. For instance, type: > > printf "Line