|
|
 |
 |
 |
 |
How to print in C
I want to print a specific portion of output screen using a printer. How can i do this using C commands??????? Thanks in advance
Sanchit wrote: > I want to print a specific portion of output screen using a printer. > How can i do this using C commands???????
By asking on a group dedicated to your platform. -- Ian Collins.
Sanchit wrote: > I want to print a specific portion of output screen using a printer. > How can i do this using C commands???????
There is no screen in standard C. Nor is there a printer. There are files which handle all communication with the outside world. Read the standard or N869.txt, at: <http://cbfalconer.home.att.net/download/n869_txt.bz2> (don't forget to expand the download with bzip2) -- <http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt> <http://www.securityfocus.com/columnists/423> <http://www.aaxnet.com/editor/edit043.html> <http://kadaitcha.cx/vista/dogsbreakfast/index.html> cbfalconer at maineline dot net -- Posted via a free Usenet account from http://www.teranews.com
CBFalconer said: That's like writing "may contain traces of nut" on a packet of peanuts. -- Richard Heathfield "Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk email: rjh at the above domain, - www.
In article <ANidnUQWpbc9CcDbRVny@bt.com>, Richard Heathfield <r@see.sig.invalid> wrote: >That's like writing "may contain traces of nut" on a packet of peanuts.
Technically, peanuts aren't nuts. They're a kind of fish. -- Richard -- "Consideration shall be given to the need for as many as 32 characters in some alphabets" - X3.4, 1963.
Richard Tobin wrote: > In article <ANidnUQWpbc9CcDbRVny @bt.com>, > Richard Heathfield <r @see.sig.invalid> wrote: >> That's like writing "may contain traces of nut" on a packet of peanuts. > Technically, peanuts aren't nuts. They're a kind of fish.
But not a true fish, since they don't have bones except for their teeth and jaws.
At least one person complained bitterly that he hadn't been told in advance how to unpack the file. (Haven't seen him lately.) -- Keith Thompson (The_Other_Keith) k@mib.org <http://www.ghoti.net/~kst> San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst> "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"
Keith Thompson said: > Richard Heathfield <r @see.sig.invalid> writes: >> CBFalconer said: >>> < http://cbfalconer.home.att.net/download/n869_txt.bz2> >>> (don't forget to expand the download with bzip2) >> That's like writing "may contain traces of nut" on a packet of >> peanuts. > At least one person complained bitterly that he hadn't been told in > advance how to unpack the file.
Yes, I know. Or, to paraphrase, he complained bitterly that the packet of peanuts didn't say "may contain traces of nut". That's my point - i.e. I am not convinced that pandering to such people is wise. > (Haven't seen him lately.)
Shhh... :-) -- Richard Heathfield "Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk email: rjh at the above domain, - www.
You don't know the number of messages I have seen in the past, of roughly the form "I can't read that". Anticipation is normally golden. -- <http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt> <http://www.securityfocus.com/columnists/423> <http://www.aaxnet.com/editor/edit043.html> <http://kadaitcha.cx/vista/dogsbreakfast/index.html> cbfalconer at maineline dot net -- Posted via a free Usenet account from http://www.teranews.com
CBFalconer <cbfalco @yahoo.com> writes: > Richard Heathfield wrote: >> CBFalconer said: >>> <http://cbfalconer.home.att.net/download/n869_txt.bz2> >>> (don't forget to expand the download with bzip2) >> That's like writing "may contain traces of nut" on a packet of peanuts. > You don't know the number of messages I have seen in the past, of > roughly the form "I can't read that". Anticipation is normally > golden.
To be fair, bzip2 is primarily a Unixish tool; someone with little or no exposure to Unixish systems might not be familiar with it. On the other hand, any reasonably competent person should know enough to do a web search for "bz2"; the first hit provides more than enough information. On the other other hand, the reminder to use bzip2 is perfectly sensible IMHO; the relationship between ".bz2" and "bzip2" is not as well known as the relationship between "peanuts" and "nuts". -- Keith Thompson (The_Other_Keith) k@mib.org <http://www.ghoti.net/~kst> San Diego Supercomputer Center <*> <http://users.sdsc.edu/~kst> "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"
Keith Thompson <k @mib.org> writes: > CBFalconer <cbfalco @yahoo.com> writes: >> Richard Heathfield wrote: >>> CBFalconer said: >>>> <http://cbfalconer.home.att.net/download/n869_txt.bz2> >>>> (don't forget to expand the download with bzip2) >>> That's like writing "may contain traces of nut" on a packet of peanuts. >> You don't know the number of messages I have seen in the past, of >> roughly the form "I can't read that". Anticipation is normally >> golden. > To be fair, bzip2 is primarily a Unixish tool; someone with little or > no exposure to Unixish systems might not be familiar with it. > On the other hand, any reasonably competent person should know enough > to do a web search for "bz2"; the first hit provides more than enough > information. > On the other other hand, the reminder to use bzip2 is perfectly > sensible IMHO; the relationship between ".bz2" and "bzip2" is not as > well known as the relationship between "peanuts" and "nuts".
If you follow that rational then anytime you mention anything that *even one person* does not understand then you should provide a caveat. It is anal in the extreme to tell people how to open a bz2 file with each reference to that file.
"Keith Thompson" writes: > On the other other hand, the reminder to use bzip2 is perfectly > sensible IMHO; the relationship between ".bz2" and "bzip2" is not as > well known as the relationship between "peanuts" and "nuts".
And it's only a question of time until somealert reader points out that a peanut is not a nut. :-(
Clever Monkey wrote: > Richard Tobin wrote: > > In article <ANidnUQWpbc9CcDbRVny@bt.com>, > > Richard Heathfield <r@see.sig.invalid> wrote: > >> That's like writing "may contain traces of nut" on a packet of peanuts. > > Technically, peanuts aren't nuts. They're a kind of fish. > But not a true fish, since they don't have bones except for their teeth > and jaws.
And don't forget -- you can't tuna fish. -- +-------------------------+--------------------+-----------------------+ | Kenneth J. Brody | www.hvcomputer.com | #include | | kenbrody/at\spamcop.net | www.fptech.com | <std_disclaimer.h> | +-------------------------+--------------------+-----------------------+ Don't e-mail me at: <mailto:ThisIsASpamT@gmail.com>
osmium said: > "Keith Thompson" writes: >> On the other other hand, the reminder to use bzip2 is perfectly >> sensible IMHO; the relationship between ".bz2" and "bzip2" is not as >> well known as the relationship between "peanuts" and "nuts". > And it's only a question of time until somealert reader points out > that a peanut is not a nut. :-(
You're too late. See upthread... -- Richard Heathfield "Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk email: rjh at the above domain, - www.
"Richard Heathfield" wrote: > osmium said: >> And it's only a question of time until somealert reader points out >> that a peanut is not a nut. :-( > You're too late. See upthread...
What I saw said that it was a fish - which made no sense to me at all. It still doesn't. What I was referring to was that the peanut is a legume. Which is not very esoteric but in fact true.
On 30 Mai, 12:07, Sanchit <sanchitgupt@gmail.com> wrote: > I want to print a specific portion of output screen using a printer. > How can i do this using C commands???????
Commands are part of your OS, not part of the C language. C FAQ: Question 19.8 and Question 19.25 Furthermore, to interface external devices, check your platform doc. -- Tor
Richard wrote: > Keith Thompson <k @mib.org> writes: >> CBFalconer <cbfalco @yahoo.com> writes: >>> Richard Heathfield wrote: >>>> CBFalconer said: >>>>> <http://cbfalconer.home.att.net/download/n869_txt.bz2> >>>>> (don't forget to expand the download with bzip2) >>>> That's like writing "may contain traces of nut" on a packet of >>>> peanuts. >>> You don't know the number of messages I have seen in the past, >>> of roughly the form "I can't read that". Anticipation is >>> normally golden. ... snip ... >> On the other other hand, the reminder to use bzip2 is perfectly >> sensible IMHO; the relationship between ".bz2" and "bzip2" is not >> as well known as the relationship between "peanuts" and "nuts". > If you follow that rational then anytime you mention anything that > *even one person* does not understand then you should provide a > caveat. > It is anal in the extreme to tell people how to open a bz2 file > with each reference to that file.
1. You are rude and crude. 2. I didn't tell people how to 'open' a bz2 file, I advised them to expand it. 3. I also mentioned the program that would do so. -- <http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt> <http://www.securityfocus.com/columnists/423> <http://www.aaxnet.com/editor/edit043.html> <http://kadaitcha.cx/vista/dogsbreakfast/index.html> cbfalconer at maineline dot net -- Posted via a free Usenet account from http://www.teranews.com
osmium wrote: > "Richard Heathfield" wrote: >> osmium said: >>> And it's only a question of time until somealert reader points out >>> that a peanut is not a nut. :-( >> You're too late. See upthread... > What I saw said that it was a fish - which made no sense to me at all. It > still doesn't. What I was referring to was that the peanut is a legume. > Which is not very esoteric but in fact true.
Is that you're way of saying he's not funny? Or do you really not get it?
CBFalconer <cbfalco @yahoo.com> writes: > Richard wrote: >> Keith Thompson <k @mib.org> writes: >>> CBFalconer <cbfalco @yahoo.com> writes: >>>> Richard Heathfield wrote: >>>>> CBFalconer said: >>>>>> <http://cbfalconer.home.att.net/download/n869_txt.bz2> >>>>>> (don't forget to expand the download with bzip2) >>>>> That's like writing "may contain traces of nut" on a packet of >>>>> peanuts. >>>> You don't know the number of messages I have seen in the past, >>>> of roughly the form "I can't read that". Anticipation is >>>> normally golden. > ... snip ... >>> On the other other hand, the reminder to use bzip2 is perfectly >>> sensible IMHO; the relationship between ".bz2" and "bzip2" is not >>> as well known as the relationship between "peanuts" and "nuts". >> If you follow that rational then anytime you mention anything that >> *even one person* does not understand then you should provide a >> caveat. >> It is anal in the extreme to tell people how to open a bz2 file >> with each reference to that file. > 1. You are rude and crude. 2. I didn't tell people how to 'open'
"anal" is not rude in the context. It seems quite appropriate for a serial nagger with nothing better to do than tell people how to open bog standard compressed files and that they are "off topic" or to snip examples and give links to text versions of C standards which bear no relation to the question asked. > a bz2 file, I advised them to expand it.
refer to above. great advice. because, err, they wouldn't be able to read it otherwise. > 3. I also mentioned the > program that would do so.
Do you refer people to your compiler of choice too when you tell them to compile a program? You're clearly of the opinion that you are some sort of NG moderator so I'll save you from my scorn by dumping you in my killfile. Besides your signatures wont snip for some reason and they are driving me crazy. Bye now! --
Keith Thompson wrote: > Richard Heathfield <r@see.sig.invalid> writes: > > CBFalconer said: > >> <http://cbfalconer.home.att.net/download/n869_txt.bz2> > >> (don't forget to expand the download with bzip2) > > That's like writing "may contain traces of nut" on a packet of peanuts. > At least one person complained bitterly that he hadn't been told in > advance how to unpack the file. (Haven't seen him lately.)
And then there are those who "know better", and refuse to use the flags you tell them to use, and then complain that there's something wrong with your install image. BTDTGTTS -- +-------------------------+--------------------+-----------------------+ | Kenneth J. Brody | www.hvcomputer.com | #include | | kenbrody/at\spamcop.net | www.fptech.com | <std_disclaimer.h> | +-------------------------+--------------------+-----------------------+ Don't e-mail me at: <mailto:ThisIsASpamT@gmail.com>
Richard said: > CBFalconer <cbfalco @yahoo.com> writes: >> Richard wrote: <snip> >>> It is anal in the extreme to tell people how to open a bz2 file >>> with each reference to that file. >> 1. You are rude and crude. 2. I didn't tell people how to 'open' > "anal" is not rude in the context.
From where I'm standing, it's rude and crude, unless the context is strictly medical or biological - and comp.lang.c is neither of those. You might not think it so, but it's a very subjective matter. I'm not telling you what you can and can't say - I'm just telling you my own perception of the word. Naturally, your opinion might vary - but normally we don't use words that we know will offend people (no matter how inoffensive those words seem to us), unless we are deliberately setting out to offend them. > It seems quite appropriate for a serial nagger
Why don't you find something useful to do instead of complaining all the time about people complaining all the time? Why not start off by helping out with some of these people asking C questions? > You're clearly of the opinion that you are some sort of NG moderator
In an unmoderated group, *everybody* is a moderator. > so I'll save you from my scorn by dumping you in my killfile.
That's one moderation technique, yes. See? You're a clc moderator too. > Besides > your signatures wont snip for some reason and they are driving me > crazy.
My newsreader recognises and snips them just fine. Get a better newsreader. -- Richard Heathfield "Usenet is a strange place" - dmr 29/7/1999 http://www.cpax.org.uk email: rjh at the above domain, - www.
osmium wrote: > "Richard Heathfield" wrote: >> osmium said: >>> And it's only a question of time until somealert reader points >>> out that a peanut is not a nut. :-( >> You're too late. See upthread... > What I saw said that it was a fish - which made no sense to me at > all. It still doesn't. What I was referring to was that the > peanut is a legume. Which is not very esoteric but in fact true.
What is esoteric about a peanut? I just eat them (in general) :-) -- <http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.txt> <http://www.securityfocus.com/columnists/423> <http://www.aaxnet.com/editor/edit043.html> <http://kadaitcha.cx/vista/dogsbreakfast/index.html> cbfalconer at maineline dot net -- Posted via a free Usenet account from http://www.teranews.com
On Wed, 30 May 2007 17:20:21 -0400, in comp.lang.c , Kenneth Brody <kenbr @spamcop.net> wrote: >Clever Monkey wrote: >> Richard Tobin wrote: >> > In article <ANidnUQWpbc9CcDbRVny@bt.com>, >> > Richard Heathfield <r@see.sig.invalid> wrote: >> >> That's like writing "may contain traces of nut" on a packet of peanuts. >> > Technically, peanuts aren't nuts. They're a kind of fish. >> But not a true fish, since they don't have bones except for their teeth >> and jaws. >And don't forget -- you can't tuna fish.
No need, they're already in a C.... (say it out loud, it'll make sense...) Hey, and its almost topical. -- Mark McIntyre "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." --Brian Kernighan
On Thu, 31 May 2007 10:43:47 -0400, in comp.lang.c , shadowman <shadow @noemail.com> wrote: >Or do you really not get it? Someone better explain why "peanut" and "fish" are synonyms. It makes no sense to me either (though I simply ignored the apparent joke). -- Mark McIntyre "Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it." --Brian Kernighan
|
 |
 |
 |
 |
|