From: "Vyacheslav Akhmechet" <coffeemug@gmail.com>
Subject: Re: Arrowless navigation
Date: Thu, 21 Sep 2006 13:46:32 -0400 [thread overview]
Message-ID: <b381ea40609211046t511224deu3b196331f89edb31@mail.gmail.com> (raw)
In-Reply-To: <877izx5e3y.fsf@robotron.kosmorama>
I just switched my CapsLock and control keys and I'm running into
problems. It's actually ok within emacs but I can't edit everything
there all the time and having to use CapsLock with c and v to
copy/paste in other pieces of software is a big pain. In general it
seems like default emacs bindings / conventions aren't very ergonomic.
Makes me consider trying VI :)
On 9/21/06, David Hansen <david.hansen@gmx.net> wrote:
> On Thu, 21 Sep 2006 11:17:44 -0400 Vyacheslav Akhmechet wrote:
>
> > I recently disabled the arrow keys to avoid temptation. However, I
> > find that default navigation is fairly uncomfortable: C-f, C-b, C-n,
> > C-p. The keys are far away from each other and navigating like that is
> > really stressful on the fingers. Why is this done this way?
> >
> > Do most people redefine these bindings? Initially I wanted to redefine
> > to C-j, C-k, C-l and C-i (because they resemble the arrow keys and are
> > close to the home row) but some of the most common emacs bindings are
> > there. So how do the pros navigate?
>
> I use C-f and friends. I'm so used to it...
>
> But if you like to have some other cursor movement commands
> w/o overwriting important emacs key bindings you can either
> use these windows keys as a modifier or do some key mapping
> magics with xmodmap.
>
> A quite common setup is to use CapsLock as the control key and
> the left control key as another modifier.
>
> David
>
>
>
> _______________________________________________
> help-gnu-emacs mailing list
> help-gnu-emacs@gnu.org
> http://lists.gnu.org/mailman/listinfo/help-gnu-emacs
>
next prev parent reply other threads:[~2006-09-21 17:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 15:17 Arrowless navigation Vyacheslav Akhmechet
2006-09-21 15:35 ` Drew Adams
2006-09-21 17:22 ` David Hansen
2006-09-21 17:46 ` Vyacheslav Akhmechet [this message]
2006-09-21 20:06 ` Xavier Maillard
[not found] ` <b381ea40609212121o56de31e6xa96285dc861a5ab0@mail.gmail.com>
2006-09-22 4:22 ` Vyacheslav Akhmechet
[not found] ` <mailman.7258.1158898978.9609.help-gnu-emacs@gnu.org>
2006-09-22 9:31 ` Tim X
2006-09-21 20:05 ` Xavier Maillard
2006-09-22 12:08 ` David Hansen
[not found] ` <mailman.7249.1158869692.9609.help-gnu-emacs@gnu.org>
2006-09-21 21:12 ` Jochem Huhmann
2006-09-23 15:39 ` Dieter Wilhelm
[not found] ` <mailman.7295.1159072918.9609.help-gnu-emacs@gnu.org>
2006-10-14 23:13 ` David Combs
2006-10-15 9:42 ` Dieter Wilhelm
2006-09-22 14:20 ` Giles Chamberlin
2006-09-22 22:11 ` Xavier Maillard
2006-09-21 20:02 ` Xavier Maillard
[not found] ` <mailman.7237.1158859969.9609.help-gnu-emacs@gnu.org>
2006-10-14 23:07 ` David Combs
[not found] <mailman.7231.1158851870.9609.help-gnu-emacs@gnu.org>
2006-09-22 6:46 ` Florian Kaufmann
2006-09-22 9:21 ` Tim X
2006-09-22 16:23 ` don provan
2006-09-22 21:17 ` Kevin Rodgers
2006-09-24 22:02 ` David Golden
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=b381ea40609211046t511224deu3b196331f89edb31@mail.gmail.com \
--to=coffeemug@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.
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).