unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: VanL <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: binding b-key to pageback behavior
Date: Wed, 27 Nov 2019 22:45:14 +1100	[thread overview]
Message-ID: <m2v9r5v8z9.fsf@vogel.localnet> (raw)
In-Reply-To: 864kysasu8.fsf@zoho.eu

Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:

> VanL wrote:
>
>>>> Is there a general configuration to bind
>>>> b-key to pageback?
>>>
>>> Well, how would that work? In your code, it
>>> isn't even the same function, it is
>>> `scroll-down-command', then its
>>> `View-scroll-page-backward'... And even if
>>> it did, after evaluating it one wouldn't be
>>> able to write this very message!
>>
>> Those modes the customization is done to are
>> for reading only in the main.
>
> I thought by "general" you meant you looked for
> a way to do it without stating the specific
> modes and/or functions?

I was meaning 'general' in the sense where SPC
functions to scroll, there, I'd like for b-key
to scroll the other way.

> If that's not what you meant, what is a general
> configuration to bind a specific key to
> a concept, which is implemented differently in
> different modes?

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

>> SPC behaves as expected there and I look for
>> the reverse binding to apply to b.
>
> Do `C-h k SPC' to find out what SPC does.
> Use this to figure out the name of the reverse
> function. Bind this to b:
>
> (require 'mode)
> (define-key mode-map "b" #'function-name)
>

Ah, that is neat and short.  Thanks.

>> Thanks for the suggestions. Are you able to
>> put a LICENSE on your code?
>>
>> For example, I keep a CC0 empty file and..
>
> CC0 = Creative Commons 1.0?

I believe that one is desireable for
documentation.

> Well, I haven't read the small print...
>
> Is it enough if I put one file in the base
> directory of all my Elisp?

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

-- 
əə0@ 一 二 三 言 語 𝔖
'VLIW architecture?'




  reply	other threads:[~2019-11-27 11:45 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 [this message]
2019-11-27 23:53         ` Emanuel Berg via Users list for the GNU Emacs text editor
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

  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=m2v9r5v8z9.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).