public inbox for guile-emacs@sourceware.org
 help / color / mirror / Atom feed
From: Keisuke Nishida <kxn30@po.cwru.edu>
To: guile-emacs@sourceware.cygnus.com
Subject: Re: New internal implementation
Date: Sat, 06 May 2000 17:43:00 -0000	[thread overview]
Message-ID: <m3ya5n42c1.fsf@kei.cwru.edu> (raw)
In-Reply-To: <20000507075238H.satoru-t@is.aist-nara.ac.jp>

Satoru Takabayashi <satoru-t@is.aist-nara.ac.jp> writes:

> How about preparing `autogen.sh' in the CVS to automate
> these forgetful procedures?

Good idea.  I'll make it.

> | 7. Install the "emacs" subdirectory to somewhere:
> | 
> |   # cd ..
> |   # mkdir /usr/local/share/emacs/scheme
> |   # cp -r emacs /usr/local/share/emacs/scheme
> 
> Can it be done with `make install' as I proposed before?

You can do "ln -s . /usr/local/share/emacs/scheme" instead if you want.

> Probably, it is good to distribute Guile Emacs as an
> all-in-one package instead of patch files to emacs-20.6.
> People may have difficulty in installation and give up. 

Right, though I guess most users of Guile Emacs are good developers :)
We can do so when we release Guile Emacs 1.0, but it is easier to
distribute a small tarball for now.  (I don't want to release over
10MB packages once a month.)

-- Kei

  reply	other threads:[~2000-05-06 17:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-05  6:47 Keisuke Nishida
2000-05-05  8:21 ` Dynamic binding: lisp-ref and lisp-set! Keisuke Nishida
2000-05-06  5:37 ` New internal implementation Satoru Takabayashi
2000-05-06  6:57   ` Keisuke Nishida
2000-05-06 15:50     ` Satoru Takabayashi
2000-05-06 17:43       ` Keisuke Nishida [this message]
2000-05-07  2:27         ` Satoru Takabayashi
2000-05-07  2:58           ` Keisuke Nishida
     [not found]         ` <20000507182914A.satoru-t@is.aist-nara.ac.jp>
     [not found]           ` <m3k8h6r912.fsf@kei.cwru.edu>
2000-05-07  3:14             ` Satoru Takabayashi
2000-05-07  3:41               ` 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=m3ya5n42c1.fsf@kei.cwru.edu \
    --to=kxn30@po.cwru.edu \
    --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).