From: Bob Marcum <bmarcum@Houston.rr.com>
Subject: Re: Autoload failed to define function mwheel-install
Date: Fri, 17 Dec 2004 07:58:27 -0600 [thread overview]
Message-ID: <41C2E603.78CC9C90@Houston.rr.com> (raw)
In-Reply-To: 523F0421-4F7A-11D9-8EDB-000D932A32C4@Web.DE
Peter Dyballa wrote:
> Am 16.12.2004 um 15:35 schrieb Bob Marcum:
>
> > ( autoload 'mwheel-install "mwheel" "Enable mouse wheel support" t)
> > (mwheel-install)
>
> Shouldn't this be handled by loaddefs.el and ldefs-boot.el? And you
> just use your mouse wheel ...
>
> --
> Greetings
>
> Pete
>
Frankly, Pete, ya got me. I haven't a clue. Are you suggesting a
specific solution?
If you are, please flush it out. Show me how.
next prev parent reply other threads:[~2004-12-17 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.14444.1103163918.27202.help-gnu-emacs@gnu.org>
2004-12-16 14:35 ` Autoload failed to define function mwheel-install Bob Marcum
2004-12-16 15:51 ` Peter Dyballa
2004-12-17 13:58 ` Bob Marcum [this message]
2004-12-26 23:04 ` Kai Grossjohann
[not found] ` <mailman.6541.1103208307.27204.help-gnu-emacs@gnu.org>
2004-12-27 17:19 ` Kevin Rodgers
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=41C2E603.78CC9C90@Houston.rr.com \
--to=bmarcum@houston.rr.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).