From: Colin Marquardt <c.marquardt@alcatel.de>
Subject: Re: strokes.el revamp
Date: Tue, 30 Apr 2002 12:43:05 +0200 [thread overview]
Message-ID: <k8zadrltqkm.fsf@alcatel.de> (raw)
In-Reply-To: rzqd6wh4j90.fsf@djlvig.dl.ac.uk
d.love@dl.ac.uk (Dave Love) writes:
> My previous hack at strokes.el obviously didn't produce something
> usable. The original overloading of mouse-2 just loses and presumably
> no-one uses it. The following seems better and potentially useful for
> input of technical characters, for instance. I suspect the doc and
> commentary needs more review than I've given it.
[...]
> @@ -116,7 +118,7 @@
> ;; Whenever you load in the strokes package, you will be able to save
> ;; what you've done upon exiting Emacs. You can also do
>
> -;; > M-x save-strokes
> +;; > M-x strokes-propmpt-user-save-strokes
-----------------------^
Small typo.
Colin
prev parent reply other threads:[~2002-04-30 10:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-30 9:40 strokes.el revamp Dave Love
2002-04-30 10:43 ` Colin Marquardt [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=k8zadrltqkm.fsf@alcatel.de \
--to=c.marquardt@alcatel.de \
/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).