From: lawrence mitchell <wence@gmx.li>
Subject: Re: cua-mode clobbers S-<cursor>
Date: Sun, 05 Jan 2003 17:40:42 +0000 [thread overview]
Message-ID: <uel7r8pgl.fsf@ID-97657.usr.dfncis.de> (raw)
In-Reply-To: 84vg134i7s.fsf@lucy.cs.uni-dortmund.de
Kai Grossjohann wrote:
> I think I might like cua-mode a lot. Alas, I have my own bindings
> for S-<up> and S-<down> (they scroll by one line), which I need to
> move elsewhere. Alas, I can't think of another nicely mnemonic
> keybinding for them.
Hmm, now I'm intrigued as to what <up> and <down> do. Scroll by
page?
If you don't use numlock, you might find that you can use
<kp-{up,down}>, although they're a bit far away.
> Suggestions?
> Oh, it should be somewhere in the cursor keys region; I already have
> other bindings C-S-j and C-S-k for those cases where my hand is near
> the home row.
--
lawrence mitchell <wence@gmx.li>
next prev parent reply other threads:[~2003-01-05 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-05 17:30 cua-mode clobbers S-<cursor> Kai Großjohann
2003-01-05 17:40 ` lawrence mitchell [this message]
2003-01-05 19:28 ` Kai Großjohann
2003-01-14 14:20 ` Joe Casadonte
2003-01-14 15:27 ` Kai Großjohann
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=uel7r8pgl.fsf@ID-97657.usr.dfncis.de \
--to=wence@gmx.li \
/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).