From: Peter Heslin <public@heslin.eclipse.co.uk>
Subject: Re: For advanced CUA users: cua-movement-commands is gone.
Date: Mon, 7 Feb 2005 18:29:04 +0000 (UTC) [thread overview]
Message-ID: <cu8c1g$li$1@sea.gmane.org> (raw)
In-Reply-To: m3acqgk2kh.fsf@kfs-l.imdomain.dk
On 2005-02-07, Kim F. Storm <storm@cua.dk> wrote:
>
> With my latest changes to cua mode in CVS emacs, the
> cua-movement-commands variable has been removed in favour
> of a much cleaner approach.
Thanks for the warning. I suggest that you post this as well to
places like comp.emacs and gnu.emacs.help, since there are so many
non-developers using CVS emacs at this point.
On at least on occasion, I have answered a question in one of those
groups with reference to customizing cua-movement-commands.
Peter
prev parent reply other threads:[~2005-02-07 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 11:54 For advanced CUA users: cua-movement-commands is gone Kim F. Storm
2005-02-07 18:29 ` Peter Heslin [this message]
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='cu8c1g$li$1@sea.gmane.org' \
--to=public@heslin.eclipse.co.uk \
/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.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).