Open
Bug 173106
Opened 22 years ago
Updated 2 years ago
copiousoutput ignored in mailcap
Categories
(Firefox :: File Handling, defect)
Tracking
()
NEW
People
(Reporter: nicolas.george, Unassigned)
References
(Depends on 1 open bug)
Details
Il my mailcap file, I have
application/msword; antiword %s; copiousoutput
If I try to download an word file witn Mozilla, it asks me if I want to open it
with antiword, and then dumps the document on its standard output, usually
~/.xsession-errors.
I think Mozilla shound take in account the copiousoutput flag, and recapture the
output to display it itself.
Comment 1•22 years ago
|
||
Um... You're using a command that writes to standard output. You should be
using "needsterminal" (not like we support that yet). I suppose we could
make "copiousoutput" imply "needsterminal"... Past that, I'm not quite sure
what a good way of dealing would be... There's no clean way to open "antiword |
$PAGER" in a terminal window....
Assignee: law → bzbarsky
Status: UNCONFIRMED → NEW
Depends on: 120380
Ever confirmed: true
Priority: -- → P5
Target Milestone: --- → Future
Reporter | ||
Comment 2•22 years ago
|
||
There is another way for Mozilla to handle copiousoutput : it can catch antiword
output, and display it as a text/plain document. I think this would be the best
way to do it, but it may not be trivial to do.
Comment 3•22 years ago
|
||
That would indeed be somewhat hard, and more to the point would be broken. Far
too many apps that would be flagged with "copiousoutput" embed ANSI
color/bold/whatever sequences in their output because they expect a terminal to
handle it. Thus the output is in fact not text/plain and Mozilla's rendering of
it would be pretty broken.
Updated•22 years ago
|
QA Contact: sairuh → petersen
Updated•15 years ago
|
QA Contact: chrispetersen → file-handling
Updated•14 years ago
|
Assignee: bzbarsky → nobody
Priority: P5 → --
Target Milestone: Future → ---
Updated•8 years ago
|
Product: Core → Firefox
Version: Trunk → unspecified
Updated•2 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•