public inbox for
 help / color / mirror / Atom feed
From: Kalle Olavi Niemitalo <>
Subject: Re: scheme directory
Date: Wed, 03 May 2000 12:15:00 -0000	[thread overview]
Message-ID: <87vh0vh2e7.fsf@PC486.Niemitalo.LAN> (raw)
In-Reply-To: <>

Satoru Takabayashi <> writes:

>   # mkdir /usr/local/share/emacs/20.6/scheme
>   # cp -r emacs /usr/local/share/emacs/20.6/scheme

This would be best, I think.

>   # mkdir /usr/local/share/emacs/site-scheme
>   # cp -r emacs /usr/local/share/emacs/site-scheme

Actually, this is how it was before I changed "site-scheme" to
"scheme".  ;-)

> Anyway, why should we install *.scm files into
> "/usr/local/share/emacs/20.6/scheme/emacs" instead of
> "/usr/local/share/emacs/20.6/scheme"?  I think `emacs' at
> the end of the path is redundant.

The files contain Guile modules.  For example, emacs/guile.scm is
loaded with (use-module (emacs guile)).  In the module name,
`emacs' is not redundant.  If we installed the *.scm files
directly in .../scheme/, we would have to either change Guile's
module-loading procedures or install a symlink somewhere.

> Moreover, it might be fine to install *.scm files
> automatically by `make install' of Guile Emacs.


  reply	other threads:[~2000-05-03 12:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-03  4:52 Satoru Takabayashi
2000-05-03 12:15 ` Kalle Olavi Niemitalo [this message]
2000-05-05 11:56   ` Ken Raeburn
2000-05-03 15:03 ` interrupting the Scheme process Keisuke Nishida
2000-05-04 10:21   ` Kalle Olavi Niemitalo
2000-05-05 12:08   ` Ken Raeburn
2000-05-06  8:00     ` Keisuke Nishida
2000-05-06 10:34       ` Ken Raeburn

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=87vh0vh2e7.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).