From: Paul Johnson <baloo@ursine.ca>
Subject: SOLVED: keydef issues
Date: Thu, 05 Aug 2004 23:52:17 GMT [thread overview]
Message-ID: <87oelpgn37.fsf_-_@ursine.ca> (raw)
In-Reply-To: <86acxac61p.fsf@ID-110038.user.uni-berlin.de>
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
raphael.berbain@free.fr (Raphaël Berbain) writes:
> Paul Johnson <baloo@ursine.ca> writes:
>> byte-code: Error in ~/.gnus: keydef
>
> Ah, that's because I am using the keydef package to define my keys.
> Either grab it from http://www.anc.ed.ac.uk/~stephen/emacs/ell.html,
> or use this:
>
> (define-key gnus-group-mode-map (kbd "d") 'rgb/gnus-agent-get)
I think that's my new favorite way to remap keys. Thanks!
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
parent reply other threads:[~2004-08-05 23:52 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <86acxac61p.fsf@ID-110038.user.uni-berlin.de>]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oelpgn37.fsf_-_@ursine.ca \
--to=baloo@ursine.ca \
/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 NNTP newsgroup(s).