public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Keisuke Nishida <kxn30@po.cwru.edu>
To: Kalle Olavi Niemitalo <tosi@ees2.oulu.fi>
Cc: guile-emacs@sourceware.cygnus.com
Subject: Re: automating %load-path
Date: Mon, 27 Mar 2000 17:28:00 -0000	[thread overview]
Message-ID: <m3k8indgsp.fsf@kei.cwru.edu> (raw)
In-Reply-To: <87ln34y0h4.fsf@PC486.Niemitalo.LAN>

Kalle Olavi Niemitalo <tosi@ees2.oulu.fi> writes:

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

That is right.  I am not going to demotivate you.  I have added
the two files (Makefile.in and src/epath.in) just now.

From your past mail:
| 2. Add a new macro PATH_SCMLOADSEARCH in src/epaths.in.  If we
|    don't support Scheme in temacs, we don't need
|    PATH_SCMDUMPLOADSEARCH.

I think we don't need PATH_SCMDUMPLOADSEARCH.

| 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 agree with this.  Maybe we don't need to load ~/.emacs.scm
in lisp/startup.el.

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

A list of functions/features might be helpful.  Not necessary to
be written precisely because they will possibly change soon.

  reply	other threads:[~2000-03-27 17:28 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 [this message]
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:
  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=m3k8indgsp.fsf@kei.cwru.edu \
    --to=kxn30@po.cwru.edu \
    --cc=guile-emacs@sourceware.cygnus.com \
    --cc=tosi@ees2.oulu.fi \
    /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).