From: Drew Adams <drew.adams@oracle.com>
To: Michele Bert <micbert75@gmail.com>, help-gnu-emacs@gnu.org
Subject: RE: C-x keystroke changed at runtime
Date: Tue, 20 Sep 2016 07:23:12 -0700 (PDT) [thread overview]
Message-ID: <60e3291e-30fd-4d68-b023-8be8d4c35f8b@default> (raw)
In-Reply-To: <CACE4N+X+9-aEFi2M9JWLpd82ZA8O3aemYruJ7BKP3CPuvMYOwQ@mail.gmail.com>
> I use Emacs (23.3.1 on Ubuntu 12.04) in my daily work, and I can
> assert I know it _quite_ well. Allthough today something very strange
> has happened.
>
> After more than 1 week that it has been running (continuosly: I use to
> leave it always open, even during the night, opening and closing
> buffers, creating new frames, even with aid of emacsclient), suddenly
> (few minutes ago) the C-x keystroke has changed behavior: whenever
> there is an active region, it kills the selected text (just like C-w),
> while if there isn't any region, it acts as a prefix for the usual
> keystrokes (I can visit a file with C-x, C-f, or save it with C-x,
> C-s, or change buffer with C-x, b, for example). But with an active
> region it kills it instantly.
>
> I am going to restart the program, but before doing it, I would be
> very curious to understand what is happening, so if anyone has a
> suggestion about some tests or checks I can do, I would appreciate.
What does `C-h v cua-mode' tell you?
Sounds like `cua-mode' is turned on. Perhaps you have installed
a package or other Emacs-Lisp code that automatically turns on
`cua-mode', or perhaps you turned it on, yourself.
Normally, just _loading_ a library should not turn anything
on (and should not change global key bindings). Alas, this
is not always the case.
next prev parent reply other threads:[~2016-09-20 14:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 8:42 C-x keystroke changed at runtime Michele Bert
2016-09-20 14:22 ` Yuri Khan
2016-09-20 14:57 ` Michele Bert
2016-09-20 14:23 ` Drew Adams [this message]
2016-09-20 14:47 ` Eli Zaretskii
2016-09-20 14:59 ` Michele Bert
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=60e3291e-30fd-4d68-b023-8be8d4c35f8b@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=micbert75@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).