From: Neil Jerram <neil@ossau.uklinux.net>
To: ttn@glug.org
Cc: guile-devel@gnu.org, guile-emacs@sources.redhat.com
Subject: Re: Elisp translator work finished (for now)
Date: Tue, 12 Feb 2002 14:59:00 -0000 [thread overview]
Message-ID: <m37kpi1f8c.fsf@laruns.ossau.uklinux.net> (raw)
In-Reply-To: <m33d062vui.fsf@laruns.ossau.uklinux.net>
>>>>> "Neil" == Neil Jerram <neil@ossau.uklinux.net> writes:
>>>>> "thi" == Thien-Thi Nguyen <ttn@giblet.glug.org> writes:
thi> i modified lang/elisp/base.scm `load-emacs' like so: [...]
Neil> Strange. I'll have a look... Thanks for your interest and the report!
Oh dear; my representation of Elisp variables is a bit screwy.
(`setq' sets a variable called `load-path' in (lang elisp base), but
the Scheme definition of `load' picks up `load-path' from (lang elisp
internals load).) I'll try to fix this in the next few days.
Thanks again.
Neil
next prev parent reply other threads:[~2002-02-12 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-08 3:53 Neil Jerram
2002-02-11 14:38 ` Thien-Thi Nguyen
2002-02-12 14:38 ` Neil Jerram
2002-02-12 14:59 ` Neil Jerram [this message]
2002-02-13 13:47 ` Neil Jerram
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=m37kpi1f8c.fsf@laruns.ossau.uklinux.net \
--to=neil@ossau.uklinux.net \
--cc=guile-devel@gnu.org \
--cc=guile-emacs@sources.redhat.com \
--cc=ttn@glug.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).