From: Tassilo Horn <tassilo@member.fsf.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Cut and open commands?
Date: Sat, 23 Feb 2008 18:22:36 +0100 [thread overview]
Message-ID: <87zltrfuzn.fsf@member.fsf.org> (raw)
In-Reply-To: fpp5og$5nn$1@news.net.uni-c.dk
saneman <asdfsdf@asd.com> writes:
> I would like to redefine cut and open to: C-x and C-o regardless of
> the built in definitions.
Don't cripple your emacs yourself, use cua-mode.
,----[ C-h f cua-mode RET ]
| cua-mode is an interactive autoloaded Lisp function in `cua-base'.
|
| It is bound to <menu-bar> <options> <cua-mode>, <menu-bar> <options>
| <cua-emulation-mode>.
|
| (cua-mode &optional ARG)
|
| Toggle CUA key-binding mode.
| When enabled, using shifted movement keys will activate the
| region (and highlight the region using `transient-mark-mode'),
| and typed text replaces the active selection.
|
| Also when enabled, you can use C-z, C-x, C-c, and C-v to undo,
| cut, copy, and paste in addition to the normal Emacs bindings.
| The C-x and C-c keys only do cut and copy when the region is
| active, so in most cases, they do not conflict with the normal
| function of these prefix keys.
|
| If you really need to perform a command which starts with one of
| the prefix keys even when the region is active, you have three
| options:
| - press the prefix key twice very quickly (within 0.2 seconds),
| - press the prefix key and the following key within 0.2 seconds, or
| - use the SHIFT key with the prefix key, i.e. C-S-x or C-S-c.
|
| You can customize `cua-enable-cua-keys' to completely disable the
| CUA bindings, or `cua-prefix-override-inhibit-delay' to change
| the prefix fallback behavior.
|
| CUA mode manages Transient Mark mode internally. Trying to disable
| Transient Mark mode while CUA mode is enabled does not work; if you
| only want to highlight the region when it is selected using a
| shifted movement key, set `cua-highlight-region-shift-only'.
`----
Bye,
Tassilo
--
People sometimes ask me if it is a sin in the Church of Emacs to use
vi. Using a free version of vi is not a sin; it is a penance. So happy
hacking. (Richard M. Stallman)
next prev parent reply other threads:[~2008-02-23 17:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-23 13:06 Cut and open commands? saneman
2008-02-23 13:28 ` saneman
2008-02-23 17:22 ` Tassilo Horn [this message]
[not found] ` <mailman.7830.1203787374.18990.help-gnu-emacs@gnu.org>
2008-02-25 10:02 ` saneman
2008-02-25 17:07 ` Joel J. Adamson
2008-02-25 19:38 ` saneman
2008-02-25 20:45 ` Joel J. Adamson
2008-02-25 22:27 ` saneman
2008-02-26 7:51 ` Thierry Volpiatto
[not found] ` <mailman.7948.1204011578.18990.help-gnu-emacs@gnu.org>
2008-02-26 9:12 ` saneman
2008-02-26 9:17 ` saneman
2008-02-26 16:45 ` Joel J. Adamson
2008-02-27 9:04 ` saneman
2008-02-27 14:53 ` Joel J. Adamson
2008-02-28 4:58 ` Kevin Rodgers
2008-02-25 22:46 ` Peter Dyballa
2008-02-25 18:15 ` Sven Joachim
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=87zltrfuzn.fsf@member.fsf.org \
--to=tassilo@member.fsf.org \
--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).