Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!osu-cis!tut!karl
From: karl@tut.UUCP
Newsgroups: comp.sources.bugs
Subject: Re: another tcsh bug
Message-ID: <37@tut.cis.ohio-state.edu>
Date: Mon, 7-Sep-87 10:07:58 EDT
Article-I.D.: tut.37
Posted: Mon Sep  7 10:07:58 1987
Date-Received: Tue, 8-Sep-87 04:06:03 EDT
References: <16196@teknowledge-vaxc.ARPA> <24@tut.cis.ohio-state.edu> <4481@ncoast.UUCP>
Organization: OSU
Lines: 18

allbery@ncoast.UUCP writes:
> It occurs to me that a better way to handle this is to set a flag "did the
> periodic alias" immediately before doing it, and clear it immediately after
> printing the prompt.  If the flag is already set, don't execute the alias.
> Is there some valid reason (bad coding is _not_ a valid reason!) why this
> can't be done?

On the one hand, I remember considering that solution when I first
realized the halt-and-catch-fire bug was there; on the other hand, I
believe I couldn't do that due to the nature of the parse/execute
routines which I used (the calling sequence for which I borrowed from
process()).  There isn't any way to stop it at that particular point,
as I recall.  But I will check into it again.

As it is, the flag is set just before attempting alias resolution, and
cleared after execution.
-- 
Karl