Package Details: muttprint 0.73_4-3

Git Clone URL: https://aur.archlinux.org/muttprint.git (read-only)
Package Base: muttprint
Description: An app to print email from CLI mail clients, mutt in particular
Upstream URL: http://muttprint.sf.net
Licenses: GPL
Submitter: None
Maintainer: jasonwryan
Last Packager: jasonwryan
Votes: 56
Popularity: 0.036249
First Submitted: 2006-01-07 14:55
Last Updated: 2016-05-05 02:03

Latest Comments

robb commented on 2016-12-21 19:46

> I have set muttprint in my muttrc but I get the following error:
> Press any key to continue...cat: write error: Broken pipe
I had the same issue. I was able to debug the problem a bit without involving mutt, by doing just "cat file | muttprint". This returned the following error:
lpr: The printer or class does not exist.

Which seems odd since the lpq command knows the printer, it returns:
"hpc_5180 is ready". And echo $PRINTER returns: "hpc_5180"

Anyway I was able to (mutt)print successfully by adding the following to my muttrc file:
set print_command="muttprint -P A4 -p $PRINTER"

(It seems that it should also be possible to set the printer via a muttprintrc file. See the muttprint manual page.)

Shibumi commented on 2016-12-16 19:00

I have set muttprint in my muttrc but I get the following error:

Press any key to continue...cat: write error: Broken pipe

jasonwryan commented on 2016-05-05 02:04

@dtbaumann - thanks: added your patch

dtbaumann commented on 2016-05-04 06:15

Hi, it seems that the settings for duplex printing are mixed up. For papersave mode (two pages on one landscape sheet) the binding is short edge and vice versa.

--- a/muttprint 2016-05-04 08:00:34.253412690 +0200
+++ b/muttprint 2016-05-04 08:04:04.371149272 +0200
@@ -643,14 +643,14 @@
if ($Config{PAPERSAVE} eq "on") {
if ($useCups) {
$Config{PRINT_COMMAND} =~
- s/\$CUPS_OPTIONS/ -o sides=two-sided-long-edge \$CUPS_OPTIONS/;
+ s/\$CUPS_OPTIONS/ -o sides=two-sided-short-edge \$CUPS_OPTIONS/;
} else { # no cups
modifyPS("landscape");
}
} else { # no papersave
if ($useCups) {
$Config{PRINT_COMMAND} =~
- s/\$CUPS_OPTIONS/ -o sides=two-sided-short-edge \$CUPS_OPTIONS/;
+ s/\$CUPS_OPTIONS/ -o sides=two-sided-long-edge \$CUPS_OPTIONS/;
} else { # no cups
modifyPS("portrait");
}

cachereturn commented on 2016-02-18 18:19

Please change url=(http://muttprint.sf.net) -> url=http://muttprint.sf.net

makepkg is failing with error "url should not be an array."

awagner commented on 2013-10-17 18:52

@grudziar, I don't have the reference ready, but somewhere there are AUR guidelines saying that packages of the base-devel group can be presumed available on every AUR'ing computer and need not be specified in the depends...

grudziar commented on 2013-10-17 17:08

I had to manually install automake and autoconf on my machine. Apparently, they are not listed as dependencies, and without aclocal and autom4te build fails.

Anonymous comment on 2013-06-16 21:45

Bingo!
Thanks for sorting this out - much appreciated!

awagner commented on 2013-06-07 08:46

Updated. I had to recreate the diff file because there were changes to all the different languages' man Makefiles that had to be included. I hope it works now.

Anonymous comment on 2013-06-06 16:10

Just tried this, think there is a bit of a bug somewhere ...

The build almost gets to the end, then fails on the man page generation:

sed -e 's,##DOCDIR##,/usr/share/doc/muttprint,g' -e 's,##SHAREDIR##,/usr/share,g' -e 's,##BINDIR##,/usr/bin,g' -e 's,##SYSCONFDIR##,/usr/etc,g' -e 's,##TEMPDIR##,/tmp,g' -e 's,##LIBDIR##,/usr/lib,g' ./muttprint.pod > muttprint
pod2man --center="Muttprint Kurzanleitung" muttprint muttprint.1
muttprint around line 3: Non-ASCII character seen before =encoding in 'schöner'. Assuming ISO8859-1
POD document had syntax errors at /usr/bin/core_perl/pod2man line 71.

The following page seems to indicate at least someone knows about the bug:

https://launchpad.net/ubuntu/+source/muttprint/+changelog

I tried to edit the PKGBUILD and change the patch file version to 0.73_4 (and the associated hash so it verified), unfortunately although I can now see the "--utf-8" argument being passed to the pod2man command, it still fails with the same error.

Seems like the =encoding is in the wrong place in the man page file?

All comments