From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: Stefan Monnier <monnier-TBKEPPAhkIr7qOVTksikzQ@public.gmane.org>
Cc: 15272-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org
Subject: bug#15272: 24.3.50; Cannot open load file tex-site
Date: Thu, 05 Sep 2013 15:17:01 +0200 [thread overview]
Message-ID: <86a9jr2ysy.fsf@somewhere.org> (raw)
In-Reply-To: <mailman.1355.1378385600.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org> (Stefan Monnier's message of "Thu, 05 Sep 2013 08:52:22 -0400")
Stefan Monnier wrote:
>> Using the latest one compiled by Dani (r114118), I have the following error:
>> --8<---------------cut here---------------start------------->8---
>> (info) Loading `d:/Users/fni/src/emacs-leuven/.emacs-minimal.el'...
>> M1
>> M2
>> eval-buffer: Cannot open load file: no such file or directory, tex-site
>> --8<---------------cut here---------------end--------------->8---
>
> Hmm... indeed I see that loading files from the <pkg>-autoloads.el is
> more common than I thought.
Please confirm or infirm this: They way I do use package is the right one?
--8<---------------cut here---------------start------------->8---
(require 'package)
;; archives from which to fetch
(setq package-archives
(append '(("org" . "http://orgmode.org/elpa/")
("melpa" . "http://melpa.milkbox.net/packages/")
("marmalade" . "http://marmalade-repo.org/packages/"))
package-archives))
(package-initialize)
--8<---------------cut here---------------end--------------->8---
I had read, somewhere, that `package-initialize' wasn't necessary as it now
*would* be done automatically (by Emacs) after the init is eval'ed.
Is this true?
Anyway, I've got the feeling it's too late: some packages must be loaded
before my customizations; for example, if I want to add something to a list
(which wouldn't exist yet, except if I protect all my code chunks in
eval-after-load constructions).
> You can work around the problem by re-installing auctex, and I'll fix it
> in the trunk so reinstalling is not needed.
Answer with the next Windows binary...
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-09-05 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-05 9:00 bug#15272: 24.3.50; Cannot open load file tex-site Sebastien Vauban
2013-09-05 9:29 ` Eli Zaretskii
2013-09-05 12:52 ` Stefan Monnier
[not found] ` <mailman.1344.1378373419.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.1344.1378373419.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-09-05 13:11 ` Sebastien Vauban
2013-09-05 14:20 ` Eli Zaretskii
[not found] ` <mailman.1355.1378385600.10748.bug-gnu-emacs@gnu.org>
[not found] ` <mailman.1355.1378385600.10748.bug-gnu-emacs-mXXj517/zsQ@public.gmane.org>
2013-09-05 13:17 ` Sebastien Vauban [this message]
2013-09-05 15:33 ` Stefan Monnier
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=86a9jr2ysy.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=15272-ubl+/3LiMTaZdePnXv/OxA@public.gmane.org \
--cc=monnier-TBKEPPAhkIr7qOVTksikzQ@public.gmane.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).