unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Benjamin Badgley'" <mortecanine@peoplepc.com>,
	<help-gnu-emacs@gnu.org>
Subject: RE: How to get skills in elisp ?
Date: Thu, 28 May 2009 08:55:23 -0700	[thread overview]
Message-ID: <2EC05CEBE6564DA69EC14ACEAD8E16D3@us.oracle.com> (raw)
In-Reply-To: <4A1E3896.7050906@peoplepc.com>

> Seems I've gotten a rather long group listing for a load 
> path. Any ideas on how to wrangle it back down to perhaps
> two or so directories?

Put the code you need in just those two or so directories. ;-)

Just what is the problem you have with a long `load-path'? 

> Not sure where to go to set it for Emacs itself. My dot emacs 
> file evaluates out the long path listing.

Dunno what you mean ("for Emacs itself"=?, "evaluates out"=?).

Set your `load-path' in your init file (.emacs) or in some file that you load
from your init file.

> I want to finish hacking the dot emacs and then byte compile 
> it, set a new dot emacs up.
> ;;; Included in the new dot emacs
> (require 'emacs-source.elc)

Yes, that's fine. But use just (require 'emacs-source). And you will need to put
(provide 'emacs-source) somewhere in emacs-source.el.

But don't bother to byte-compile your init file (.emacs). Keep it short and
sweet. Let it load other stuff (e.g. emacs-source.elc) that loads other stuff.
The other stuff can be byte-compiled.

> However, that darn load path issue bugs me. 

I don't understand what the issue is. What's wrong with the path being long?

> (add-to-list 'load-path 
> "/usr/share/emacs/site-lisp/emacs-goodies-el/color-theme.el")

Just use /usr/share/emacs/site-lisp/emacs-goodies-el - no need to mention any
individual files you want to load. Assuming the order of directories in your
`load-path' is what you want, you should be able to just have directories there.

`load-path' tells Emacs where to look. `load-library', `load', `load-file', and
`require' tell Emacs which libraries to load. It will look for them by
consulting `load-path'.

HTH.





  reply	other threads:[~2009-05-28 15:55 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  7:09 How to get skills in elisp ? Benjamin Badgley
2009-05-28 15:55 ` Drew Adams [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-05-25  7:30 Francis Moreau
2009-05-25  8:17 ` Drew Adams
     [not found] ` <mailman.7753.1243239425.31690.help-gnu-emacs@gnu.org>
2009-05-25  9:15   ` Francis Moreau
2009-05-25 10:22     ` Pascal J. Bourguignon
2009-05-25 11:50     ` Andreas Röhler
2009-05-25 12:42     ` Richard Riley
2009-05-25 13:51       ` Pascal J. Bourguignon
2009-05-25 14:18         ` Richard Riley
2009-05-26  7:58       ` Francis Moreau
2009-05-25 17:11     ` Drew Adams
     [not found]     ` <mailman.7774.1243271469.31690.help-gnu-emacs@gnu.org>
2009-05-25 19:41       ` Francis Moreau
2009-05-25 20:52         ` Drew Adams
2009-05-25 10:04 ` Tassilo Horn
2009-05-25 11:01 ` Pascal J. Bourguignon
2009-05-25 12:03   ` Andreas Röhler
2009-05-27 13:05   ` Thien-Thi Nguyen

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=2EC05CEBE6564DA69EC14ACEAD8E16D3@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=mortecanine@peoplepc.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).