Possibly better loop construct, also labels+goto important and on the fly compiler idea.

[rurpy at yahoo.com]

On 10/26/2013 07:45 PM, rusi wrote:
> On Sunday, October 27, 2013 2:07:53 AM UTC+5:30, Peter Cacioppi wrote:
>> Rusi said:
>> 
>> "Users of GG are requested to read and follow these instructions
>> https://wiki.python.org/moin/GoogleGroupsPython " 
>> 
>> Seriously, it's not exactly clear what protocol GG users are expected follow 
>> to make posts hygenic.

First, thanks (both of you) very much for the feedback.  I originally 
wrote that page.

> Yes... that page is longer and more confusing than necessary.
> 1. The double-posting bit is unnecessary -- not been happening after the 'new' GG.

OK, I have not seen the the cc option in a long time either.

> 2. The missing attributions problem is new and needs to be added

I don't understand this.  When I use GG I have not noticed missing
attributions.  Do you have any idea under what circumstances it happens?

> 3. The main message of that page that needs to be noted is
> - to remove extra spurious lines

That is point #2 on the page, right after the point about double posting
and will be #1 when the double posting point is removed.  Are you saying
that is it not prominent enough, or not clear enough?
 
> - to NOT top-post

Good point, I'll add that.

>> The standards I've used when creating this sort of 
>> content is to use screen shots with arrows and circles drawn in. If you're 
>> going to make an instruction page for some nuanced client feature, spend an 
>> extra 10 minutes and make it fully idiot proof.
> 
> Please do!
> If I were in charge I would say "Patches welcome!"
> Who is the 'you' you think you are addressing?

If me, I'll think about it but given that the page is instructions
about how to modify text, pictures would not come to my mind immediately
as being most appropriate.

Thanks again though for the suggestions.