Barry Warsaw wrote: > On Jan 27, 2009, at 2:32 AM, Andreas Roehler wrote: > >>> If you don't change existing default behavior, you're cool. > >> Always have that in mind. Until now there is one changing concerning > >> py-beginning-of-def-or-class really "or" > >> So far I see no other need and this one might revoked if causing >> divorce... :) > > Sorry, remind me again about the change you want to make to this? > > Barry >
Goal was: commands should - speak for themselves - need no docu reading - be easily to put at a key or alias. Therefor, if we have a compound command, which with an option changes its behaviour, IMO its better to split it into two or more at the user level. Old function `py-beginning-of-def-or-class' is renamed to `py-beginning-of-def-or-class-if-arg', now adressed by either py-beginning-of-function, py-beginning-of-class, or py-beginning-of-def-or-class (really "or", i.e. stops at both) So old `py-beginning-of-def-or-class' remains the function with the guts and is called by the new introduced. In the last case (really "or") that way: (py-beginning-of-def-or-class-if-arg 'either arg) py-beginning-of-def-or-class-if-arg still exists as command, you may simply change the key if you want to use it as before. BTW: opened another account at lp. Thanks for introducing me to bazaar. Maybe have a look at http://bazaar.launchpad.net/~a-roehler/s-x-emacs-werkstatt/ Andreas Röhler _______________________________________________ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
