Re: lynx-dev broken mail message.

[pAb-032871]

In "lynx-dev broken mail message (was: Tables (once again) and virtual lynx 
pages)"
[18/May/2000 Thu 12:11:56]
Klaus Weide wrote:

> Your message had a NUL ('\0') byte...
> 

Great, another one. . .  Bad Email, I mean.  Resending, WITHOUT
the offending null.

Sorry, I hope it didn't cause any problems.  The list server is
perfectly okay, because I also found it in my local OUTgoing file.
It was written in an external editor, which was probably up and
running during the crash this morning [some low-level hacking
that didn't go well. . .].

I didn't even SEE that until I tried reading the message in a
hex editor.  Null characters [hex-00] are zero-width in most
fonts, even supposedly "fixed-width".


> > it could ignore TARGET attributes, rendering subsequ
> 
>                                                       ^
> ...at this point.
> 
> Your software (mail user agent, editor?) may be broken.  Or it could
> be a mailing list problem.

Thanks, I went through my incoming and outgiong archives, but
that was the only occurence.  Won't happen again [really, I'll
check more thoroughly if there's another system bomb].


                    Patrick
          <mailto:address@hidden>
 

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden