From: Michael Brand <michael.brand@alumni.ethz.ch>
To: emacs-orgmode@gnu.org
Subject: Re: Re: Re: RSI
Date: Sun, 13 Sep 2009 19:03:44 +0200 [thread overview]
Message-ID: <4AAD25F0.50309@alumni.ethz.ch> (raw)
In-Reply-To: <4AAD1565.90106@alumni.ethz.ch>
Eric S Fraga wrote:
> ... Therefore, I'm intrigued by your
> reference to viper: is it possible to use, constructively and easily,
> viper with org-mode? ...
For me definitely yes. org-mode (which I use for a few months) and viper-mode (which I use for two years) are both too good for me to abandon one in favor of the other, they are even the two most important and valuable modes in Emacs for me (beside calc which I also value most but don't need for "real work"). I find viper-mode comfortable even in "Editable Dired" mode (C-x C-q when in Dired).
To cut a hidden region to the clipboard like a closed heading or drawer one can use either C-k or unhide it and cut as a region (`m x C-f p d ' x' in org-mode and viper-mode). Remember that a region can be moved very easily within the same file with S-M-up or S-M-down repeatedly.
There is no necessity for me to abandon viper-mode as a whole if some things don't work with e. g. org-mode. E. g. sometimes when I edit a org table cell then the viper-mode commands `c e' behaves erroneously like `i'. But here one can use a workaround like `d e i' and this is not happening outside org tables. I fear that the viper-mode is still used by too few people so that things like that are unlikely to be fixed in org-mode.
Beside this, viper-mode for me works with org-mode like with all other modes I used it before.
- Michael
next parent reply other threads:[~2009-09-13 17:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4AAD1565.90106@alumni.ethz.ch>
2009-09-13 17:03 ` Michael Brand [this message]
2009-09-14 19:35 ` Re: Re: Re: RSI Eric S Fraga, 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AAD25F0.50309@alumni.ethz.ch \
--to=michael.brand@alumni.ethz.ch \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.