[V] Re: beginning-of-defun bug

[Stephen J. Turnbull]

Andreas Roehler writes:
 > Stephen J. Turnbull wrote:
 > > Andreas Roehler writes:
 > > 
 > >  > Why invent extras when cleaning up the base is possible?
 > > 
 > > Read my lips: The first argument to a generic movement command
 > 
 > Don't see such a generic thing at all.

forward-char, forward-word, end-of-line, forward-paragraph, etc etc.
They *all* behave the same way: the argument is a repeat count,
defaulting to 1.

 > Could you allow it coming into your mind Barry Warsaw, Tim Peters
 > or whoever introduced py-beginning-of-def-or-class as replacement
 > into python-mode.el, might have reflected its cause?

Sure.  Python-mode does a lot of things inconsistently with the normal
Emacs behavior.  You haven't noticed me patching them away, have you?
But that is quite different from changing behavior that is very
regular across many similar commands in the core, simply because one
unusual mode has historically done it differently.

 > So why block them?

They're not being blocked; I showed you how to work around the issue
by marshaling the arguments.  Alternatively, just bind C-M-a to
py-beginning-of-def-or-class.

 > Any precise complaint about it?

Go back and read the thread.  The precise complaints have all been
explained, several times; you are ignoring them.