Re: python-mode: make sure output is not eaten

[Steven Huwig]

On Aug 23, 2006, at 12:04 AM, Stefan Monnier wrote:
> Yes, of course.  BTW do you have any idea why the current code uses  
> "\n\n"?

Might it be because the Python interactive interpreter needs the extra
newline due to significant whitespace?  E.g.

>>> for i in range(1,5):
...     print i,
...
1 2 3 4

a DEDENT token is created by the unindented second newline, closing
the block.  A single newline cannot do that as it is also the
statement terminator.

Probably it compensates for indented text without a trailing newline.
It doesn't look like python-mode itself has any situations where this
matters, but it is possible -- but unlikely -- for user input to be
affected.

If you do the following in python-mode with both versions:

C-c C-s for i in range(1, 5): C-q C-j
<tab> print i, <return>

you will see the difference in behavior.


-- Steven Huwig