From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: [patch] Very minor issue with CUA mode
Date: Mon, 02 May 2005 00:35:23 +0200 [thread overview]
Message-ID: <m31x8qmv6c.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87vf65t9ii.fsf@wigwam.deepwood.net> (Daniel Brockman's message of "Sat, 30 Apr 2005 02:04:37 +0200")
Daniel Brockman <daniel@brockman.se> writes:
> Download cua.el from cua.dk and put it in ~/cua.el.
> Then do emacs -q RET M-x load-file RET ~/cua.el RET. BANG.
>
> I should say that I didn't test the above patch, and to be honest, I
> couldn't figure out how to do it! It seems that the autoload code is
> somehow cached so that changing it in the Lisp file doesn't work.
You need to make bootstrap to test it.
I installed the patch, thanks.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
prev parent reply other threads:[~2005-05-01 22:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 0:04 [patch] Very minor issue with CUA mode Daniel Brockman
2005-05-01 22:35 ` 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=m31x8qmv6c.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).