From: "rgb" <rbielaws@i1.net>
Subject: Re: Newbie major-mode and elisp question
Date: 8 Sep 2005 09:21:55 -0700 [thread overview]
Message-ID: <1126196515.790157.238520@g49g2000cwa.googlegroups.com> (raw)
In-Reply-To: fmRTe.1984$7D1.862@newssvr12.news.prodigy.com
sj wrote:
> 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.
a progn isn't necessary here but doesn't hurt anything
> (progn
> ;; Clean up any old nyquist process buffers
> (if (get-buffer nyquist-buffer)
> (kill-buffer nyquist-buffer))
Simply delete this line. It's purpose is to allow a buffer's
mode to be changed without lingering artifacts from the old mode.
Since you are creating a derived mode, the mode from which
nyquist-mode derives is already doing the kill appropriately.
> (kill-all-local-variables)
next prev parent reply other threads:[~2005-09-08 16:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 7:02 Newbie major-mode and elisp question sj
2005-09-08 16:21 ` rgb [this message]
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=1126196515.790157.238520@g49g2000cwa.googlegroups.com \
--to=rbielaws@i1.net \
/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).