unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Felix Lechner via <help-guix@gnu.org>
To: Gottfried <gottfried@posteo.de>
Cc: help-guix@gnu.org
Subject: Re: unbound variable
Date: Wed, 2 Nov 2022 06:48:49 -0700	[thread overview]
Message-ID: <CAFHYt56b2RB7e3K5Bxmur1Ok16G7OWLwjR4BUVkVXUTNL5PTzA@mail.gmail.com> (raw)
In-Reply-To: <1f4a011a-b8e7-df3b-2591-c73908425074@posteo.de>

Hi Gottfried,

On Wed, Nov 2, 2022 at 5:50 AM Gottfried <gottfried@posteo.de> wrote:
>
> If e.g. I have a different printer (e.g. from an other company), and I
> want to install it,

That is a CUPS question. As you can imagine, there are lots of
printers. I usually look at which format the printer speaks, and how
it likes to communicate. Basic formats are PCL and Postscript, with
PCL being faster but less cool. My favorite communication for
networked printers is Port 9100, which I think used to be called
JetDirect, but there are others.

There is also USB (and parallel, if your printer is really old).

My own printer is reasonably well supported by CUPS alone, although I
might find a more capable PPD via hplip. RIght now, it's not worth my
time to go further. You, too, may be looking at a compromise.

For printers with their own data format, you may need Gutenprint,
which I believe is not packaged in Guix. More importantly, I believe
there are significant hurdles to packaging because there are so many
paths to replace.

Hope that helps.

Kind regards
Felix Lechner


  reply	other threads:[~2022-11-02 14:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 18:25 unbound variable Gottfried
2022-11-01 18:30 ` Felix Lechner via
2022-11-01 19:14   ` Gottfried
2022-11-01 19:38     ` Felix Lechner via
2022-11-01 20:00       ` Gottfried
2022-11-01 20:35         ` Felix Lechner via
2022-11-02  8:36           ` Gottfried
2022-11-02 12:50           ` Gottfried
2022-11-02 13:48             ` Felix Lechner via [this message]
2022-11-02 16:50               ` kiasoc5

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFHYt56b2RB7e3K5Bxmur1Ok16G7OWLwjR4BUVkVXUTNL5PTzA@mail.gmail.com \
    --to=help-guix@gnu.org \
    --cc=felix.lechner@lease-up.com \
    --cc=gottfried@posteo.de \
    /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).