[comp.windows.x.motif] Effect of Keyboard Paging

ellis@osf.org (11/21/90)

     > I can't understand how one could get used to this. If I hit next-page
     > a bunch of times, and I'm looking at text in the middle of the buffer,
     > how am I supposed to start editing that text? Am I supposed to reach
     > over, grab the mouse and click on the spot I want to modify?

> I don't agree.  How would I cut a large area of text - more than a page in
> length - if hitting next-page moves my text insertion point?  On the Mac, I
> often will put my text insertion point at one location, page down several
> pages, extend select another location (selecting multiple pages of text back
> to the first text insertion point), Cut, move to another location and Paste.
> How would I do this with if the insertion point moved when I hit next-page?

There are two alternatives:

1.  Have keyboard paging leave the cursor where it is in the document.
    To edit at the location you are at after paging, one must use the mouse
    to click.

2.  Have keyboard paging leave the cursor where it is in the viewport.
    To select an area of text: type KSelect, do paging, when you're in the
    right page, type Shift+Btn1 Click at the right location, or navigate to
    the right location and type Shift+KSelect.
    Alternately, you can type Shift+KPageDown to extend the current selection
    as you page.
    In this model, scrollbar-based paging still leave the cursor where
    it is in the document.  A keyboard user can take advantage of this
    if necessary by traversing to the scrolling, and navigating in the
    scrollbar.

We're aware of the two possibilities and will be considering what to
do about the current paging model.

  -- Ellis