From: sj <dummy@dummy.com>
Subject: Newbie major-mode and elisp question
Date: Thu, 08 Sep 2005 07:02:35 GMT [thread overview]
Message-ID: <fmRTe.1984$7D1.862@newssvr12.news.prodigy.com> (raw)
I'm writing my first major mode to run Nyquist in a buffer. Nyquist is an
extension of XLISP for audio synthesis and composition. Nyquist-mode is a
derivative of inferior-lisp mode, its working pretty well except for one
annoying side effect. Whenever I issue (nyquist-mode) to start a new
Nyquist process, whatever buffer I'm currently in gets switched to
fundamental-mode. I have isolated the problem to the
kill-all-local-variables statement. Is there some other way I should be
doing this?
(defun nyquist-mode ()
(interactive)
(if (nyquist-has-process-p)
;; If we are already live just switch to the nyquist buffer
(switch-to-buffer nyquist-buffer)
;; Else start a new Nyquist process.
(progn
;; Clean up any old nyquist process buffers
(if (get-buffer nyquist-buffer)
(kill-buffer nyquist-buffer))
(kill-all-local-variables)
(run-lisp nyquist-program)
(switch-to-buffer "*inferior-lisp*")
(rename-buffer nyquist-buffer)
(setq major-mode 'nyquist-mode)
(setq mode-name "Nyquist")
(setq inferior-lisp-buffer nyquist-buffer)
(lisp-load-file nyquist-start-file)
(use-local-map nyquist-map)
(run-hooks 'nyquist-hook)
)))
Some background:
There is only --one-- nyquist process at any time. The variable
nyquist-buffer holds the buffer name for the nyquist process (needed
because I ultimately need other non-nyquist lisp running)
nyquist-program contains the local invocation to run nyquist. Hopefully the
rest is self-explanatory.
--
Remove underscores to reply
_jones_57_@_swbell_._net
next reply other threads:[~2005-09-08 7:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 7:02 sj [this message]
2005-09-08 16:21 ` Newbie major-mode and elisp question rgb
2005-09-08 17:12 ` Kevin Rodgers
2005-09-09 5:07 ` Stefan Monnier
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='fmRTe.1984$7D1.862@newssvr12.news.prodigy.com' \
--to=dummy@dummy.com \
/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).