Barry Warsaw wrote: > On Apr 16, 2010, at 11:27 AM, Andreas Roehler wrote: > >> trying to keep some experimental implementations synced >> semantically, I'm stumbling about the following: >> >> py-goto-block-up (&optional nomark) >> "Move up to start of current block. >> Go to the statement that starts the smallest enclosing block; roughly >> speaking, this will be the closest preceding statement that ends with a >> colon and is indented less than the statement you started on.... >> " >> >> IMHO it should rather be named into something like >> `py-goto-beginning-of-block' >> >> while `py-goto-block-up' indicates a higher level. > > Sure, I think this renaming makes sense.
OK, thanks. So I'll make a branch. FWIW, I rarely use this command. ;) > > -Barry I'm reflecting a set of commands following example of paredit.el's Depth-Changing Commands etc. http://mumble.net/~campbell/emacs/paredit/paredit.html Things like `paredit-splice-sexp-killing-backward' Just saying "block" where paredit.el says "list". Andreas _______________________________________________ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
