On Tue, Dec 2, 2008 at 8:38 PM, Brian Cameron <Brian.Cameron at sun.com> wrote: > > Peter: > >>> To me, this sounds like the problem described in this email thread. I >>> think this is the right bug report. >> >> Do you know who logged that bug report? >> >> The bug refers to how the behaviour of PgUp/PgDown/Home/End have >> changed relative to Solaris 10 (and early SXCE builds). Where the keys >> scrolled the window, and no longer do so. > > Okay, thanks for clarifying. The original bug report was that these > keys should affect the scrollbar and work the same as when you hold down > the Shift key. So, we probably need to decide whether we want it to > work that way, or whether we want to define these keys to work as they > do on Linux, where they help you to navigate a file you are editing. > Personally, I think the later would be more useful.
And many of us think otherwise. I don't edit inside of a terminal window as a rule - if I'm editing files I use an editor. But that's not really the point - the point is that we need to make it possible for different modes of operation to exist so that you don't have to foce any groups to be utterly miserable. (And I don't really know why this particular behaviour irritates me so much. But it really does drive me absolutely potty to the point where I want to pick the system up and throw it out of the window. And I can adapt to most things.) > We probably should have just one bug report, since we can't have it > behave in both ways. Why not? Why not actually let users choose which behaviour they want? You could even imagine multiple profiles with different settings. (You can have it either way in xterm, for example. It's not a menu choice or anything like that, but it is possible to configure it ether way.) > That said, I am happy to move the bug back to the > jds/gnome/terminal category and clarify in the bug report that we want > the behavior to be the same as on Solaris 10 and early SXCE builds if > we think that is the right fix. The request - really - is that it be possible to get the old behaviour back. It doesn't have to be the default. It doesn't have to be exposed as a menu choice. Some manual hack would be entirely adequate. And I think that there are multiple bugs here. The issue about whether the keys should scroll the terminal window is completely separate from the issue of what the application should do if it gets the keystrokes passed through to it, which is what Shawn's talking about. -- -Peter Tribble http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
