Sergey Poznyakoff wrote: > I have also fixed this: > > > Now... just one more thing. When cursor-movement-scrolls=On, > > the action 'scroll-backward' should behave exactly the same way > > as when the cursor is on the top line and <up> is pressed.
Thanks. <Up> and <PageUp> don't work exactly the same, though. When the preceding node is longer than a screenful, <Up> shows a full page (with the cursor at the bottom), whereas <PageUp> shows half a page (with the cursor at the start of the centre line). Compare: info info, N, 5, Up, Down, Pageup, Down, Up, Down, Pageup, Down, ... It's not important, but it's somewhat strange. When doing <PageUp> at the top node of a document, the cursor now gets placed at the bottom. This is quite confusing when the first node of a document is longer than the screen. For example with gawk: info gawk, PageUp, PageUp, ... And also in the help text: info info, h, PageUp, PageUp, ... The cursor beviour of <PageUp> is a little strange. After doing info info, N, 6, End, then a series of PageUp puts the cursor at the following places: top, bottom, top, bottomish, top, middlish (on a 33-line 80-column Konsole). Something else: the "el" command in the help window acts as if the help window had held the same text as the other window, the window in which <h> was typed. For example: after info info, h, L, the two windows both show the first node of the Info document, which isn't right. Only when <h> reuses an existing window, should it retain the history. When <h> opens a new window, it should clear the history for that window, so that <L> says "Cannot kill the last node" and the help text stays put. Benno
