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

Keisuke Nishida <> writes:

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

If users add their own Scheme files in different directories,
they still can alter %load-path in their .emacs.scm.  I think
this would be a step in the right direction.  I would also like
automatic installation, but that may be a little difficult to
implement.  The easiest way might be to put the Scheme files
under src/emacs-20.6 too.

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

(I personally make ${prefix}/share/emacs/20.5/scheme a symlink to
the local CVS directory.)

> Could you write some documentation, especially NEWS file as a
> function introduction for that?

I'll write a NEWS file based on ChangeLog and recent mails.
What other documentation do you have in mind: a complete manual
in Texinfo?  I'm not sure I could manage that.

  reply	other threads:[~2000-03-27  9:08 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 [this message]
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 \
    --in-reply-to=87ln34y0h4.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).