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

[Slawomir Nowaczyk <slawomir.nowaczyk.847@student.lu.se>]

On Wed, 30 Aug 2006 18:10:33 -0400
Stefan Monnier <monnier@iro.umontreal.ca> wrote:

#>>>> Agreed. But why is removing "_emacs_out ()" any more selective
#>>>> than removing ">>> _emacs_out ()"?
#>>> 
#>>> We're talking about "^_emacs_out " vs "^\\(>>> \\)?_emacs_out":
#>>> clearly one of the two regexps describes a superset of the other.
#>>> If you can guarantee that it'll always match "^>>> _emacs_out ",
#>>> then it's a different question.
#>
#>> I do not think it is a problem... The following patch seems to work
#>> for me:
#> 
#> But in what way is that better?

It probably isn't... but it does guarantee I can always match "^>>> _emacs_out" :)

#> > #> Also adding the assert to python-send-command did not restrict
#> > #> the user in any way, only the python.el hacker.
#> 
#> > Right. Fine, this is probably not important enough to warrant
#> > further discussion.
#> 
#> Especially since python-send-command doesn't wait for the command to
#> terminate any more, so it doesn't add any `print' any more, whether
#> on the same line or on a separate one.

Exactly.

-- 
 Best wishes,
   Slawomir Nowaczyk
     ( slawomir.nowaczyk.847@student.lu.se )

Be nice to other people--they outnumber you six billion to one.