From: Xah Lee <xahlee@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: elpa package loading problem?
Date: Thu, 29 Nov 2012 20:53:44 -0800 (PST) [thread overview]
Message-ID: <d60d8ce1-ff52-42d0-ad36-5b109c367766@me7g2000pbb.googlegroups.com> (raw)
In-Reply-To: mailman.14118.1354247749.855.help-gnu-emacs@gnu.org
On Nov 28, 11:09 pm, Easior <eas...@126.com> wrote:
> …
> It's just my question.
>
> However, I also found something strange with package.el in emacs 24.
> I installed command-frequency.el, info+.el, maxfame.el etc, byelpa.
> Those package couldn't load properly if I add the following lines:
>
> ,------------------------------------------------
> | (require 'command-frequency)
> | (eval-after-load "info" '(require 'info+))
> | (require 'maxframe)
> | (add-hook 'window-setup-hook 'maximize-frame t)
> `------------------------------------------------
>
> to the file ~/.emacs. The *Bugtrace* reports that
>
> If I adjust my dotemacs file as follows
>
> ,------------------------------------------------
> | ;; (require 'command-frequency)
> | ;; (eval-after-load "info" '(require 'info+))
> | ;; (require 'maxframe)
> | (add-hook 'window-setup-hook 'maximize-frame t)
> `------------------------------------------------
>
> then the maxframe.el works well while command-frequency.el and
> info+.el didn't take any effects. I found those files named
> <package>-<autoloads>.el when I entered into theelpadirectory.
> Based on these facts, I understand that
>
> * packages installed byelpacouldn't required in ~/.emacs since
> they would be autoloaded through the autoloads files. Furthermore,
> the autoloads files are generated from the ;;##autoload lines in
> package sources.
> * maxfame.el works since the function, maximize-frame, is in the
> autoloads file.
> * command-frequency.el doesn't work because there is nothing in its
> autoloads file.
>
> Is it right?
>
> Question:
>
> Is there a way to make info+.el, command-frequency.el run byelpa?
> What can I do?
>
> Thanks in advance.
>
> Best regards,
>
> Easior
> -----
> Ich bin von heute und ehedam, aber etwas ist in mir, das ist vor
> morgen und übermorgen und einstmal.
>
> Friedrich Wilhelm Nietzsche
in general, you want to do
(package-initialize)
first before trying to do any config for packages from the package
system.
See update here, bottom:
〈Emacs 24 Package System Problems〉
http://ergoemacs.org/emacs/emacs_package_system_problem.html
also, i recommend using MELPA.
〈A Guide on Emacs 24 Package System〉
http://ergoemacs.org/emacs/emacs_package_system.html
command-frequency is obsolete. New is keyfreq.el. Please see bottom:
〈Emacs's Command Frequency〉
http://ergoemacs.org/emacs/command-frequency.html
Xah
prev parent reply other threads:[~2012-11-30 4:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 16:44 elpa package loading problem? Xah Lee
2012-06-04 8:58 ` José A. Romero L.
2012-06-04 19:18 ` José A. Romero L.
2012-06-04 23:09 ` Xah Lee
2012-11-29 7:09 ` Easior
2012-11-30 4:18 ` Jude DaShiell
[not found] ` <mailman.14118.1354247749.855.help-gnu-emacs@gnu.org>
2012-11-30 4:53 ` Xah Lee [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=d60d8ce1-ff52-42d0-ad36-5b109c367766@me7g2000pbb.googlegroups.com \
--to=xahlee@gmail.com \
--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).