From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: crisp movement versus cua
Date: Thu, 19 May 2005 10:07:33 +0200 [thread overview]
Message-ID: <m3u0kzmyey.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <878y2cxilj.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 19 May 2005 08:41:28 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> crisp.el seems to be still using cua--standard-movement-commands which
> was recently removed. Eg,
>
> M-x cua-mode
> M-x crisp-mode
> => Symbol's value as variable is void: cua--standard-movement-commands
>
> I only noticed this when trying some autoloads, I don't use either
> myself. The new style is meant to be for crisp to set a property on
> its commands, or something, is it?
I installed a fix. Thanks.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
prev parent reply other threads:[~2005-05-19 8:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 22:41 crisp movement versus cua Kevin Ryde
2005-05-19 8:07 ` Kim F. Storm [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=m3u0kzmyey.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@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 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).