Path: utzoo!attcan!uunet!ogicse!schaefer
From: schaefer@ogicse.ogi.edu (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: ^@ in compose mode
Message-ID: <11966@ogicse.ogi.edu>
Date: 6 Sep 90 18:19:31 GMT
References: <1990Sep6.191142.2170@robobar.co.uk>
Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR
Lines: 18

In article <1990Sep6.191142.2170@robobar.co.uk> ronald@robobar.co.uk (Ronald Khoo) writes:
} Is it just my setup, or does mush normally go into an infinite loop
} when you type a NUL at the builtin mail composition editor?

I don't know if it's just your setup, but mush normally ignores NUL when
it appears anywhere on standard input, in the mail composition editor or
anywhere else.  Code fragment:

    while ((c = getchar()) == 0)    /* Ignore NUL chars from stdin */
	;                           /* until better solution found */
    return c;

This is because mush stores each line of standard input in a standard C
string, so reading and storing a NUL would improperly truncate the string.
Was anything else involved here, e.g. were you using a macro or editing a
previously typed line with ~u ?
-- 
Bart Schaefer						schaefer@cse.ogi.edu