public inbox for
 help / color / mirror / Atom feed
From: Kalle Olavi Niemitalo <>
Subject: automating %load-path
Date: Sun, 26 Mar 2000 08:45:00 -0000	[thread overview]
Message-ID: <87og81zwk3.fsf@PC486.Niemitalo.LAN> (raw)

I would like to make Guile Emacs automatically insert its Scheme
directories in the %load-path of Guile, so that users don't have
to do that in ~/.emacs.scm.  My plan:

1. Add a new variable $schemepath in

2. Add a new macro PATH_SCMLOADSEARCH in src/  If we
   don't support Scheme in temacs, we don't need

3. Make the epaths-force target in store $schemepath
   in epaths.h.

4. Make init_guileapi() in src/guileapi.c add the
   PATH_SCMLOADSEARCH directories in %load-path.  I'm not very
   familiar with Guile's C API but I'll learn.  :-)

5. Create a new module (emacs init) and place all Scheme
   initialization code there.  This could load (emacs io).

6. Load (emacs init) from lisp/startup.el.

The Emacs files src/ and would have to be
added in CVS.  I currently have only Emacs 20.5, not 20.6 so
could you add those files, Keisuke?  I can insert the
modification comments.

             reply	other threads:[~2000-03-26  8:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-26  8:45 Kalle Olavi Niemitalo [this message]
2000-03-26 10:51 ` Keisuke Nishida
2000-03-27  9:08   ` Kalle Olavi Niemitalo
2000-03-27 17:28     ` Keisuke Nishida
2000-03-29  2:33       ` before the 0.3 release (was %load-path) Kalle Olavi Niemitalo
2000-04-09 12:46 ` Makefile preprocessing trouble " Kalle Olavi Niemitalo
2000-04-10  3:47   ` Kalle Olavi Niemitalo
2000-04-14  0:29 ` automating %load-path Kalle Olavi Niemitalo
2000-04-29  1:21   ` Kalle Olavi Niemitalo
2000-04-29  1:46     ` Keisuke Nishida
2000-04-29 11:37       ` Kalle Olavi Niemitalo
2000-04-29 12:27         ` Keisuke Nishida

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87og81zwk3.fsf@PC486.Niemitalo.LAN \ \ \

* 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).