[Python-mode] myrkwid bug with backspace/delete

[Andreas Röhler]

Am 01.04.2011 22:49, schrieb Barry Warsaw:
> On Apr 01, 2011, at 10:45 PM, Andreas Röhler wrote:
>
>> Am 01.04.2011 21:58, schrieb Barry Warsaw:
>>> On Apr 01, 2011, at 12:31 PM, Andreas Röhler wrote:
>>>
>>>> checked in fixes.  Also cured a mistake of 745208'-fix, where python- and
>>>> emacs-lisp logic has been came across...
>>>
>>> Thanks Andreas!  Things are looking better, but still not quite perfect. ;)
>>>
>>> -----snip snip-----
>>> def foo():
>>>       a = bar(one=1,
>>>               two=2,
>>>               three=3)
>>> -----snip snip-----
>>>
>>> Put point at the closing parenthesis and hit return.  You get lined up under
>>> the 't' in 'three' whereas you should be lined up under the 'a'.
>>
>> Hi Berry,
>>
>> it's lined below `t' indicating the multiline character.
>
> Right.  But after the closing of the bar() function call, the next line can't
> possibly occur under the 't' because you'll get an IndentationError:
>
> -----snip snip-----
> def foo():
>      a = bar(one=1,
>              two=2,
>              three=3)
>              x = 7
> -----snip snip-----
>>>> ## working on region in file /tmp/python-16786-mj.py...
> Traceback (most recent call last):
>    File "<stdin>", line 1, in<module>
>    File "/tmp/python-16786-mj.py", line 5
>      x = 7
>      ^
> IndentationError: unexpected indent
>
>> I'm afraid we are here in a sphere, were people will ask for different styles.
>>
>> Unless I miss something.
>
> Perhaps I didn't explain it well.

Hi Barry, hi Georg,

thanks, it's just my lacking experience.
Will need some help with python occassionally.

   Does the above example (default behavior
> for current myrkwid branch) make sense?
>


Yes. BTW let's look for the right name for this error.

What about: "column after assignement"?


Cheers

Andreas




>> What about storing that as a bug report and coming back at a later time?
>>
>> BTW after merge would adress the execute/shell/unicode errors.
>>
>> OTOH if you think it must be now it will be now... :-)
>
> This one I think has to be fixed now :)
>
> Cheers,
> -Barry