This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author kbk
Recipients bmiller, cben, kbk, roger.serwy, terry.reedy
Date 2009-04-03.19:35:23
SpamBayes Score 2.402667e-11
Marked as misclassified No
Message-id <1238787325.79.0.755051042138.issue2704@psf.upfronthosting.co.za>
In-reply-to
Content
As far as typing in the comment widget goes - it 
works fine if you 
don't 
add CR at the end of the lines until you go back 
and edit it by 
inserting some text.  Then the faulty 
wordwrapping kicks in, and it 
has 
to be fixed by removing all the extra spaces and 
CR by hand.  The 
only 
way around it that I've found is to use hard CR.  
But then you have 
to 
second guess the right margin.  You'll notice 
that if you undo the 
wrapping it did on my comment, that the lines are 
shorter than in 
your 
comments! This paragraph was entered w/o returns. 
It gets screwed as 
soon as I click outside the widget. And the screwing 
depends on the width of my browser window, because that 
affect the width of the text entry widget.

Rev 62545 to 2.6 was forward ported to 3.0 on 
4May, r62716.  I'm 
using py3k HEAD and it works the same as 2.6: 
pressing Home toggles 
beween the left margin and the start of the code 
text.
History
Date User Action Args
2009-04-03 19:35:26kbksetrecipients: + kbk, terry.reedy, cben, bmiller, roger.serwy
2009-04-03 19:35:25kbksetmessageid: <1238787325.79.0.755051042138.issue2704@psf.upfronthosting.co.za>
2009-04-03 19:35:24kbklinkissue2704 messages
2009-04-03 19:35:23kbkcreate