From: Kalle Olavi Niemitalo <tosi@stekt.oulu.fi>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: automating %load-path
Date: Fri, 14 Apr 2000 00:29:00 -0000 [thread overview]
Message-ID: <874s959m4l.fsf@PC486.Niemitalo.LAN> (raw)
In-Reply-To: <87og81zwk3.fsf@PC486.Niemitalo.LAN>
Kalle Olavi Niemitalo <tosi@ee.oulu.fi> writes:
> 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.
I have committed these changes.
There is a bug; I now get the following error on startup:
> No such function: scheme-interaction-mode
This message comes from Guile. `scheme-interaction-mode' exists
as a Lisp function, and in the (emacs guile) module as a Scheme
function, but the default module does not use (emacs guile) and
so the Lisp-to-Scheme call fails. This can be worked around by
doing M-: (scheme-eval '(use-modules (emacs guile))) after
getting the error.
I guess a real fix involves changing `define-command' so that it
makes the Lisp part of the command always call the Scheme part
from the correct module. I haven't yet figured out how to do
this. This will perhaps be affected when Guile gets its new
module system, but I don't think we should wait for that.
next prev parent reply other threads:[~2000-04-14 0:29 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 ` Kalle Olavi Niemitalo [this message]
2000-04-29 1:21 ` automating %load-path 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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874s959m4l.fsf@PC486.Niemitalo.LAN \
--to=tosi@stekt.oulu.fi \
--cc=guile-emacs@sourceware.cygnus.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).