summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBarry Warsaw <barry@python.org>1999-06-03 22:18:59 (GMT)
committerBarry Warsaw <barry@python.org>1999-06-03 22:18:59 (GMT)
commitc0d2d51dd2a57b4c26d3abec63860b90e93d34de (patch)
tree73f890cabcce7d1198313ddbbfbd955004b0d7e3
parentf4a15089a3452510c22a252c14d9da9dccba8168 (diff)
downloadcpython-c0d2d51dd2a57b4c26d3abec63860b90e93d34de.zip
cpython-c0d2d51dd2a57b4c26d3abec63860b90e93d34de.tar.gz
cpython-c0d2d51dd2a57b4c26d3abec63860b90e93d34de.tar.bz2
(py-statement-closes-block-p): py-goto-initial-line could leave us in
the line's whitespace. back-to-indentation should /follow/ this call.
-rw-r--r--Misc/python-mode.el4
1 files changed, 2 insertions, 2 deletions
diff --git a/Misc/python-mode.el b/Misc/python-mode.el
index 924c2c7..d30c1b3 100644
--- a/Misc/python-mode.el
+++ b/Misc/python-mode.el
@@ -150,7 +150,7 @@ you're editing someone else's Python code."
When this variable is non-nil, two things happen when a buffer is set
to `python-mode':
- 1. `py-indent-offset' is guess from existing code in the buffer.
+ 1. `py-indent-offset' is guessed from existing code in the buffer.
Only guessed values between 2 and 8 are considered. If a valid
guess can't be made (perhaps because you are visiting a new
file), then the value in `py-indent-offset' is used.
@@ -2929,8 +2929,8 @@ be at the start of a statement."
I.e., if the line starts with `return', `raise', `break', `continue',
and `pass'. This doesn't catch embedded statements."
(let ((here (point)))
- (back-to-indentation)
(py-goto-initial-line)
+ (back-to-indentation)
(prog1
(looking-at (concat py-block-closing-keywords-re "\\>"))
(goto-char here))))