lp:~mwhudson/pyrepl/trunk

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

99. By agaynor on 2010-11-16

Added readline.get_line_buffer

98. By antocuni on 2010-11-16

use setuptools instead of distutils

97. By antocuni on 2010-11-16

(antocuni, arigo) we need to reset all the flags on the input file descriptor,
else the console will be in "cooked mode" after we resume the job, and things
could be messed up (try uncomment the call do prepare() and press CTRL-D or
arrow keys immediately after the resuming and see what happens :-))

96. By antocuni on 2010-11-15

display tab characters as 4 spaces, not as ^I

95. By antocuni on 2010-11-12

emulate readline even more, and sort completions "by column" instead of "by row"

94. By antocuni on 2010-11-12

try to match the behaviour of readline even more: ReadlineALikeReader does not
show completions inside brackets, while pyrepl still does

93. By antocuni on 2010-11-12

try to match more closely the behaviour of readline in case there is an unique
completion followed by a <TAB> (this semantic is e.g. exploited by
fancycompleter to automatically complete unique prefixes)

92. By antocuni on 2010-11-12

always set the dirty flag when we press enter: this makes pyrepl to hide (if
it's visible) the completion menu before going to the next line

91. By antocuni on 2010-11-07

take care of escape sequences when computing the lenght of menu entries,
because in that case the length of the string might be different than the
number of characters actually displayed. This lets pyrepl to display colored completions

90. By antocuni on 2010-06-21

don't propagate exceptions raised inside the completer. This mimic the
behavior of cpython's readline, and it's very unpleasant to see your
interpreter crashing just because you hit <TAB> and there is an error in the
completer