One of my biggest pet peeves is people who don't bother to read (or listen
to) carefully what someone is saying before they flame them. The kid tried
a google search and couldn't find what he wanted (how to TYPE the pipe
character, NOT what pipe is). You jumped on him and made an ass of yourself
because your response missed the point of his post.
> Pipe
> A data-channel ( | ) in RAM that takes output from a program and feeds
> the data as input to another program
>
> See the | That's the charter on your keyboard for pipe (shift +
> \)
>
The last sentence in your post is NOT part of that web page, so he still
wouldn't have had an answer to his question from that site.
If your response to him is a reflection of your normal persona at work, I
feel sorry for the "average" user who gets tech support from you. Being
part of the tech support team often means you have to support the least
competent users with a friendly smile and demeanor. BTW, when working in an
office, how hard is it to respond over your shoulder to answer a keyboarding
question. Hell, I don't mind taking a minute or two out of my workload to
educate a rookie if they're working hard and are sincere about learning. In
the process I can learn something new (maybe a subtle detail about that
topic/issue, maybe a new way to phrase something, or perhaps just a better
understanding of how other people think/react to situations).
Hell, there isn't much going on with the A+ exam on here right now, so
lighten up
-Breedo_