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 atagar1
Recipients atagar1
Date 2011-09-13.15:29:31
SpamBayes Score 2.82588e-11
Marked as misclassified No
Message-id <1315927772.69.0.871921956001.issue12972@psf.upfronthosting.co.za>
In-reply-to
Content
Hi, when using terminal coloring codes (for instance '\x1b[32mhello world\x1b[0m' for a green 'hello world') the raw_input function and readline module behave well except under a very specific use case...

========================================

import readline # provides history via up/down

prompt = '\x1b[32m>>> \x1b[0m' # green '>>> ' prompt

while True:
  raw_input(prompt)

========================================

This provides a green prompt and up/down cycles through prior input. This works well as long as the input is shorter than the prompt string length (in this case 13 characters). However, if the input is longer than the prompt then up/down thinks that the first thirteen rendered characters now belong to the prompt. For instance...

atagar@fenrir:~/Desktop/arm$ python tmp.py 
>>> http://docs.python.org/library/readline

Press up, then down to get back to a blank prompt. You'll have...
>>> http://do

This is probably due to a len() check on the raw_input argument...
>>> len('>>> http://do')
13
>>> len('\x1b[32m>>> \x1b[0m')
13

I'm at a bit of a loss for investigating this further - help would be appreciated! -Damian
History
Date User Action Args
2011-09-13 15:29:32atagar1setrecipients: + atagar1
2011-09-13 15:29:32atagar1setmessageid: <1315927772.69.0.871921956001.issue12972@psf.upfronthosting.co.za>
2011-09-13 15:29:32atagar1linkissue12972 messages
2011-09-13 15:29:31atagar1create