public inbox for
 help / color / mirror / Atom feed
From: Satoru Takabayashi <>
Subject: Re: New internal implementation
Date: Sat, 06 May 2000 15:50:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Keisuke Nishida <> wrote:

>> Here is a log:
>Did you try this?
>4. Recompile patched Emacs Lisp files:
>  % emacs -q -batch -f batch-byte-recompile-directory lisp

Thank you for pointing this out.  I forgot to do it when I
reported. I just rebuilt Guile Emacs and the problem were

>If you extract the source files directly in guile-emacs/src, then
>you don't need to create a patch every time.  I'll add a new file
>INSTALL.CVS for CVS users.

OK, I extracted the source files of emacs-20.6.tar.gz in
guile-emacs/src.  It released me from creating a patch every
time but I feel the installation is still rather troublesome.

| 4. Recompile patched Emacs Lisp files:
|   % emacs -q -batch -f batch-byte-recompile-directory lisp
| 5. Regenerate the configure script:
|   % autoconf

How about preparing `' in the CVS to automate
these forgetful procedures?

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

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. 

-- Satoru Takabayashi

  reply	other threads:[~2000-05-06 15:50 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 [this message]
2000-05-06 17:43       ` Keisuke Nishida
2000-05-07  2:27         ` Satoru Takabayashi
2000-05-07  2:58           ` Keisuke Nishida
     [not found]         ` <>
     [not found]           ` <>
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

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