Bug#245847: scale and autoscale don't work with this new fix!
On Mon, Dec 13, 2004 at 08:43:46PM +0100, Alan Schmitt wrote:
> Le 13 déc. 04, à 12:43, Sven Luther a écrit :
>
> >On Mon, Dec 13, 2004 at 12:24:14PM +0100, Alan Schmitt wrote:
> >>Le 13 déc. 04, à 10:23, San VU NGOC a écrit :
> >>
> >>>yes for me h,j,k,l work as page-movement too.
> >>>BUT if you press, say, j, while the bottom of the page is already
> >>>shown, THEN it shows the next page. This is a bug or a feature, as
> >>>one
> >>>wishes.
> >>
> >>I wrote that code, and this is indeed how it is intended to work.
> >
> >Well, it would be more intuitive ig the page jump behavior happened
> >only on
> >the second boundary click.
>
> I'm not sure to understand. Do you mean:
> top of page: j -> goes down somewhat (let's say to bottom of page); j
> -> nothing happens; j -> next page?
>
> I'm not sure I would like this, I very often display a full page, and
> use j and k to navigate. I would not like to have to hit the key twice.
You already have page-down, page-up and space to go to the next page, don't
you ?
> >also it would be nice if the move delta was cobfigurable, or had a
> >finer
> >ratio. HJKL -> current behavior, hjkl -> more fine grained moves.
>
> It would indeed be nice to be configurable. At the moments it works
> like "page down" for gv, for instance (IIRC how gv works).
>
> >Mmm, maybe it would even be possible to map the arrow keys, not sure
> >though.
>
> This is however very tricky with graphics.
Bah, you just get the keycode of the arrow key, if other apps can do it, so
can advi.
Friendly,
Sven Luther
Reply to: