From: "roger peppe" <rogpeppe@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] file heuristics on troff input
Date: Mon, 14 Jul 2008 18:55:06 +0100 [thread overview]
Message-ID: <df49a7370807141055i785986d3ie77e7ee060484d94@mail.gmail.com> (raw)
In-Reply-To: <20080714163213.82A091E8C45@holo.morphisms.net>
one thing that has bugged me in the past: upas relies on file -m to
determine the type of attachments, but file only reads the first block
of the file, so if you've got a utf-8 file with the first non-ascii character
beyond the 8192nd byte, you get corrupted mail.
IMHO for the -m option, file should probably read the whole file,
but there are probably good reasons for not doing so.
next prev parent reply other threads:[~2008-07-14 17:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 14:44 Pietro Gagliardi
2008-07-11 16:11 ` hiro
2008-07-11 17:30 ` Pietro Gagliardi
2008-07-11 16:55 ` C H Forsyth
2008-07-11 17:00 ` Iruata Souza
2008-07-14 16:33 ` Russ Cox
2008-07-14 17:55 ` roger peppe [this message]
2008-07-14 18:48 ` erik quanstrom
2008-07-15 20:07 erik quanstrom
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=df49a7370807141055i785986d3ie77e7ee060484d94@mail.gmail.com \
--to=rogpeppe@gmail.com \
--cc=9fans@9fans.net \
/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 NNTP newsgroup(s).