From: VanL <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: binding b-key to pageback behavior
Date: Thu, 28 Nov 2019 16:50:59 +1100 [thread overview]
Message-ID: <m2r21sv9a4.fsf@vogel.localnet> (raw)
In-Reply-To: 865zj4510q.fsf@zoho.eu
Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:
> 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.
In a more perfect world DWIM Mode just works.
> 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) )
I cargo culted the two liner and it
broke Emacs's startup. Will see how
this goes. Thanks.
>> 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...
C17's draft N2176 page 13 point 14 is an unpleasant shocker.
--
LoL,
əə0@ 一 二 三 言 語 𝔖
'VLIW architecture?'
G4 White 78 Black 79
next prev parent reply other threads:[~2019-11-28 5:50 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
2019-11-28 5:50 ` VanL [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2r21sv9a4.fsf@vogel.localnet \
--to=van@scratch.space \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).