From: Matthew Lundin <mdl@imapmail.org>
To: e.fraga@ucl.ac.uk
Cc: Matt Lundin <mdl@imapmail.org>, emacs-orgmode@gnu.org
Subject: Re: Re: RSI
Date: Fri, 11 Sep 2009 11:34:27 -0400 [thread overview]
Message-ID: <87vdjpcx6k.fsf@fastmail.fm> (raw)
In-Reply-To: <87my57gk5e.wl%ucecesf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 07 Sep 2009 10:48:45 +0100")
Eric S Fraga <ucecesf@ucl.ac.uk>, Eric S Fraga <ucecesf@ucl.ac.uk>
writes:
> At Tue, 01 Sep 2009 15:50:08 -0400,
> Matt Lundin wrote:
>> key. Thus, short of using viper, the only solution that works for me is
>> to use the Caps Lock key as Control. With that slight modification, I
>> find emacs controls *very* comfortable (perhaps even as comfortable than
>
> Yes, making caps lock act as control is key to using emacs without
> pain (for me). However, it's not a full solution for some keyboards
> which don't have a caps lock key. Therefore, I'm intrigued by your
> reference to viper: is it possible to use, constructively and easily,
> viper with org-mode? If so, any pointers on how to accomplish this
> would be fantastic! A modal approach to writing/editing is fine with
> me.
Well, I'm sorry to say that org-mode was the reason I abandoned viper.
It's probably a limitation of mine, but I found it too confusing to go
back and forth between all the C-c keys and viper's modal commands. I
also found the behavior of "dd" and the like to be unpredictable when
called on closed outline headings, drawers, etc. I much prefer the
behavior of C-k in org-mode's native keybindings. I imagine there are
others around here who have gotten it working.
IMO, viper is fine for relatively simple text modes. But for more
complex modes, I found it easier to stick with emacs' native
keybindings.
YMMV.
- Matt
next prev parent reply other threads:[~2009-09-11 15:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-01 18:11 RSI Samuel Wales
2009-09-01 18:16 ` RSI Samuel Wales
2009-09-01 18:22 ` RSI Keith Lancaster
2009-11-04 11:22 ` RSI Adam Spiers
2009-11-04 14:30 ` RSI Bill Powell
2009-09-01 18:22 ` RSI PT
2009-09-01 19:50 ` RSI Matt Lundin
2009-09-07 9:48 ` RSI Eric S Fraga, Eric S Fraga
2009-09-07 11:34 ` Alan E. Davis
2009-09-11 15:34 ` Matthew Lundin [this message]
2009-09-11 15:29 ` Eric S Fraga
2009-09-07 13:25 ` RSI B Smith-Mannschott
2009-09-07 17:16 ` RSI Daniel Martins
2009-09-07 19:48 ` RSI B Smith-Mannschott
2009-09-08 5:50 ` RSI PT
2009-09-08 8:05 ` RSI B Smith-Mannschott
[not found] <4AAD12BA.90105@alumni.ethz.ch>
2009-09-13 17:03 ` RSI Michael Brand
2009-09-13 20:42 ` RSI Dave Täht
2009-09-14 9:06 ` Eric S Fraga, Eric S Fraga
2009-09-15 0:56 ` Dave Täht
2009-09-15 9:20 ` Eric S Fraga
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vdjpcx6k.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).