unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: David Kastrup <dak@gnu.org>
Subject: Re: Checking Process Status
Date: 12 Feb 2003 23:43:12 +0100	[thread overview]
Message-ID: <x5wuk52k8v.fsf@lola.goethe.zz> (raw)
In-Reply-To: qWz2a.39840$yn1.1668284@twister.austin.rr.com

"CarlC" <carlc@snowbd.com> writes:

> "CarlC" <carlc@snowbd.com> wrote in message
> news:Ewz2a.39752$yn1.1662533@twister.austin.rr.com...
> > This code has worked for me. To do away with the "undesirable
> consequences",
> > I make this temporary in the compile function:
> >
> > (defadvice compile (before cobol-compile activate)
> >   "Set compile-command and make compile syncronous"
> >   (fset 'save-start-process (symbol-function 'start-process))
> >   (fmakunbound 'start-process))
> >
> > (defadvice compile (after cobol-compile activate)
> >   "Process cobol error listing."
> >   (fset 'start-process 'save-start-process)
> > ...
> 
> Spoke too soon. This code breaks with "Symbol's chain of function
> indirections contains a loop: start-process" if I run a compile more than
> once and then try to open a shell buffer. Anyone know the proper way to
> accomplish this?

You do it right the first time, wrong the second time.  But it is not
really necessary to save in a global variable, and you want stuff to
get restored in any case.

I'd use
(defadvice compile (around cobol-compile activate)
  "Set ...."
  (let ((saved-start-process (symbol-function 'start-process)))
       (unwind-protect
         (progn (fmakunbound 'start-process) ad-to-it)
         (fset 'start-process saved-start-process))))

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  parent reply	other threads:[~2003-02-12 22:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-03 14:53 Checking Process Status CarlC
2003-02-03 15:04 ` David Kastrup
2003-02-03 17:49   ` Kevin Rodgers
2003-02-03 22:19     ` CarlC
2003-02-03 22:15   ` CarlC
2003-02-03 22:29     ` David Kastrup
2003-02-03 22:42       ` CarlC
2003-02-03 23:56         ` Kevin Rodgers
2003-02-04 17:20           ` Jay Belanger
2003-02-10 20:47             ` Kevin Rodgers
2003-02-11  6:35               ` Eli Zaretskii
2003-02-12 22:03           ` CarlC
     [not found]             ` <qWz2a.39840$yn1.1668284@twister.austin.rr.com>
2003-02-12 22:43               ` David Kastrup [this message]
2003-02-12 22:55                 ` CarlC
2003-02-12 23:17                   ` David Kastrup
2003-02-13  9:37                   ` Kai Großjohann
     [not found] <mailman.1775.1044945429.21513.help-gnu-emacs@gnu.org>
2003-02-12  0:10 ` Kevin Rodgers
2003-02-12 17:37   ` Jay Belanger

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=x5wuk52k8v.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    /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).