Bug#2595: efax segmentation violation.
On Sat, 23 Mar 1996, David H. Silber wrote:
> Package: efax
> Version: 0.7a-5
>
> I take a plain text file and turn it into a fax image:
>
> ~/job/work (dhs@firefly) <ttyp8> $ efix -i text -o fax -n T.%03d Tasks
> efix: opened Tasks as 66-line/page text file with 8x16 font Sat Mar 23 19:17:25 1996
> efix: opened next page as 66-line/page text file with 8x16 font
>
>
> Then I try to send it:
>
> ~/job/work (dhs@firefly) <ttyp8> $ efax -d /dev/cua1 -i +FCLASS=2 -zQ0H0 -c1 -tT230-0156 T.001
> efax: efax v 0.7a (Debian release 07a-5) starts Sat Mar 23 19:17:45 1996
> efax: Copyright 1995 Ed Casas (compiled Jan 17 1996 16:04:36)
> efax: Warning: missing value(s) in "1"
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Did you notice the warning? You might simply have lost an argument.
I am very sure that I did send one or two plain text files as test cases
before I released the first Debian version of efax --- and also when it
was remarked that efax does not strictly depend on gs as it can send plain
ascii text.
I think that you are using it simply in the wrong way --- the fax(1)
command offers you all you need. Check the fax(1) script and infer from
it how the parameters should be set. But Ed wrote fax(1) as efix(1) and
efax(1) have such messy interfaces.
I can't check into this now as I'm away from my Debian desktop, and I don't
have a modem on my laptop.
--
Dirk Eddelbuettel edd@qed.econ.queensu.ca
and until April 9th at edd@ehess.cnrs-mrs.fr
Reply to: