Ask Bjoern Hansen wrote:
I prefer not having any prompt to make cut'n'paste easier.
I agree with Ask, but... that's pretty much out of question, given my experience with the guide, too many users think the command lines are actually code or something else. So there should be a clear (documented) difference between code and prompts.
So far more people in favor of single char prompts. Plus I agree with Bill that sometimes it helps to show which dir you are inside complex install scenarios or similar situations.
Folks, remember that I've been doing the guide for 3.5 years, and what I'm saying is based solely on the questions I had to answer in those years, otherwise I agree with you all. Just remember that not all readers of the docs are as advanced as you :)
You'd laugh, but there were a few times when some readers couldn't make the example code work, because they've copy-n-pasted the header:
file:foo.pl ----------- #!/usr/bin/perl ... # some code
into the script as is (including the first two lines, or only the second line).
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
