From: Kalle Olavi Niemitalo <tosi@stekt.oulu.fi>
To: Keisuke Nishida <kxn30@po.cwru.edu>
Cc: guile-emacs@sourceware.cygnus.com
Subject: some ideas (mostly about names)
Date: Tue, 14 Mar 2000 12:46:00 -0000 [thread overview]
Message-ID: <87ln3lp9k5.fsf@PC486.Niemitalo.LAN> (raw)
Please add guile or guile-emacs in `features' and make M-x
emacs-version show that.
In the README, you suggest copying the Scheme files to
/usr/local/share/emacs/site-scheme/emacs. You have made them a
standard part of guile-emacs, so wouldn't it make sense to omit
the "site-"? You could even place them in the Emacs source tree,
so that the new Emacs can use them before it is installed. The
makefiles should then be amended to install the scheme/ tree
just like lisp/, and the startup code should add it in Guile's
%load-path.
Are you going to append exclamation points to names of Emacs
builtins which alter things, like "define-key"?
next reply other threads:[~2000-03-14 12:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-14 12:46 Kalle Olavi Niemitalo [this message]
2000-03-14 13:14 ` 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=87ln3lp9k5.fsf@PC486.Niemitalo.LAN \
--to=tosi@stekt.oulu.fi \
--cc=guile-emacs@sourceware.cygnus.com \
--cc=kxn30@po.cwru.edu \
/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).