Sorry, I just re-approved an already sent nmh-bugs post. It's a
duplicate, please ignore.
--
Doug Morris
Morris Communications & Computer Services, Inc.
http://www.mhost.com/
Tobias Polzin <[EMAIL PROTECTED]> wrote:
>I don't like BASE64/Quoted-Printable Encoded Mails, because they
>are difficult to Quote and Search with exmh/glimple.
>If I use "/usr/lib/python/mimefy.py -b -d | /usr/mh/lib/slocal"
>some 8bit Parts of Mails got garbled by slocal. It seems to me,
>every
On August 29, 2002 at 11:14, Tobias Polzin wrote:
> I don't like BASE64/Quoted-Printable Encoded Mails, because they
> are difficult to Quote and Search with exmh/glimple.
> If I use "/usr/lib/python/mimefy.py -b -d | /usr/mh/lib/slocal"
> some 8bit Parts of Mails got garbled by slocal. It seems
> "slocal" is only one of a zillion programs that cannot properly
> handle embedded '\0' characters.
>
> This is, at least in part, due to the unfortunate "design" of
> fgets().
The problem occurs, while slocal copies the stdin to a temporary
file. I patched slocal.c such that this can be done
I don't like BASE64/Quoted-Printable Encoded Mails, because they
are difficult to Quote and Search with exmh/glimple.
If I use "/usr/lib/python/mimefy.py -b -d | /usr/mh/lib/slocal"
some 8bit Parts of Mails got garbled by slocal. It seems to me,
everything in a line following a "zero char" (includ
