From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: f.j.wright@qmul.ac.uk, arash@gnu.org, 3332@debbugs.gnu.org,
4275@debbugs.gnu.org
Subject: bug#4275: bug#3332: bug#4275: 23.1; Printing
Date: Wed, 02 Feb 2022 19:07:51 +0200 [thread overview]
Message-ID: <83y22t5h94.fsf@gnu.org> (raw)
In-Reply-To: <878rutus98.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 02 Feb 2022 17:50:59 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Arash Esbati <arash@gnu.org>, f.j.wright@qmul.ac.uk,
> 3332@debbugs.gnu.org, 4275@debbugs.gnu.org
> Date: Wed, 02 Feb 2022 17:50:59 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > See the node "Windows Printing" in the Emacs manual, which explains
> > that the default setting of the printer on MS-Windows isn't guaranteed
> > to work, and provides a few alternative suggestions for setting up the
> > printer.
> >
> > I don't think we can do anything with these problems beyond describing
> > the various tricks of the trade.
>
> Could this command output a message (on Windows) that points the user to
> this manual node when you get this error?
Which command? lpr-buffer?
The error comes from very low-level code, but I guess anything's
possible if we want it badly enough.
next prev parent reply other threads:[~2022-02-02 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001301c9d866$3827b540$a8771fc0$@j.wright@qmul.ac.uk>
2009-05-20 0:09 ` bug#3332: 23.0.93; Printing on MS Windows Jason Rumney
2009-05-20 17:12 ` Francis Wright
2022-01-31 17:14 ` bug#3332: bug#4275: 23.1; Printing Lars Ingebrigtsen
2022-01-31 18:56 ` Arash Esbati
2022-01-31 19:19 ` Eli Zaretskii
2022-01-31 19:40 ` Arash Esbati
2022-01-31 19:50 ` Eli Zaretskii
2022-02-02 16:50 ` bug#4275: " Lars Ingebrigtsen
2022-02-02 17:07 ` Eli Zaretskii [this message]
2022-02-01 12:41 ` Francis Wright
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83y22t5h94.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=3332@debbugs.gnu.org \
--cc=4275@debbugs.gnu.org \
--cc=arash@gnu.org \
--cc=f.j.wright@qmul.ac.uk \
--cc=larsi@gnus.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.