| Original Content of Parent |
|---|
| That’s only true if you pretend that Microsoft culture is all that exists, which I often think you do. The FORWARD part is hardly “accepted” unless you qualify that by specifically stating who has accepted it. And it quite demonstrably is not necessary. It is a Microsoft-shibboleth that marks the speaker. It is very foreign, even alien, in Unix culture. |
That’s only true if you pretend that Microsoft culture is all that exists
I don't know how you got the impression that I said or implied it can't be called just "slash", but that's the only way I see that your arguments makes sense.
It is a Microsoft-shibboleth that marks the speaker. It is very foreign, even alien, in Unix culture.
Jargon is context-specific by definition. So what if the term is inappropriate in another context.
That doesn't mean that I'm buying your premise. The same typists that require this term would have the same responses in unix as in Windows. Perhaps you haven't spent enough time in end-user IT support, or perhaps your users were different, but that doesn't make "forward slash" wrong.
| [reply]
[d/l] |
BECAUSE THE PRISONERS OF $BILL
uh, I'm a long time unix user.
TOOK SEVERE OFFENCE AT THE MEREST SUGGESTION THAT THEIR QUAINT JARGON WAS ANYTHING BUT UNIVERSAL AND OBLIGATORY.
Stop lying about what I've done. This is the third time you've done this in this thread. You're the only one who hinted that it might be universal or obligatory. Any confusion should have been cleared by my second reply, so you're willfully being jerk, perhaps even ignorant.
| [reply] |