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

Kalle Olavi Niemitalo <> writes:

> 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:

I think it is more convenient to set the path explicitly in the init file
than to specify it with the configure program, unless we automatically
install all scheme programs in that directory and most users are just to
use them.  Should we really do this right now?

(I personally add the local cvs directory to %load-path, so I don't need
to install scheme files.)

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

This is a good idea.  But ~/.emacs.scm is still beneficial as an example
of how to use/setup Guile Emacs.

I haven't have time to work on Guile Emacs these days and will not for
more one month...  Since you Kalle have added some useful features,
including complete-symbol and import-macro, I would like to release
Guile Emacs 0.3.  Could you write some documentation, especially NEWS
file as a function introduction for that?

-- Kei

  reply	other threads:[~2000-03-26 10:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-26  8:45 Kalle Olavi Niemitalo
2000-03-26 10:51 ` Keisuke Nishida [this message]
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 \ \ \ \ \

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