From: Ian Zimmerman <bayard@newsguy.com>
Subject: Re: Browse skeleton positions
Date: 02 Nov 2003 08:10:31 -0800 [thread overview]
Message-ID: <87y8uy69ag.fsf@newsguy.com> (raw)
In-Reply-To: jwvoevxiam0.fsf-monnier+gnu.emacs.help@vor.iro.umontreal.ca
Stefan> How 'bout:
(defvar s-p-c-prefix [?\C-c ?+])
(defvar s-p-c-m-m
(let ((map (make-sparse-keymap)))
(define-key map s-p-c-prefix skeleton-position-mode-map)))
Stefan> So you avoid redundancy. The prefix variable is so that people
Stefan> can use another prefix (ESC is often a good choice for some
Stefan> users although it's a bad default choice).
Excellent idea, thanks.
--
"Rap music is our punishment for neglecting music education."
An anonymous teacher
next prev parent reply other threads:[~2003-11-02 16:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87vfqnygi7.fsf@newsguy.com>
2003-10-17 20:42 ` Browse skeleton positions Stefan Monnier
2003-10-18 17:58 ` Ian Zimmerman
2003-10-19 23:36 ` Stefan Monnier
2003-10-30 23:57 ` Ian Zimmerman
2003-10-31 17:28 ` Stefan Monnier
2003-11-02 16:10 ` Ian Zimmerman [this message]
2003-11-11 17:49 ` Ian Zimmerman
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=87y8uy69ag.fsf@newsguy.com \
--to=bayard@newsguy.com \
/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.
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).