URL:
  <http://savannah.gnu.org/bugs/?29240>

                 Summary: Doc addenum to windowlist keybindings
                 Project: GNU Screen
            Submitted by: mrbrown8
            Submitted on: Tue 16 Mar 2010 09:18:28 PM MDT
                Category: Documentation
                Severity: 3 - Normal
                Priority: 5 - Normal
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
                 Release: Cur Dev Sources
           Fixed Release: None
         Planned Release: None
           Work Required: None

    _______________________________________________________

Details:

The attached patch adds documentation about navigating in windowlists. For
this case I chose to separately list the bindings as there wasn't a section on
"standard movement keys", unless you count what was in the Copy and Paste
section (in the texinfo manual). Currently under windowlist, there's a
reference to the keybindings in copymode that implies in my opinion that those
bindings are standard across the entire 'screen' application. The problem I
had with this is that there were keybindings in copy mode that don't exist in
windowlist (and of course, vise versa). It's quite possible to create a
top-level chapter on what bindings are universal and then only include the
extra bindings to those sections that have them, but I just didn't go that
route.

Comments are welcomed.




    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Tue 16 Mar 2010 09:18:28 PM MDT  Name:
patch_doc_addenum_windowlist_keybinds.diff  Size: 5kB   By: mrbrown8

<http://savannah.gnu.org/bugs/download.php?file_id=19962>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?29240>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/



Reply via email to