unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Benjamin Badgley <mortecanine@peoplepc.com>
To: help-gnu-emacs@gnu.org
Subject: RE: How to get skills in elisp ?
Date: Thu, 28 May 2009 03:09:10 -0400	[thread overview]
Message-ID: <4A1E3896.7050906@peoplepc.com> (raw)


Not flaming Drew, only stating fact. I still use a dial up with a serial 
modem. It's okay for our needs presently. Rather, it needs to be.

That aside, I have been delving into the lovely world of load path. 
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? Not 
sure where to go to set it for Emacs itself. My dot emacs file evaluates 
out the long path listing.

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)

That will cut down load time. If I keep the original dot emacs then, I 
can add / subtract and recompile as needed. Besides that it'll save 
running into evaluation errors when it loads a simple one or two line 
dot emacs file.

However, that darn load path issue bugs me. And I may be taking the long 
way home. Please let me if that's the case, it's how I learn. But no 
need to indulge stupidity either, if you can offer some help, pointers 
please do.

So far my favorite line of code is the one below.

(setq inhibit-startup-message t)

And I also enjoy:

(add-to-list 'load-path 
"/usr/share/emacs/site-lisp/emacs-goodies-el/color-theme.el")
(require 'color-theme)
(eval-after-load "color-theme-wheat"
  (progn (color-theme-hober))

As for finding useful documentation, I find myself doing a  C-h i a lot. 
It helped get me started on hacking the dot emacs file. I stumbled over 
the Emacs FAQ via the C-h i key-chord.  With auto decompress on in Emacs 
you can read compressed info files just swell. I bet it would also work 
on those pesky compressed man pages, too. ;)

Well, I ought to be scooting along. Need to break tomorrow, do some 
writing instead of coding.  Nitol, run it slow.  :)

;;; Ben





             reply	other threads:[~2009-05-28  7:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28  7:09 Benjamin Badgley [this message]
2009-05-28 15:55 ` How to get skills in elisp ? Drew Adams
  -- 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=4A1E3896.7050906@peoplepc.com \
    --to=mortecanine@peoplepc.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).