From: Orm Finnendahl <finnendahl@folkwang-hochschule.de>
Subject: no connection lisp-mode buffer and *inferior-lisp*
Date: Wed, 15 Oct 2003 12:34:36 +0200 [thread overview]
Message-ID: <20031015103435.GC2097@finnendahl.de> (raw)
Hi,
I posted the message below a couple of days ago and didn't get any
response. I guess not many people on this list are using ilisp but
maybe someone can redirect me to some place where I could get help?
--
Orm
---------------------- Begin forwarded message -------------------
since upgrading to emacs 21.3 I can't get the connection between a
source lisp file and an inferior lisp buffer. It used to work fine
before.
I started up an inferior lisp with "M-x run-lisp", which establishes
an *inferior-lisp* buffer. Trying to evaluate an expression in a
lisp-mode buffer, I get the error "You must start an inferior LISP
with run-ilisp" in the command buffer. Doing that and specifying
"lisp" as the Dialect won't help either.
Below is my configuration concerning lisp/scheme in my .emacs.
I had the same problem with scheme but found out that this goes away
if I switch to scheme-mode in an arbitrary buffer *before* issuing
"M-x run-scheme". After that it works with all scheme-mode buffers. I
suspect some scheme-mode hook taking care of establishing a link
between scheme mode buffers and the scheme process but couldn't find
the culprit. Now I just have (scheme-mode) in my .emacs as a
workaround. I'd rather solve that cleaner though.
Thanx for any hints,
Orm
--------------------------------------------------------------------
(setq inferior-lisp-program "/usr/local/bin/clisp")
(load-library "ilisp-scheme-easy-menu")
(setq scheme-program-name "guile -l /usr/share/guile/site/siteinit.scm")
(setq guile-program "guile -l /usr/share/guile/site/siteinit.scm")
;; Add new keybindings: C-x C-e evaluates the *next* form,
;; C-x C-m macroexpands the next form.
(defun lisp-eval-sexp (&optional and-go)
"Send the next sexp to the inferior Lisp process.
Prefix argument means switch to the Lisp buffer afterwards."
(interactive "P")
(lisp-eval-region (point)
(save-excursion (forward-sexp) (point))
and-go
) )
(defun lisp-macroexpand-region (start end &optional and-go)
"Macroexpand the current region in the inferior Lisp process.
Prefix argument means switch to the Lisp buffer afterwards."
(interactive "r\nP")
(comint-send-string
(inferior-lisp-proc)
(format "(macroexpand-1 (quote %s))\n" (buffer-substring start end))
)
(if and-go (switch-to-lisp t))
)
(defun lisp-macroexpand-sexp (&optional and-go)
"Macroexpand the next sexp in the inferior Lisp process.
Prefix argument means switch to the Lisp buffer afterwards."
(interactive "P")
(lisp-macroexpand-region (point)
(save-excursion (forward-sexp) (point))
and-go
) )
;; Define the great keybindings.
(inferior-lisp-install-letter-bindings)
------------------------------------------------------------------------
---------------------- End forwarded message --------------------------
next reply other threads:[~2003-10-15 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 10:34 Orm Finnendahl [this message]
[not found] <mailman.1725.1066214358.21628.help-gnu-emacs@gnu.org>
2003-10-15 12:04 ` no connection lisp-mode buffer and *inferior-lisp* Gunter Bengel
2003-10-15 18:54 ` John Paul Wallington
2003-10-16 14:56 ` Ivan Boldyrev
-- strict thread matches above, loose matches on Subject: below --
2003-10-12 10:23 Orm Finnendahl
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031015103435.GC2097@finnendahl.de \
--to=finnendahl@folkwang-hochschule.de \
/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).