From: npostavs@users.sourceforge.net
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24224@debbugs.gnu.org, Mohammed Sadik <sadiqpkp@gmail.com>
Subject: bug#24224: Enable 'h, j, k, l' key navigation where ever possible
Date: Sun, 14 Aug 2016 14:10:25 -0400 [thread overview]
Message-ID: <87wpjjusq6.fsf@users.sourceforge.net> (raw)
In-Reply-To: <83wpjjfel5.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 14 Aug 2016 20:24:54 +0300")
severity 24224 wishlist
quit
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Mohammed Sadik <sadiqpkp@gmail.com>
>> Date: Sun, 14 Aug 2016 12:22:38 +0530
>>
>> There are several buffers where alphabet keys have no effect.
>> In such buffers, it would be nice to enable the keys h, j, k, and l, for
>> navigation, and even further q for quit (or close the buffer), o for
>> other window, etc. This might also help resolve the pinky problem a little.
>>
>> The buffers that can include those key for navigation can be
>> help-mode, apropos-mode, woman, package-menu-mode (package listings),
>> compilation-mode, customize (Custom-mode), info-mode, and so on.
>
> Some of these keys are already bound in some of these modes. For
> example, h and l have bindings in help-mode.
>
> So I guess this could be some optional minor mode, off by default.
>
> Thanks.
view-mode has code for the k and j bindings, but commented out:
(defvar view-mode-map
(let ((map (make-sparse-keymap)))
...
(define-key map "q" 'View-quit)
...
;; (define-key map "k" 'View-scroll-line-backward)
(define-key map "y" 'View-scroll-line-backward)
;; (define-key map "j" 'View-scroll-line-forward)
...
(define-key map "o" 'View-scroll-to-buffer-end)
...
(define-key map "?" 'describe-mode) ; Maybe do as less instead? See above.
(define-key map "h" 'describe-mode)
next prev parent reply other threads:[~2016-08-14 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 6:52 bug#24224: Enable 'h, j, k, l' key navigation where ever possible Mohammed Sadik
2016-08-14 17:24 ` Eli Zaretskii
2016-08-14 18:10 ` npostavs [this message]
2020-08-22 18:45 ` Stefan Kangas
2020-10-01 12:38 ` Stefan Kangas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wpjjusq6.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=24224@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=sadiqpkp@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.