From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: keybinding trouble
Date: Fri, 08 Feb 2013 17:43:21 +0100 [thread overview]
Message-ID: <87liaykb86.fsf@web.de> (raw)
In-Reply-To: <mailman.19346.1360341084.855.help-gnu-emacs@gnu.org> (Frederik's message of "Fri, 08 Feb 2013 17:31:07 +0100")
Frederik <freak.fred@gmail.com> writes:
> (eval-after-load 'flyspell-mode
> '(define-key flyspell-mode-map (kbd "C-c f")
> 'flyspell-auto-correct-previous-word))
Please have a look at the doc of `eval-after-load'. Your first argument
'flyspell-mode is not a name of a file or feature. You want 'flyspell
or "flyspell".
Regards,
Michael.
next parent reply other threads:[~2013-02-08 16:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.19346.1360341084.855.help-gnu-emacs@gnu.org>
2013-02-08 16:43 ` Michael Heerdegen [this message]
2013-02-08 16:31 keybinding trouble Frederik
2013-02-08 16:40 ` Drew Adams
2013-02-08 17:01 ` Frederik
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=87liaykb86.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).