Sorry for the inline answer and my bad english. [EMAIL PROTECTED] am Freitag, 10. Juni 2005 15.14: > I whole heartedly agree!
(In this top posting manner, the sense of above sentence (at least for me) is: Somebody agrees, and does that _whole_heartedly_. Ok, it may be interesting sometimes to know if somebody agrees with verve and not just simply, but not in a perl mailing list). With what? > top post rules! Oh! Let's have a look: > Derek B. Smith > OhioHealth IT > UNIX / TSM / EDM Teams > > > > > > "Ryan Frantz" > <[EMAIL PROTECTED] > med-llc.com> To > "Wiggins d'Anconia" > 06/09/2005 04:13 <[EMAIL PROTECTED]>, > PM <[EMAIL PROTECTED]> > cc > <[EMAIL PROTECTED]>, > <beginners@perl.org> > Subject > RE: host id Derek B. Smith, Ryan Frantz, Wiggins d'Anconia and Bret.Goodfellow seem to diskuss something. But what? > [snipped 8 empty lines] > This? Or is this just a conveniance because of the surrounding chaos? > Sure, don't top-post. Pardon? A: "top post rules!" B: "Sure, don't top-post" > But then who's gonna bother to scroll to the end > of the email as the thread gets longer? And who's gonna bother to turn over the pages in a book whose read text gets longer and longer? > Many users don't even realize that there is a reply in bottom-posted emails. Huh? Why should somebody get an answer mail without an answer inside (apart from RE:AnotherSpam? > Bottom-posting ignores the natural behavior of most users. Because most users switch their natural behavior when they switch from talking to writing? > Another example of human behavior (top vs. bottom): > > Q: Where's the first place your eyes take you when you visit a web page? > A: The upper left quadrant of the page. Not the bottom. I'd say that the focussing of the first glance is appropriate for PR stuff, selling papers, etc. For an intellectual (and hopefully intelligent) discussion consisting of arguments, argument chains, explanations and tries to understand, it's certainly not useful. This holds even more if several people take part of the discussion. I think there is a difference between "natural" and "widespread". [...] So, the thing getting agreement must follow soon! > -----Original Message----- > From: Wiggins d'Anconia [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 09, 2005 4:02 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; beginners@perl.org > Subject: Re: host id Interesting, indeed. > "Because it's up-side down. > Why is that? > It makes replies harder to read. > Why not? > Please don't top-post." - Sherm Pendley, Mac OS X list > > [EMAIL PROTECTED] wrote: > > I, being too lazy to look up a perl function, would use hostname > > command in > > > backticks like so: > > > > $HostID = `hostname`; > > Right which is why the above is "too lazy". Anyone reading this please > don't settle for the above, it is error prone, insecure, and > insufficient. There is no error checking, there at least needs to be a > full path, and it is potentially slower. > > > Not sure if that will catch a newline character so I would also follow > > it > > > with this: > > > > $HostID =~ s/\n//; > > Right, in which case we can at least suggest 'chomp', > > perldoc -f chomp > > http://danconia.org > > > -----Original Message----- > > From: Bret Goodfellow [mailto:[EMAIL PROTECTED] > > Sent: Thursday, June 09, 2005 3:36 PM > > To: beginners@perl.org > > Subject: host id > > > > > > Simple question to answer, I hope. I am running on an HP-UX system, > > and > > > would like to retrive the UNIX system's host-id (name of box). Is > > there > > > a function to do this? A: "Simple question to answer, I hope. I am running on an HP-UX system," B: "and" A: "would like to retrive the UNIX system's host-id (name of box). Is" B: "there" A: "a function to do this?" Must be gurus. Don't understand anything. > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > <http://learn.perl.org/> <http://learn.perl.org/first-response> very useful citation... > -- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > <http://learn.perl.org/> <http://learn.perl.org/first-response> ...otherwise it would not be mentioned twice. Now, imagine my reply as top posting. I know it's difficult to convince people to reply inline. A lot of my customers even don't get it if their top post replies are so unclear that I have to write another mail to ask what they meant. Even after tens of chaotic discussions leading to misunderstandings they don't get it. They seem to think that it is "natural" that discussions per email are chaotic. Aaarrggghhh! joe -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>
