From: Chris Beggy <chrisb@kippona.com>
To: knishida@sky.sannet.ne.jp
Cc: guile-emacs@sources.redhat.com
Subject: Re: emacs-guile
Date: Thu, 17 Jan 2002 20:06:00 -0000 [thread overview]
Message-ID: <20020117.230602.59069554.chrisb@kippona.com> (raw)
In-Reply-To: <m3ita0h6qo.wl@xp.netlab.jp>
From: Keisuke Nishida <knishida@sky.sannet.ne.jp>
> At Fri, 18 Jan 2002 08:41:31 +0900,
> Keisuke Nishida wrote:
> >
> > > 2. let me use scheme libraries to do functions in emacs, like
> > > manipulating buffers and so on.
>
> Oops, you can do something with Emacs's buffers using Scheme libraries.
> Try the following in _lisp-interaction-mode_.
>
> (require 'guile)
> (guile-import string-upcase)
>
> (insert (string-upcase (buffer-substring-no-properties 1 100)))
and that returns:
(require 'guile)
(guile-import string-upcase)
(insert (string-upcase (buffer-substring-no-properties 1 115))) (REQUIRE 'GUILE)
(GUILE-IMPORT STRING-UPCASE)
(INSERT (STRING-UPCASE (BUFFER-SUBSTRING-NO-PROPERTIES 1 115)
which is great! Now I am starting to understand.
> `guile-lisp-eval' is also a Lisp function. You can use
> `guile-import-module' to import all functions defined in
> a Guile's module.
so guile-import, guile-lisp-eval, guile-import-module are all
your functions from guile.el. Thanks.
Do we have any capability to do something like C-h f <scheme
function> to learn about the scheme functions in the imported
library? Do we have to worry about collision with elisp symbols?
Chris
next prev parent reply other threads:[~2002-01-18 4:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 14:25 emacs-guile Chris Beggy
2002-01-17 15:08 ` emacs-guile Keisuke Nishida
2002-01-17 15:23 ` emacs-guile Chris Beggy
2002-01-17 15:40 ` emacs-guile Keisuke Nishida
2002-01-17 15:55 ` emacs-guile Keisuke Nishida
2002-01-17 20:06 ` Chris Beggy [this message]
2002-01-18 0:05 ` emacs-guile 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=20020117.230602.59069554.chrisb@kippona.com \
--to=chrisb@kippona.com \
--cc=guile-emacs@sources.redhat.com \
--cc=knishida@sky.sannet.ne.jp \
/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).