all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: binding b-key to pageback behavior
Date: Thu, 28 Nov 2019 00:53:57 +0100	[thread overview]
Message-ID: <865zj4510q.fsf@zoho.eu> (raw)
In-Reply-To: m2v9r5v8z9.fsf@vogel.localnet

VanL wrote:

> I figure the modes all fall in ultimately in
> two boxes, either for reading or editing.

Absolutely, but you still need to mention the
individual modes (or maps) and whenever the
scrolling stuff differs, that has to be
explicit as well. So ultimately the result of
doing that wouldn't be all that different from
setting it up mode by mode.

But yes it would look something like what I've
already posted:

(defun set-vertical-keys (map)
  "Set MAP keys for moving point vertically."
  (define-key map "i" #'previous-line)
  (define-key map "k" #'next-line) )

> Having the license in the actual file like in
> 'rot13.el' is best, I believe.

Interesting, Gnus also does that, in
`gnus-summary-caesar-message'. Sounds like the
kind of pleasant thing one would like to write
in Elisp...

-- 
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal




  reply	other threads:[~2019-11-27 23:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-25  1:39 binding b-key to pageback behavior VanL
2019-11-25  2:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2019-11-25 11:02   ` VanL
2019-11-25 15:17     ` Emanuel Berg via Users list for the GNU Emacs text editor
2019-11-27 11:45       ` VanL
2019-11-27 23:53         ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2019-11-28  5:50           ` VanL
2019-11-28  6:34             ` Emanuel Berg via Users list for the GNU Emacs text editor

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=865zj4510q.fsf@zoho.eu \
    --to=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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.