unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Subject: For advanced CUA users: cua-movement-commands is gone.
Date: Mon, 07 Feb 2005 12:54:38 +0100	[thread overview]
Message-ID: <m3acqgk2kh.fsf@kfs-l.imdomain.dk> (raw)


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.

If you have code relying on this, you need to adapt your code
to the new method of marking a command as a movement command:

  (put 'your-command 'CUA 'move)

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

             reply	other threads:[~2005-02-07 11:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-07 11:54 Kim F. Storm [this message]
2005-02-07 18:29 ` For advanced CUA users: cua-movement-commands is gone Peter Heslin

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=m3acqgk2kh.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    /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).