public inbox for
 help / color / mirror / Atom feed
From: Keisuke Nishida <>
To: Kalle Olavi Niemitalo <>
Subject: Re: patch: M-x emacs-version
Date: Wed, 22 Mar 2000 23:08:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <87em934ixa.fsf@PC486.Niemitalo.LAN>

Kalle Olavi Niemitalo <> writes:

> > and provide a Lisp function `use-scheme-module' or something.
> This could be made part of `require': if the required feature is
> a list, it would be interpreted as a Scheme module name.  Perhaps
> that is a bad idea; it would overload the meaning of a primitive.

I guess we will use a whole new package management system in the future,
so we don't need to care about this too much for the moment.

> > I'm not sure whether we should include this subdirectory in a
> > archive instead of a patch.
> Sorry, I don't quite understand.  Do you mean the src
> subdirectory and guile-emacs-*.tar.gz archives?  If so, I think
> it is not useful there.

Yes, that's what I meant.

> I hope it will be easier to use guile-emacs with non-20.6
> versions of Emacs if the tar.gz contains either the patch or a
> way to generate it.  Files in the src directory don't help with
> this: to generate the patch from them, one also needs the
> emacs-20.6 source which may not be available when emacs-20.9 is
> current.

That's right.  I'll provide the patch with tarball, while maintain
the src directory in the CVS repository.  We could add more patches
by creating subdirectories for other Emacsen.

      reply	other threads:[~2000-03-22 23:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-20 20:54 Kalle Olavi Niemitalo
2000-03-21 12:18 ` Keisuke Nishida
2000-03-21 22:39   ` Kalle Olavi Niemitalo
2000-03-22 23:08     ` Keisuke Nishida [this message]

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