gnome default printer insanity? Re: generic postscript printer is NOT my default

[Ralph Shumaker]

James G. Sack (jim) wrote:
> Ralph Shumaker wrote:
> 
>>..
>><DefaultPrinter hp1100>
>>DeviceURI parallel:/dev/lp0
>>Location HP LJ 1100
>>Info HP LJ 1100
>>State Idle
>>Accepting Yes
>>JobSheets none none
>>QuotaPeriod 0
>>PageLimit 0
>>KLimit 0
>></Printer>
>><Printer TimeWaste>
>>DeviceURI parallel:/dev/lp0
>>Location This is an exercise in futility.
>>Info This is an exercise in futility.
>>State Idle
>>Accepting Yes
>>JobSheets none none
>>QuotaPeriod 0
>>PageLimit 0
>>KLimit 0
>></Printer>
> 
> 
> Looks normal to me. Do you have the latest cups appropriate for your
> FC4? (yum update cups).

(Creating this prompt on Mon Aug 07 at 15:55:52.)
# yum update cups
Setting up Update Process
Setting up repositories
Reading repository metadata in from local files
Could not find update match for cups
No Packages marked for Update/Obsoletion
(Creating this prompt on Mon Aug 07 at 16:00:35.)
#

> 
> 
>>..
>>I suppose that "\|" in your suggested command translates to OR .  I use
>>bash on fc4.  If it was supposed to do something different than what I
>>supposed, tell me and I'll retry.
> 
> 
> No, you were "supposed to" type both of the characters '\' and '|', but
> it doesn't make any difference because you improvised correctly to run
> two commands (one with cups, one with lpd), and confirmed that cupds
> _is_ running and there is not any lpd running.

I didn't "type" anything.  I used cut and paste to put your command (as 
*you* typed it) directly to the bash command line.  It didn't work, so I 
/surmised/ that the '\' was escaping the '|' to allow it to mean "OR" to 
allow a dual search in one shot.

> 
> Interesting(?) aside..
> My format,
>   grep cups\|lpd
> was intended to check for either match in one call, but my advice was
> wrong anyway -- I should have used egrep, because grep doesn't do
> alternatives (egrep does). I should have said
>   egrep cups\|lpd
> or equivalently
>   egrep 'cups|lpd'
> The significant point here is that '|' normally has special meaning to
> the shell, and either the '\' escaping or the '...' quoting prevents the
> shell from interpreting special characters.

As I surmised.