From: Thorsten <quintfall@googlemail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: [printing] duplex doesn't work (Thorsten)
Date: Mon, 10 Oct 2011 00:53:29 +0200 [thread overview]
Message-ID: <86list4w0m.fsf@googlemail.com> (raw)
In-Reply-To: 20111008190525.GB7078@srevilak.net
Steve Revilak <steve@srevilak.net> writes:
> My linux distribution uses CUPS. Via CUPS, I've configured duplex as
> a default option for print jobs. To see if CUPS is installed on your
> system, visit <http://localhost:631/> in your web browser of choice.
> If you see a page with the word "CUPS", then that is probably what
> your system is using to print, and you use this web interface to
> configure duplex as a default option. Maybe this is all you need to
> do.
Perfect, this did the job, now duplex printing works fine in Emacs too.
Thanks a lot for your long and informative answer - it helped me to get
rid of a problem that annoyed me for quite some time now.
Cheers
--
Thorsten
prev parent reply other threads:[~2011-10-09 22:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 17:52 [printing] duplex doesn't work Thorsten
2011-10-08 19:05 ` [printing] duplex doesn't work (Thorsten) Steve Revilak
2011-10-09 22:53 ` Thorsten [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86list4w0m.fsf@googlemail.com \
--to=quintfall@googlemail.com \
--cc=help-gnu-emacs@gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).