summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBarry Warsaw <barry@python.org>1995-03-15 18:23:16 +0000
committerBarry Warsaw <barry@python.org>1995-03-15 18:23:16 +0000
commit4a68b93f76f44b07b8b8325646129b052351d4c0 (patch)
tree7d3fa7288dcdbfec6c8cc52d176a39aa44a983ee
parent0f3b5e600f71b99a953a434a55e6d164f2320ec1 (diff)
downloadcpython-4a68b93f76f44b07b8b8325646129b052351d4c0.tar.gz
#(py-electric-colon): updated comment
-rw-r--r--Misc/python-mode.el10
1 files changed, 5 insertions, 5 deletions
diff --git a/Misc/python-mode.el b/Misc/python-mode.el
index 15c62a69da..7c87c35a76 100644
--- a/Misc/python-mode.el
+++ b/Misc/python-mode.el
@@ -436,11 +436,11 @@ argument is provided, that many colons are inserted non-electrically."
(py-compute-indentation)))
)
(setq outdent py-indent-offset))
- ;; electric colon won't re-indent lines that start to the left
- ;; of the current computed indentation, under the assumption
- ;; that these are already outdented properly. Use TAB, C-c C-l
- ;; or C-c C-r to adjust. TBD: Is there a better way to
- ;; determine this???
+ ;; Don't indent, only outdent. This assumes that any lines that
+ ;; are already outdented relative to py-compute-indentation were
+ ;; put there on purpose. Its highly annoying to have `:' indent
+ ;; for you. Use TAB, C-c C-l or C-c C-r to adjust. TBD: Is
+ ;; there a better way to determine this???
(if (< (current-indentation) indent) nil
(goto-char here)
(beginning-of-line)