Hi: Here's a command for printing from text editor in SuSE7.1Pro: lpr -P%p -#%c Where do I find the translation for this? I added a printer [didn't have one before], so Yast2 configured the parallel port part. Tested OK. Now, I have to do something, but not sure. When I click on the print button and watch the task bar, it says it's printing. Don't know where though. I'm thinking it's somewhere along the path that command is following. Any help appreciated. Tom
tom poe writes:
Hi: Here's a command for printing from text editor in SuSE7.1Pro: lpr -P%p -#%c obviously some witchery from the text editor.
Where do I find the translation for this? I added a printer [didn't have one before], so Yast2 configured the parallel port part. Tested OK.
Now, I have to do something, but not sure. When I click on the print button Please learn how to walk, then try skying, or a bike, and ONLY when very gifted both together. first validate printing with simple files, like: lpr /etc/passwd. Read lpr man pages, and related man pages. Then complain, if U need to
-- Pierre Imbaud <pierre@saiph.com> 12 Rue des Bosquets 91480 Quincy Sous Sénart France Tel: 01 69 00 94 57 Fax 09 47
On Friday 10 August 2001 16:16, pierre@saiph.com wrote:
tom poe writes:
Hi: Here's a command for printing from text editor in SuSE7.1Pro: lpr -P%p -#%c
obviously some witchery from the text editor.
Where do I find the translation for this?
man lpr: -P Force output to a specific printer. Normally, the default print er is used (site dependent), or the value of the environment variable PRINTER is used. -#num The quantity num is the number of copies desired of each file named. For example, lpr -#3 foo.c bar.c more.c would result in 3 copies of the file foo.c, followed by 3 copies of the file bar.c, etc. %p is a variable used to tell lpr which printer you choose in the print dialog of the editor. %c is a variable telling lpr how many copies you want. If you open 'Advanced Editor', click 'print' you'll actually see these variables in the dialog that pops up :)
I added a printer [didn't have one before], so Yast2 configured the parallel port part. Tested OK.
nice...
Now, I have to do something, but not sure. When I click on the print button
Read the printing-how-to, and the printing-usage-how-to... a lot of stuff is explained...
Please learn how to walk, then try skying, or a bike, and ONLY when very gifted both together. first validate printing with simple files, like: lpr /etc/passwd. Read lpr man pages, and related man pages. Then complain, if U need to
I don't think he *was* complaining, just being confused about the issue... HTH Jon Clausen,
On Friday 10 August 2001 08:39, Jon Clausen wrote:
On Friday 10 August 2001 16:16, pierre@saiph.com wrote:
Thank You, my friends. I now have the fundamental approach to resolving printing problems. Wish me luck. I quickly brought up a terminal, typed lpr /etc/passwd, and the bash command returned a no such thing, lpr message. Looks like I can focus in on the problem, now. Thanks, again. Tom tompoe@aether:~ > lpr /etc/passwd bash: lpr: command not found
On Fri, Aug 10, 2001 at 01:27:38AM -0700, tompoe@source.net wrote:
I quickly brought up a terminal, typed lpr /etc/passwd, and the bash command returned a no such thing, lpr message. Looks like I can focus in on the problem, now. Thanks, again. Tom
tompoe@aether:~ > lpr /etc/passwd bash: lpr: command not found
Looks like you're missing a package, or that lpr isn't on your path. 'locate lpr' will give you all filenames on your system with lpr in the name. HTH... -- David Smith Tel: +44 (0)1454 462380 (direct) STMicroelectronics Fax: +44 (0)1454 617910 1000 Aztec West TINA (ST only): (065) 2380 Almondsbury Home: 01454 616963 BRISTOL Mobile: 07932 642724 BS32 4SQ Work Email: Dave.Smith@st.com Home Email: David.Smith@ds-electronics.co.uk
On Friday 10 August 2001 21:18, Dave Smith wrote:
On Fri, Aug 10, 2001 at 01:27:38AM -0700, tompoe@source.net wrote:
I quickly brought up a terminal, typed lpr /etc/passwd, and the bash command returned a no such thing, lpr message. Looks like I can focus in on the problem, now. Thanks, again. Tom
tompoe@aether:~ > lpr /etc/passwd bash: lpr: command not found
Looks like you're missing a package, or that lpr isn't on your path. 'locate lpr' will give you all filenames on your system with lpr in the name.
Could this be a permissions issue? Bash returns 'command not found' when you don't have the permissions too: jon@p166:~ > halt bash: halt: command not found jon@p166:~ > hmm... Tom did you try lpr as root? HTH Jon Clausen BTW: Could one get bash to return 'permission denied' instead of 'command not found' ? (whenever the command is actually there, but you don't have the perms...) mostly curious ;)
On Sat, Aug 11, 2001 at 10:23:14AM +0200, Jon Clausen wrote:
On Friday 10 August 2001 21:18, Dave Smith wrote:
On Fri, Aug 10, 2001 at 01:27:38AM -0700, tompoe@source.net wrote:
I quickly brought up a terminal, typed lpr /etc/passwd, and the bash command returned a no such thing, lpr message. Looks like I can focus in on the problem, now. Thanks, again. Tom
tompoe@aether:~ > lpr /etc/passwd bash: lpr: command not found
Looks like you're missing a package, or that lpr isn't on your path. 'locate lpr' will give you all filenames on your system with lpr in the name.
Could this be a permissions issue?
Bash returns 'command not found' when you don't have the permissions too:
This is incorrect, see below.
jon@p166:~ > halt bash: halt: command not found jon@p166:~ >
BTW: Could one get bash to return 'permission denied' instead of 'command not found' ? (whenever the command is actually there, but you don't have the perms...) mostly curious ;)
Mmm. let's clear this up. "Command not found" means that the command either does not exist OR it is not to be found in your PATH. So the example above of "halt" is because halt is to be found in "/sbin" which is not usually in the path of a normal user, but is in that of "root's". However if the command IS in your path, but the permissions don't allow you to execute it, you get "permission denied". "Command not found" is bash, "Permission denied" is bash reporting an error from a system call. To see where a command is use the bash builtin "type", if type complains then the command is not in your PATH. Cliff
Bash returns 'command not found' when you don't have the permissions too:
This is incorrect, see below.
Right.. my mistake
Mmm. let's clear this up. "Command not found" means that the command either does not exist OR it is not to be found in your PATH. So the example above of "halt" is because halt is to be found in "/sbin" which is not usually in the path of a normal user, but is in that of "root's". However if the command IS in your path, but the permissions don't allow you to execute it, you get "permission denied". "Command not found" is bash, "Permission denied" is bash reporting an error from a system call.
O.K. this is, of course correct. Please disregard my previous post :)
To see where a command is use the bash builtin "type", if type complains then the command is not in your PATH.
'which' does more or less the same? Jon Clausen
participants (5)
-
Cliff Sarginson -
Dave Smith -
Jon Clausen -
pierre＠saiph.com -
tom poe