From: Keisuke Nishida <firstname.lastname@example.org>
Subject: Re: automating %load-path
Date: Sat, 29 Apr 2000 12:27:00 -0000 [thread overview]
Message-ID: <email@example.com> (raw)
Kalle Olavi Niemitalo <firstname.lastname@example.org> writes:
> Before my emacs/init.scm changes, .emacs.scm used to be loaded in
> the root module. When .emacs.scm used modules such as (emacs
> guile), the public commands defined there were imported to the
> root module and the Lisp side could find them.
> Nowadays, .emacs.scm is loaded from emacs/init.scm so the root
> module is not current. If .emacs.scm uses (emacs guile), its
> variables get imported to (emacs init). The Lisp stubs defined
> by `define-command' couldn't find them from there.
> One could have worked around this problem by making
> emacs/init.scm switch to the root module before loading
> .emacs.scm. But I think my solution is better, as it also takes
> care of the case where .emacs.scm uses one module which uses
> another module where commands are defined.
> Now, `define-command' always makes the command available in Lisp,
> whether or not anything uses the containing Scheme module.
I see, and I agree with you. I guess we could define
`lisp-export-environment' for this purpose in the future when
the environment patch is merged into Guile.
prev parent reply other threads:[~2000-04-29 12:27 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
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 [this message]
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).