* Daniel Nilsson [28.02.2005 02:42]: > On Mon, Feb 28, 2005 at 02:29:04AM +0100, Bernhard Walle wrote: > >>>>>I reassigned this bug to the muttprint package, I guess we will have >>>>>to figure out from there where things are broken. Thanks for your >>>>>help. >>>> >>>>It's probable psnup, if you use muttprint with non-cups setup. >>> >>>Hmm, not sure I understand what non-cups setup means in this case. I >>>do use a CUPS printer system on my box... >>> >>>My print command in .muttprintrc is: >>> >>>PRINT_COMMAND="lp -d $PRINTER" >>> >>>I see something mentioned regarding CUPS in the comment above the >>>print command so I assume this is what you are referring to. In the >>>man page is says that "CUPS support could be activated by CUPS" but I >>>don't understand what that means. Should I set PRINT_COMMAND to CUPS >>>as in: >>> >>>PRINT_COMMAND="CUPS" ? > > > By setting the PRINT_COMMAND to CUPS I no longer see this issue, I can > print 2-up and get good quality results. From your comment above this > seems to imply a bug in psnup which is in the package psutils. Should > I move this bug to the psutils package then or is it still an issue > with the way muttprint uses psnup ?
Try it out: PAPERSAVE="off" PRINTER="TO_FILE:/tmp/test.ps" And then cat /tmp/test.ps | psnup -2 -q | lpr Regards, Bernhard -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
