GNOME Bugzilla – Bug 110794
Overview pane, shift-home/end doesn't select-to beginning/end
Last modified: 2006-06-18 05:10:59 UTC
Bug exists since 0.13.4, probably from the fix on #88869. Formerly, shift-home/end would select all messages from current position to beginning/end of list. It doesn't work any more. Note that keyboard selection in general has been broken since the shift to gtk2, for known reasons (widget broken, had to choose that or mouse selection functionality and mouse won over keyboard). However, until 0.13.4, one could at least use shift-home/end to select messages, if that's what one wanted. That no longer works. Note also that it could be CONTROL-shift-home/end, or just shift-home-end, since there's not a logical local line beginning/end to select to, as is the standard default for plain shift modified, without control as well. I believe the former functionality didn't use the control, but restoring the functionality either way or both ways would make PAN much more useful to those using the keyboard a lot, again. Finally, note this has been discussed on the user list, both back with 0.13.4, and now with 0.13.94, the latter threadlet as part of the .94 announcement thread. Of course, we won't complain if the rest of the broken keyboard functionality (repeated shift-PgUp/PgDn, and shift-up/dn, extending the selection, rather than starting a new one) since gtk2 was returned as well, but if the widget is still broken, just returning select-to-beginning and select-to-end as above would be a big step. =:^)
> Bug exists since 0.13.4, probably from the fix on #88869. Yes, I think you're right. > Formerly, shift-home/end would select all messages from > current position to beginning/end of list. It doesn't work > any more. The original keybinding was control-shift-home/end, not shift-home/end. Tested with 0.13.3. > Note also that it could be CONTROL-shift-home/end, > or just shift-home-end, since there's not a logical > local line beginning/end to select to, as is the > standard default for plain shift modified, without > control as well. I believe the former functionality > didn't use the control, but restoring the functionality > either way or both ways would make PAN much more useful > to those using the keyboard a lot, again. Fixed in CVS, to restore control-shift-{begin,end} and further to make shift-{begin,end} have the same behavior: http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=pan/pan&command=DIFF_FRAMESET&file=articlelist.c&rev1=1.618&rev2=1.619&root=/cvs/gnome http://cvs.gnome.org/bonsai/cvsview2.cgi?diff_mode=context&whitespace_mode=show&subdir=pan&command=DIFF_FRAMESET&file=ANNOUNCE.html&rev1=1.124&rev2=1.125&root=/cvs/gnome > Finally, note this has been discussed on the user list, > both back with 0.13.4, and now with 0.13.94, the latter > threadlet as part of the .94 announcement thread. Yes, and I see in one of the threads you were wise enough to comment, "I'd suggest filing a bug report," :) It's hard to overstate how much Chris and I rely on bugzilla. I have a hard time keeping my inbox. By contrast, bugzilla's "open 0.14.0 bugs" page[1] is my current homepage. > Of course, we won't complain if the rest of the broken > keyboard functionality (repeated shift-PgUp/PgDn, and > shift-up/dn, extending the selection, rather than > starting a new one) since gtk2 was returned as well, File a new bug report and I'll look into this after 0.14.0. [1] http://bugzilla.gnome.org/buglist.cgi?product=Pan&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=VERIFIED&target_milestone=0.14.0