On Mon 20 Jun 2022, at 23:50, Gareth Evans wrote:
> On Mon 20 Jun 2022, at 23:31, Gareth Evans wrote:
>> On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
>>> On 2022-06-20 at 12:01, Brian wrote:
>>>
On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
> On 2022-06-20 at 08:5
On Mon 20 Jun 2022, at 23:31, Gareth Evans wrote:
> On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
>> On 2022-06-20 at 12:01, Brian wrote:
>>
>>> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>>>
On 2022-06-20 at 08:59, Brian wrote:
>>
> The ability to print to an IPP pri
On Mon 20 Jun 2022, at 17:34, The Wanderer wrote:
> On 2022-06-20 at 12:01, Brian wrote:
>
>> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>>
>>> On 2022-06-20 at 08:59, Brian wrote:
>
The ability to print to an IPP printer involves discovering its
URI. CUPS gets the URI vi
On Mon 20 Jun 2022 at 19:49:18 +0100, Brian wrote:
Please forget about this mai. I pressed the wrong key. Never done that
before!
> On Mon 20 Jun 2022 at 12:34:19 -0400, The Wanderer wrote:
>
> > On 2022-06-20 at 12:01, Brian wrote:
> >
> > > "...once the URIis known"? What mechaism does that?
On Mon 20 Jun 2022 at 12:34:19 -0400, The Wanderer wrote:
> On 2022-06-20 at 12:01, Brian wrote:
>
> > "...once the URIis known"? What mechaism does that? Incidentally, a
> > URI is required to query a printer for its attributes.
>
> Any of a number of mechanisms.
>
> CUPS could run discovery on
On 2022-06-20 at 12:01, Brian wrote:
> On Mon 20 Jun 2022 at 09:28:30 -0400, The Wanderer wrote:
>
>> On 2022-06-20 at 08:59, Brian wrote:
>>> The ability to print to an IPP printer involves discovering its
>>> URI. CUPS gets the URI via avahi-daemon whether it is an
>>> on-demand or manual queu
ways happen automatically in all cases.
>
> >> I can certainly see it as being reasonable to want to be able to
> >> have CUPS perform printer discovery *on request*, and manually
> >> choose which of the discovered printers to add to the list of ones
> >> that will
ry *automatically* and *automatically* add
>> every discovered printer to that list. (I don't know with any
>> confidence whether CUPS does the latter; I don't run it in enough
>> environments with enough different available printers to have been
>> able to make a
On Wed, 22 Jun 2005 02:50:07 +0200, David A. Cobb wrote:
> When my wife tries to print from her desktop, the choices of printer are
> * scx5400_5400@:64
> * xp_ps_spooldir_HOME_xprint ... @:64
> * xp_pdf_spooldir_HOME_xprint ...@:64
> * Postscript/scx5300_5400
> And everything she tries to print co
Debian kernel-2.4.29-f3, mostly sarge, some sid.
Gnome Desktop 2.8.3
Cups: 1.0.23-10
mozilla-firefox browser, 2 versions, debian 1.0.2 for everybody but myself
Epson Color Stylus CX5400 printer
When I print from my own desktop, the choices of printer offered by the
browser's print dialog are:
10 matches
Mail list logo
