|
2
|
1 ;;; python-mode.el --- Major mode for editing Python programs
|
|
|
2
|
|
|
3 ;; Copyright (C) 1992,1993,1994 Tim Peters
|
|
|
4
|
|
98
|
5 ;; Author: 1995-1997 Barry A. Warsaw
|
|
2
|
6 ;; 1992-1994 Tim Peters
|
|
|
7 ;; Maintainer: python-mode@python.org
|
|
|
8 ;; Created: Feb 1992
|
|
102
|
9 ;; Version: 2.90
|
|
|
10 ;; Last Modified: 1997/02/24 03:37:22
|
|
2
|
11 ;; Keywords: python languages oop
|
|
|
12
|
|
|
13 ;; This software is provided as-is, without express or implied
|
|
|
14 ;; warranty. Permission to use, copy, modify, distribute or sell this
|
|
|
15 ;; software, without fee, for any purpose and by any individual or
|
|
|
16 ;; organization, is hereby granted, provided that the above copyright
|
|
|
17 ;; notice and this paragraph appear in all copies.
|
|
|
18
|
|
|
19 ;;; Commentary:
|
|
|
20
|
|
|
21 ;; This is a major mode for editing Python programs. It was developed
|
|
|
22 ;; by Tim Peters after an original idea by Michael A. Guravage. Tim
|
|
4
|
23 ;; subsequently left the net; in 1995, Barry Warsaw inherited the
|
|
|
24 ;; mode and is the current maintainer.
|
|
2
|
25
|
|
|
26 ;; At some point this mode will undergo a rewrite to bring it more in
|
|
|
27 ;; line with GNU Emacs Lisp coding standards, and to wax all the Emacs
|
|
|
28 ;; 18 support. But all in all, the mode works exceedingly well, and
|
|
|
29 ;; I've simply been tweaking it as I go along. Ain't it wonderful
|
|
|
30 ;; that Python has a much more sane syntax than C? (or <shudder> C++?!
|
|
|
31 ;; :-). I can say that; I maintain cc-mode!
|
|
|
32
|
|
|
33 ;; The following statements, placed in your .emacs file or
|
|
|
34 ;; site-init.el, will cause this file to be autoloaded, and
|
|
|
35 ;; python-mode invoked, when visiting .py files (assuming this file is
|
|
|
36 ;; in your load-path):
|
|
|
37 ;;
|
|
|
38 ;; (autoload 'python-mode "python-mode" "Python editing mode." t)
|
|
|
39 ;; (setq auto-mode-alist
|
|
|
40 ;; (cons '("\\.py$" . python-mode) auto-mode-alist))
|
|
|
41 ;;
|
|
|
42 ;; If you want font-lock support for Python source code (a.k.a. syntax
|
|
|
43 ;; coloring, highlighting), add this to your .emacs file:
|
|
|
44 ;;
|
|
|
45 ;; (add-hook 'python-mode-hook 'turn-on-font-lock)
|
|
|
46 ;;
|
|
|
47 ;; But you better be sure you're version of Emacs supports
|
|
|
48 ;; font-lock-mode! As of this writing, the latest Emacs and XEmacs
|
|
|
49 ;; 19's do.
|
|
|
50
|
|
|
51 ;; Here's a brief list of recent additions/improvements/changes:
|
|
|
52 ;;
|
|
|
53 ;; - Wrapping and indentation within triple quote strings now works.
|
|
|
54 ;; - `Standard' bug reporting mechanism (use C-c C-b)
|
|
|
55 ;; - py-mark-block was moved to C-c C-m
|
|
|
56 ;; - C-c C-v shows you the python-mode version
|
|
|
57 ;; - a basic python-font-lock-keywords has been added for (X)Emacs 19
|
|
|
58 ;; - proper interaction with pending-del and del-sel modes.
|
|
|
59 ;; - Better support for outdenting: py-electric-colon (:) and
|
|
|
60 ;; py-indent-line (TAB) improvements; one level of outdentation
|
|
4
|
61 ;; added after a return, raise, break, pass, or continue statement.
|
|
|
62 ;; Defeated by prefixing command with C-u.
|
|
2
|
63 ;; - New py-electric-colon (:) command for improved outdenting Also
|
|
|
64 ;; py-indent-line (TAB) should handle outdented lines better
|
|
|
65 ;; - improved (I think) C-c > and C-c <
|
|
|
66 ;; - py-(forward|backward)-into-nomenclature, not bound, but useful on
|
|
|
67 ;; M-f and M-b respectively.
|
|
|
68 ;; - integration with imenu by Perry A. Stoll <stoll@atr-sw.atr.co.jp>
|
|
|
69 ;; - py-indent-offset now defaults to 4
|
|
|
70 ;; - new variable py-honor-comment-indentation
|
|
|
71 ;; - comment-region bound to C-c #
|
|
|
72 ;; - py-delete-char obeys numeric arguments
|
|
|
73 ;; - Small modification to rule for "indenting comment lines", such
|
|
|
74 ;; lines must now also be indented less than or equal to the
|
|
|
75 ;; indentation of the previous statement.
|
|
|
76
|
|
|
77 ;; Here's a brief to do list:
|
|
|
78 ;;
|
|
|
79 ;; - Better integration with gud-mode for debugging.
|
|
|
80 ;; - Rewrite according to GNU Emacs Lisp standards.
|
|
|
81 ;; - possibly force indent-tabs-mode == nil, and add a
|
|
|
82 ;; write-file-hooks that runs untabify on the whole buffer (to work
|
|
|
83 ;; around potential tab/space mismatch problems). In practice this
|
|
|
84 ;; hasn't been a problem... yet.
|
|
|
85 ;; - have py-execute-region on indented code act as if the region is
|
|
|
86 ;; left justified. Avoids syntax errors.
|
|
4
|
87 ;; - Add a py-goto-error or some such that would scan an exception in
|
|
|
88 ;; the py-shell buffer, and pop you to that line in the file.
|
|
2
|
89
|
|
|
90 ;; If you can think of more things you'd like to see, drop me a line.
|
|
|
91 ;; If you want to report bugs, use py-submit-bug-report (C-c C-b).
|
|
|
92 ;;
|
|
|
93 ;; Note that I only test things on XEmacs 19 and to some degree on
|
|
|
94 ;; Emacs 19. If you port stuff to FSF Emacs 19, or Emacs 18, please
|
|
|
95 ;; send me your patches. Byte compiler complaints can probably be
|
|
|
96 ;; safely ignored.
|
|
|
97
|
|
|
98 ;;; Code:
|
|
|
99
|
|
|
100
|
|
|
101 ;; user definable variables
|
|
|
102 ;; vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
|
|
|
103
|
|
|
104 (defvar py-python-command "python"
|
|
|
105 "*Shell command used to start Python interpreter.")
|
|
|
106
|
|
|
107 (defvar py-indent-offset 4
|
|
|
108 "*Indentation increment.
|
|
|
109 Note that `\\[py-guess-indent-offset]' can usually guess a good value
|
|
|
110 when you're editing someone else's Python code.")
|
|
|
111
|
|
|
112 (defvar py-align-multiline-strings-p t
|
|
|
113 "*Flag describing how multiline triple quoted strings are aligned.
|
|
|
114 When this flag is non-nil, continuation lines are lined up under the
|
|
|
115 preceding line's indentation. When this flag is nil, continuation
|
|
|
116 lines are aligned to column zero.")
|
|
|
117
|
|
|
118 (defvar py-block-comment-prefix "## "
|
|
|
119 "*String used by \\[comment-region] to comment out a block of code.
|
|
|
120 This should follow the convention for non-indenting comment lines so
|
|
|
121 that the indentation commands won't get confused (i.e., the string
|
|
|
122 should be of the form `#x...' where `x' is not a blank or a tab, and
|
|
|
123 `...' is arbitrary).")
|
|
|
124
|
|
|
125 (defvar py-honor-comment-indentation t
|
|
|
126 "*Controls how comment lines influence subsequent indentation.
|
|
|
127
|
|
|
128 When nil, all comment lines are skipped for indentation purposes, and
|
|
|
129 in Emacs 19, a faster algorithm is used.
|
|
|
130
|
|
|
131 When t, lines that begin with a single `#' are a hint to subsequent
|
|
|
132 line indentation. If the previous line is such a comment line (as
|
|
|
133 opposed to one that starts with `py-block-comment-prefix'), then it's
|
|
|
134 indentation is used as a hint for this line's indentation. Lines that
|
|
|
135 begin with `py-block-comment-prefix' are ignored for indentation
|
|
|
136 purposes.
|
|
|
137
|
|
|
138 When not nil or t, comment lines that begin with a `#' are used as
|
|
|
139 indentation hints, unless the comment character is in column zero.")
|
|
|
140
|
|
|
141 (defvar py-scroll-process-buffer t
|
|
|
142 "*Scroll Python process buffer as output arrives.
|
|
|
143 If nil, the Python process buffer acts, with respect to scrolling, like
|
|
|
144 Shell-mode buffers normally act. This is surprisingly complicated and
|
|
|
145 so won't be explained here; in fact, you can't get the whole story
|
|
|
146 without studying the Emacs C code.
|
|
|
147
|
|
|
148 If non-nil, the behavior is different in two respects (which are
|
|
|
149 slightly inaccurate in the interest of brevity):
|
|
|
150
|
|
|
151 - If the buffer is in a window, and you left point at its end, the
|
|
|
152 window will scroll as new output arrives, and point will move to the
|
|
|
153 buffer's end, even if the window is not the selected window (that
|
|
|
154 being the one the cursor is in). The usual behavior for shell-mode
|
|
|
155 windows is not to scroll, and to leave point where it was, if the
|
|
|
156 buffer is in a window other than the selected window.
|
|
|
157
|
|
|
158 - If the buffer is not visible in any window, and you left point at
|
|
|
159 its end, the buffer will be popped into a window as soon as more
|
|
|
160 output arrives. This is handy if you have a long-running
|
|
|
161 computation and don't want to tie up screen area waiting for the
|
|
|
162 output. The usual behavior for a shell-mode buffer is to stay
|
|
|
163 invisible until you explicitly visit it.
|
|
|
164
|
|
|
165 Note the `and if you left point at its end' clauses in both of the
|
|
|
166 above: you can `turn off' the special behaviors while output is in
|
|
|
167 progress, by visiting the Python buffer and moving point to anywhere
|
|
|
168 besides the end. Then the buffer won't scroll, point will remain where
|
|
|
169 you leave it, and if you hide the buffer it will stay hidden until you
|
|
|
170 visit it again. You can enable and disable the special behaviors as
|
|
|
171 often as you like, while output is in progress, by (respectively) moving
|
|
|
172 point to, or away from, the end of the buffer.
|
|
|
173
|
|
|
174 Warning: If you expect a large amount of output, you'll probably be
|
|
|
175 happier setting this option to nil.
|
|
|
176
|
|
|
177 Obscure: `End of buffer' above should really say `at or beyond the
|
|
|
178 process mark', but if you know what that means you didn't need to be
|
|
|
179 told <grin>.")
|
|
|
180
|
|
|
181 (defvar py-temp-directory
|
|
|
182 (let ((ok '(lambda (x)
|
|
|
183 (and x
|
|
|
184 (setq x (expand-file-name x)) ; always true
|
|
|
185 (file-directory-p x)
|
|
|
186 (file-writable-p x)
|
|
|
187 x))))
|
|
|
188 (or (funcall ok (getenv "TMPDIR"))
|
|
|
189 (funcall ok "/usr/tmp")
|
|
|
190 (funcall ok "/tmp")
|
|
|
191 (funcall ok ".")
|
|
|
192 (error
|
|
|
193 "Couldn't find a usable temp directory -- set py-temp-directory")))
|
|
|
194 "*Directory used for temp files created by a *Python* process.
|
|
|
195 By default, the first directory from this list that exists and that you
|
|
|
196 can write into: the value (if any) of the environment variable TMPDIR,
|
|
|
197 /usr/tmp, /tmp, or the current directory.")
|
|
|
198
|
|
|
199 (defvar py-beep-if-tab-change t
|
|
|
200 "*Ring the bell if tab-width is changed.
|
|
|
201 If a comment of the form
|
|
|
202
|
|
|
203 \t# vi:set tabsize=<number>:
|
|
|
204
|
|
|
205 is found before the first code line when the file is entered, and the
|
|
|
206 current value of (the general Emacs variable) `tab-width' does not
|
|
|
207 equal <number>, `tab-width' is set to <number>, a message saying so is
|
|
|
208 displayed in the echo area, and if `py-beep-if-tab-change' is non-nil
|
|
|
209 the Emacs bell is also rung as a warning.")
|
|
|
210
|
|
102
|
211 (defvar python-font-lock-keywords
|
|
4
|
212 (let* ((keywords '("and" "break" "class"
|
|
2
|
213 "continue" "def" "del" "elif"
|
|
|
214 "else:" "except" "except:" "exec"
|
|
|
215 "finally:" "for" "from" "global"
|
|
|
216 "if" "import" "in" "is"
|
|
|
217 "lambda" "not" "or" "pass"
|
|
|
218 "print" "raise" "return" "try:"
|
|
|
219 "while"
|
|
|
220 ))
|
|
|
221 (kwregex (mapconcat 'identity keywords "\\|")))
|
|
|
222 (list
|
|
|
223 ;; keywords not at beginning of line
|
|
|
224 (cons (concat "\\s-\\(" kwregex "\\)[ \n\t(]") 1)
|
|
|
225 ;; keywords at beginning of line. i don't think regexps are
|
|
|
226 ;; powerful enough to handle these two cases in one regexp.
|
|
|
227 ;; prove me wrong!
|
|
|
228 (cons (concat "^\\(" kwregex "\\)[ \n\t(]") 1)
|
|
|
229 ;; classes
|
|
|
230 '("\\bclass[ \t]+\\([a-zA-Z_]+[a-zA-Z0-9_]*\\)"
|
|
|
231 1 font-lock-type-face)
|
|
|
232 ;; functions
|
|
|
233 '("\\bdef[ \t]+\\([a-zA-Z_]+[a-zA-Z0-9_]*\\)"
|
|
|
234 1 font-lock-function-name-face)
|
|
|
235 ))
|
|
|
236 "Additional expressions to highlight in Python mode.")
|
|
102
|
237 (put 'python-mode 'font-lock-defaults '(python-font-lock-keywords))
|
|
|
238
|
|
2
|
239
|
|
|
240 (defvar imenu-example--python-show-method-args-p nil
|
|
|
241 "*Controls echoing of arguments of functions & methods in the imenu buffer.
|
|
|
242 When non-nil, arguments are printed.")
|
|
|
243
|
|
|
244
|
|
|
245
|
|
|
246 ;; ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
|
|
|
247 ;; NO USER DEFINABLE VARIABLES BEYOND THIS POINT
|
|
|
248
|
|
|
249 (make-variable-buffer-local 'py-indent-offset)
|
|
|
250
|
|
|
251 ;; Differentiate between Emacs 18, Lucid Emacs, and Emacs 19. This
|
|
|
252 ;; seems to be the standard way of checking this.
|
|
|
253 ;; BAW - This is *not* the right solution. When at all possible,
|
|
|
254 ;; instead of testing for the version of Emacs, use feature tests.
|
|
|
255
|
|
|
256 (setq py-this-is-lucid-emacs-p (string-match "Lucid\\|XEmacs" emacs-version))
|
|
|
257 (setq py-this-is-emacs-19-p
|
|
|
258 (and
|
|
|
259 (not py-this-is-lucid-emacs-p)
|
|
|
260 (string-match "^19\\." emacs-version)))
|
|
|
261
|
|
|
262 ;; have to bind py-file-queue before installing the kill-emacs hook
|
|
|
263 (defvar py-file-queue nil
|
|
|
264 "Queue of Python temp files awaiting execution.
|
|
|
265 Currently-active file is at the head of the list.")
|
|
|
266
|
|
|
267 ;; define a mode-specific abbrev table for those who use such things
|
|
|
268 (defvar python-mode-abbrev-table nil
|
|
|
269 "Abbrev table in use in `python-mode' buffers.")
|
|
|
270 (define-abbrev-table 'python-mode-abbrev-table nil)
|
|
|
271
|
|
|
272 (defvar python-mode-hook nil
|
|
|
273 "*Hook called by `python-mode'.")
|
|
|
274
|
|
|
275 ;; in previous version of python-mode.el, the hook was incorrectly
|
|
|
276 ;; called py-mode-hook, and was not defvar'd. deprecate its use.
|
|
|
277 (and (fboundp 'make-obsolete-variable)
|
|
|
278 (make-obsolete-variable 'py-mode-hook 'python-mode-hook))
|
|
|
279
|
|
98
|
280 (defvar py-delete-function 'backward-delete-char-untabify
|
|
|
281 "*Function called by `py-delete-char' when deleting characters.")
|
|
|
282
|
|
2
|
283 (defvar py-mode-map ()
|
|
|
284 "Keymap used in `python-mode' buffers.")
|
|
|
285
|
|
|
286 (if py-mode-map
|
|
|
287 ()
|
|
|
288 (setq py-mode-map (make-sparse-keymap))
|
|
|
289
|
|
|
290 ;; shadow global bindings for newline-and-indent w/ the py- version.
|
|
|
291 ;; BAW - this is extremely bad form, but I'm not going to change it
|
|
|
292 ;; for now.
|
|
|
293 (mapcar (function (lambda (key)
|
|
|
294 (define-key
|
|
|
295 py-mode-map key 'py-newline-and-indent)))
|
|
|
296 (where-is-internal 'newline-and-indent))
|
|
|
297
|
|
|
298 ;; BAW - you could do it this way, but its not considered proper
|
|
|
299 ;; major-mode form.
|
|
|
300 (mapcar (function
|
|
|
301 (lambda (x)
|
|
|
302 (define-key py-mode-map (car x) (cdr x))))
|
|
|
303 '((":" . py-electric-colon)
|
|
|
304 ("\C-c\C-c" . py-execute-buffer)
|
|
|
305 ("\C-c|" . py-execute-region)
|
|
|
306 ("\C-c!" . py-shell)
|
|
153
|
307 ;; GDF - Don't rebind the delete key
|
|
|
308 ;; ("\177" . py-delete-char)
|
|
2
|
309 ("\n" . py-newline-and-indent)
|
|
|
310 ("\C-c:" . py-guess-indent-offset)
|
|
|
311 ("\C-c\t" . py-indent-region)
|
|
|
312 ("\C-c\C-l" . py-shift-region-left)
|
|
|
313 ("\C-c\C-r" . py-shift-region-right)
|
|
|
314 ("\C-c<" . py-shift-region-left)
|
|
|
315 ("\C-c>" . py-shift-region-right)
|
|
|
316 ("\C-c\C-n" . py-next-statement)
|
|
|
317 ("\C-c\C-p" . py-previous-statement)
|
|
|
318 ("\C-c\C-u" . py-goto-block-up)
|
|
|
319 ("\C-c\C-m" . py-mark-block)
|
|
|
320 ("\C-c#" . py-comment-region)
|
|
|
321 ("\C-c?" . py-describe-mode)
|
|
|
322 ("\C-c\C-hm" . py-describe-mode)
|
|
|
323 ("\e\C-a" . beginning-of-python-def-or-class)
|
|
|
324 ("\e\C-e" . end-of-python-def-or-class)
|
|
|
325 ( "\e\C-h" . mark-python-def-or-class)))
|
|
|
326 ;; should do all keybindings this way
|
|
|
327 (define-key py-mode-map "\C-c\C-b" 'py-submit-bug-report)
|
|
|
328 (define-key py-mode-map "\C-c\C-v" 'py-version)
|
|
|
329 )
|
|
|
330
|
|
|
331 (defvar py-mode-syntax-table nil
|
|
|
332 "Syntax table used in `python-mode' buffers.")
|
|
|
333
|
|
|
334 (if py-mode-syntax-table
|
|
|
335 ()
|
|
|
336 (setq py-mode-syntax-table (make-syntax-table))
|
|
|
337 ;; BAW - again, blech.
|
|
|
338 (mapcar (function
|
|
|
339 (lambda (x) (modify-syntax-entry
|
|
|
340 (car x) (cdr x) py-mode-syntax-table)))
|
|
|
341 '(( ?\( . "()" ) ( ?\) . ")(" )
|
|
|
342 ( ?\[ . "(]" ) ( ?\] . ")[" )
|
|
|
343 ( ?\{ . "(}" ) ( ?\} . "){" )
|
|
|
344 ;; fix operator symbols misassigned in the std table
|
|
|
345 ( ?\$ . "." ) ( ?\% . "." ) ( ?\& . "." )
|
|
|
346 ( ?\* . "." ) ( ?\+ . "." ) ( ?\- . "." )
|
|
|
347 ( ?\/ . "." ) ( ?\< . "." ) ( ?\= . "." )
|
|
|
348 ( ?\> . "." ) ( ?\| . "." )
|
|
|
349 ;; for historical reasons, underscore is word class
|
|
|
350 ;; instead of symbol class. it should be symbol class,
|
|
|
351 ;; but if you're tempted to change it, try binding M-f and
|
|
|
352 ;; M-b to py-forward-into-nomenclature and
|
|
|
353 ;; py-backward-into-nomenclature instead. -baw
|
|
|
354 ( ?\_ . "w" ) ; underscore is legit in words
|
|
|
355 ( ?\' . "\"") ; single quote is string quote
|
|
|
356 ( ?\" . "\"" ) ; double quote is string quote too
|
|
|
357 ( ?\` . "$") ; backquote is open and close paren
|
|
|
358 ( ?\# . "<") ; hash starts comment
|
|
|
359 ( ?\n . ">")))) ; newline ends comment
|
|
|
360
|
|
|
361 (defconst py-stringlit-re
|
|
|
362 (concat
|
|
|
363 "'\\([^'\n\\]\\|\\\\.\\)*'" ; single-quoted
|
|
|
364 "\\|" ; or
|
|
|
365 "\"\\([^\"\n\\]\\|\\\\.\\)*\"") ; double-quoted
|
|
|
366 "Regexp matching a Python string literal.")
|
|
|
367
|
|
|
368 ;; this is tricky because a trailing backslash does not mean
|
|
|
369 ;; continuation if it's in a comment
|
|
|
370 (defconst py-continued-re
|
|
|
371 (concat
|
|
|
372 "\\(" "[^#'\"\n\\]" "\\|" py-stringlit-re "\\)*"
|
|
|
373 "\\\\$")
|
|
|
374 "Regexp matching Python lines that are continued via backslash.")
|
|
|
375
|
|
|
376 (defconst py-blank-or-comment-re "[ \t]*\\($\\|#\\)"
|
|
|
377 "Regexp matching blank or comment lines.")
|
|
|
378
|
|
|
379 (defconst py-outdent-re
|
|
|
380 (concat "\\(" (mapconcat 'identity
|
|
|
381 '("else:"
|
|
|
382 "except\\(\\s +.*\\)?:"
|
|
|
383 "finally:"
|
|
|
384 "elif\\s +.*:")
|
|
|
385 "\\|")
|
|
|
386 "\\)")
|
|
|
387 "Regexp matching clauses to be outdented one level.")
|
|
|
388
|
|
|
389 (defconst py-no-outdent-re
|
|
|
390 (concat "\\(" (mapconcat 'identity
|
|
|
391 '("try:"
|
|
|
392 "except\\(\\s +.*\\)?:"
|
|
|
393 "while\\s +.*:"
|
|
|
394 "for\\s +.*:"
|
|
|
395 "if\\s +.*:"
|
|
4
|
396 "elif\\s +.*:"
|
|
|
397 "\\(return\\|break\\|raise\\|continue\\)[ \t\n]"
|
|
|
398 )
|
|
2
|
399 "\\|")
|
|
|
400 "\\)")
|
|
|
401 "Regexp matching lines to not outdent after.")
|
|
|
402
|
|
4
|
403 (defvar py-defun-start-re
|
|
|
404 "^\\([ \t]*\\)def[ \t]+\\([a-zA-Z_0-9]+\\)\\|\\(^[a-zA-Z_0-9]+\\)[ \t]*="
|
|
|
405 "Regexp matching a function, method or variable assignment.
|
|
|
406
|
|
|
407 If you change this, you probably have to change `py-current-defun' as well.
|
|
|
408 This is only used by `py-current-defun' to find the name for add-log.el.")
|
|
|
409
|
|
|
410 (defvar py-class-start-re "^class[ \t]*\\([a-zA-Z_0-9]+\\)"
|
|
|
411 "Regexp for finding a class name.
|
|
|
412
|
|
|
413 If you change this, you probably have to change `py-current-defun' as well.
|
|
|
414 This is only used by `py-current-defun' to find the name for add-log.el.")
|
|
|
415
|
|
98
|
416 ;; As of 30-Jan-1997, Emacs 19.34 works but XEmacs 19.15b90 and
|
|
|
417 ;; previous does not. It is suspected that Emacsen before 19.34 are
|
|
|
418 ;; also broken.
|
|
|
419 (defvar py-parse-partial-sexp-works-p
|
|
|
420 (let ((buf (get-buffer-create " ---*---pps---*---"))
|
|
|
421 state status)
|
|
|
422 (save-excursion
|
|
|
423 (set-buffer buf)
|
|
|
424 (erase-buffer)
|
|
|
425 (insert "(line1\n line2)\nline3")
|
|
|
426 (lisp-mode)
|
|
|
427 (goto-char (point-min))
|
|
|
428 (setq state (parse-partial-sexp (point) (save-excursion
|
|
|
429 (forward-line 1)
|
|
|
430 (point))))
|
|
|
431 (parse-partial-sexp (point) (point-max) 0 nil state)
|
|
|
432 (setq status (not (= (point) (point-max))))
|
|
|
433 (kill-buffer buf)
|
|
|
434 status))
|
|
|
435 "Does `parse-partial-sexp' work in this Emacs?")
|
|
4
|
436
|
|
2
|
437
|
|
|
438 ;; Menu definitions, only relevent if you have the easymenu.el package
|
|
|
439 ;; (standard in the latest Emacs 19 and XEmacs 19 distributions).
|
|
4
|
440 (defvar py-menu nil
|
|
|
441 "Menu for Python Mode.
|
|
|
442
|
|
|
443 This menu will get created automatically if you have the easymenu
|
|
|
444 package. Note that the latest XEmacs 19 and Emacs 19 versions contain
|
|
|
445 this package.")
|
|
|
446
|
|
2
|
447 (if (condition-case nil
|
|
|
448 (require 'easymenu)
|
|
|
449 (error nil))
|
|
|
450 (easy-menu-define
|
|
|
451 py-menu py-mode-map "Python Mode menu"
|
|
|
452 '("Python"
|
|
98
|
453 ["Comment Out Region" py-comment-region (mark)]
|
|
|
454 ["Uncomment Region" (py-comment-region (point) (mark) '(4)) (mark)]
|
|
2
|
455 "-"
|
|
|
456 ["Mark current block" py-mark-block t]
|
|
|
457 ["Mark current def" mark-python-def-or-class t]
|
|
|
458 ["Mark current class" (mark-python-def-or-class t) t]
|
|
|
459 "-"
|
|
|
460 ["Shift region left" py-shift-region-left (mark)]
|
|
|
461 ["Shift region right" py-shift-region-right (mark)]
|
|
|
462 "-"
|
|
|
463 ["Execute buffer" py-execute-buffer t]
|
|
|
464 ["Execute region" py-execute-region (mark)]
|
|
|
465 ["Start interpreter..." py-shell t]
|
|
|
466 "-"
|
|
|
467 ["Go to start of block" py-goto-block-up t]
|
|
|
468 ["Go to start of class" (beginning-of-python-def-or-class t) t]
|
|
|
469 ["Move to end of class" (end-of-python-def-or-class t) t]
|
|
|
470 ["Move to start of def" beginning-of-python-def-or-class t]
|
|
|
471 ["Move to end of def" end-of-python-def-or-class t]
|
|
|
472 "-"
|
|
|
473 ["Describe mode" py-describe-mode t]
|
|
|
474 )))
|
|
|
475
|
|
|
476
|
|
|
477
|
|
|
478 ;; imenu definitions, courtesy of Perry A. Stoll <stoll@atr-sw.atr.co.jp>
|
|
|
479 (defvar imenu-example--python-class-regexp
|
|
|
480 (concat ; <<classes>>
|
|
|
481 "\\(" ;
|
|
|
482 "^[ \t]*" ; newline and maybe whitespace
|
|
|
483 "\\(class[ \t]+[a-zA-Z0-9_]+\\)" ; class name
|
|
|
484 ; possibly multiple superclasses
|
|
|
485 "\\([ \t]*\\((\\([a-zA-Z0-9_, \t\n]\\)*)\\)?\\)"
|
|
|
486 "[ \t]*:" ; and the final :
|
|
|
487 "\\)" ; >>classes<<
|
|
|
488 )
|
|
|
489 "Regexp for Python classes for use with the imenu package."
|
|
|
490 )
|
|
|
491
|
|
|
492 (defvar imenu-example--python-method-regexp
|
|
|
493 (concat ; <<methods and functions>>
|
|
|
494 "\\(" ;
|
|
|
495 "^[ \t]*" ; new line and maybe whitespace
|
|
|
496 "\\(def[ \t]+" ; function definitions start with def
|
|
|
497 "\\([a-zA-Z0-9_]+\\)" ; name is here
|
|
|
498 ; function arguments...
|
|
|
499 "[ \t]*(\\([a-zA-Z0-9_=,\* \t\n]*\\))"
|
|
|
500 "\\)" ; end of def
|
|
|
501 "[ \t]*:" ; and then the :
|
|
|
502 "\\)" ; >>methods and functions<<
|
|
|
503 )
|
|
|
504 "Regexp for Python methods/functions for use with the imenu package."
|
|
|
505 )
|
|
|
506
|
|
|
507 (defvar imenu-example--python-method-no-arg-parens '(2 8)
|
|
|
508 "Indicies into groups of the Python regexp for use with imenu.
|
|
|
509
|
|
|
510 Using these values will result in smaller imenu lists, as arguments to
|
|
|
511 functions are not listed.
|
|
|
512
|
|
|
513 See the variable `imenu-example--python-show-method-args-p' for more
|
|
|
514 information.")
|
|
|
515
|
|
|
516 (defvar imenu-example--python-method-arg-parens '(2 7)
|
|
|
517 "Indicies into groups of the Python regexp for use with imenu.
|
|
|
518 Using these values will result in large imenu lists, as arguments to
|
|
|
519 functions are listed.
|
|
|
520
|
|
|
521 See the variable `imenu-example--python-show-method-args-p' for more
|
|
|
522 information.")
|
|
|
523
|
|
|
524 ;; Note that in this format, this variable can still be used with the
|
|
|
525 ;; imenu--generic-function. Otherwise, there is no real reason to have
|
|
|
526 ;; it.
|
|
|
527 (defvar imenu-example--generic-python-expression
|
|
|
528 (cons
|
|
|
529 (concat
|
|
|
530 imenu-example--python-class-regexp
|
|
|
531 "\\|" ; or...
|
|
|
532 imenu-example--python-method-regexp
|
|
|
533 )
|
|
|
534 imenu-example--python-method-no-arg-parens)
|
|
|
535 "Generic Python expression which may be used directly with imenu.
|
|
|
536 Used by setting the variable `imenu-generic-expression' to this value.
|
|
|
537 Also, see the function \\[imenu-example--create-python-index] for a
|
|
|
538 better alternative for finding the index.")
|
|
|
539
|
|
|
540 ;; These next two variables are used when searching for the python
|
|
|
541 ;; class/definitions. Just saving some time in accessing the
|
|
|
542 ;; generic-python-expression, really.
|
|
4
|
543 (defvar imenu-example--python-generic-regexp nil)
|
|
|
544 (defvar imenu-example--python-generic-parens nil)
|
|
2
|
545
|
|
|
546
|
|
|
547 ;;;###autoload
|
|
|
548 (eval-when-compile
|
|
|
549 ;; Imenu isn't used in XEmacs, so just ignore load errors
|
|
|
550 (condition-case ()
|
|
|
551 (progn
|
|
|
552 (require 'cl)
|
|
|
553 (require 'imenu))
|
|
|
554 (error nil)))
|
|
|
555
|
|
|
556 (defun imenu-example--create-python-index ()
|
|
|
557 "Python interface function for imenu package.
|
|
|
558 Finds all python classes and functions/methods. Calls function
|
|
|
559 \\[imenu-example--create-python-index-engine]. See that function for
|
|
|
560 the details of how this works."
|
|
|
561 (setq imenu-example--python-generic-regexp
|
|
|
562 (car imenu-example--generic-python-expression))
|
|
|
563 (setq imenu-example--python-generic-parens
|
|
|
564 (if imenu-example--python-show-method-args-p
|
|
|
565 imenu-example--python-method-arg-parens
|
|
|
566 imenu-example--python-method-no-arg-parens))
|
|
|
567 (goto-char (point-min))
|
|
|
568 (imenu-example--create-python-index-engine nil))
|
|
|
569
|
|
|
570 (defun imenu-example--create-python-index-engine (&optional start-indent)
|
|
|
571 "Function for finding imenu definitions in Python.
|
|
|
572
|
|
|
573 Finds all definitions (classes, methods, or functions) in a Python
|
|
|
574 file for the imenu package.
|
|
|
575
|
|
|
576 Returns a possibly nested alist of the form
|
|
|
577
|
|
|
578 (INDEX-NAME . INDEX-POSITION)
|
|
|
579
|
|
|
580 The second element of the alist may be an alist, producing a nested
|
|
|
581 list as in
|
|
|
582
|
|
|
583 (INDEX-NAME . INDEX-ALIST)
|
|
|
584
|
|
|
585 This function should not be called directly, as it calls itself
|
|
|
586 recursively and requires some setup. Rather this is the engine for
|
|
|
587 the function \\[imenu-example--create-python-index].
|
|
|
588
|
|
|
589 It works recursively by looking for all definitions at the current
|
|
|
590 indention level. When it finds one, it adds it to the alist. If it
|
|
|
591 finds a definition at a greater indentation level, it removes the
|
|
|
592 previous definition from the alist. In it's place it adds all
|
|
|
593 definitions found at the next indentation level. When it finds a
|
|
|
594 definition that is less indented then the current level, it retuns the
|
|
|
595 alist it has created thus far.
|
|
|
596
|
|
|
597 The optional argument START-INDENT indicates the starting indentation
|
|
|
598 at which to continue looking for Python classes, methods, or
|
|
|
599 functions. If this is not supplied, the function uses the indentation
|
|
|
600 of the first definition found."
|
|
|
601 (let ((index-alist '())
|
|
|
602 (sub-method-alist '())
|
|
|
603 looking-p
|
|
|
604 def-name prev-name
|
|
|
605 cur-indent def-pos
|
|
|
606 (class-paren (first imenu-example--python-generic-parens))
|
|
|
607 (def-paren (second imenu-example--python-generic-parens)))
|
|
|
608 (setq looking-p
|
|
|
609 (re-search-forward imenu-example--python-generic-regexp
|
|
|
610 (point-max) t))
|
|
|
611 (while looking-p
|
|
|
612 (save-excursion
|
|
|
613 ;; used to set def-name to this value but generic-extract-name is
|
|
|
614 ;; new to imenu-1.14. this way it still works with imenu-1.11
|
|
|
615 ;;(imenu--generic-extract-name imenu-example--python-generic-parens))
|
|
|
616 (let ((cur-paren (if (match-beginning class-paren)
|
|
|
617 class-paren def-paren)))
|
|
|
618 (setq def-name
|
|
|
619 (buffer-substring (match-beginning cur-paren)
|
|
|
620 (match-end cur-paren))))
|
|
|
621 (beginning-of-line)
|
|
|
622 (setq cur-indent (current-indentation)))
|
|
|
623
|
|
|
624 ;; HACK: want to go to the next correct definition location. we
|
|
|
625 ;; explicitly list them here. would be better to have them in a
|
|
|
626 ;; list.
|
|
|
627 (setq def-pos
|
|
|
628 (or (match-beginning class-paren)
|
|
|
629 (match-beginning def-paren)))
|
|
|
630
|
|
|
631 ;; if we don't have a starting indent level, take this one
|
|
|
632 (or start-indent
|
|
|
633 (setq start-indent cur-indent))
|
|
|
634
|
|
|
635 ;; if we don't have class name yet, take this one
|
|
|
636 (or prev-name
|
|
|
637 (setq prev-name def-name))
|
|
|
638
|
|
|
639 ;; what level is the next definition on? must be same, deeper
|
|
|
640 ;; or shallower indentation
|
|
|
641 (cond
|
|
|
642 ;; at the same indent level, add it to the list...
|
|
|
643 ((= start-indent cur-indent)
|
|
|
644
|
|
|
645 ;; if we don't have push, use the following...
|
|
|
646 ;;(setf index-alist (cons (cons def-name def-pos) index-alist))
|
|
|
647 (push (cons def-name def-pos) index-alist))
|
|
|
648
|
|
|
649 ;; deeper indented expression, recur...
|
|
|
650 ((< start-indent cur-indent)
|
|
|
651
|
|
|
652 ;; the point is currently on the expression we're supposed to
|
|
|
653 ;; start on, so go back to the last expression. The recursive
|
|
|
654 ;; call will find this place again and add it to the correct
|
|
|
655 ;; list
|
|
|
656 (re-search-backward imenu-example--python-generic-regexp
|
|
|
657 (point-min) 'move)
|
|
|
658 (setq sub-method-alist (imenu-example--create-python-index-engine
|
|
|
659 cur-indent))
|
|
|
660
|
|
|
661 (if sub-method-alist
|
|
|
662 ;; we put the last element on the index-alist on the start
|
|
|
663 ;; of the submethod alist so the user can still get to it.
|
|
|
664 (let ((save-elmt (pop index-alist)))
|
|
|
665 (push (cons (imenu-create-submenu-name prev-name)
|
|
|
666 (cons save-elmt sub-method-alist))
|
|
|
667 index-alist))))
|
|
|
668
|
|
|
669 ;; found less indented expression, we're done.
|
|
|
670 (t
|
|
|
671 (setq looking-p nil)
|
|
|
672 (re-search-backward imenu-example--python-generic-regexp
|
|
|
673 (point-min) t)))
|
|
|
674 (setq prev-name def-name)
|
|
|
675 (and looking-p
|
|
|
676 (setq looking-p
|
|
|
677 (re-search-forward imenu-example--python-generic-regexp
|
|
|
678 (point-max) 'move))))
|
|
|
679 (nreverse index-alist)))
|
|
|
680
|
|
|
681
|
|
|
682 ;;;###autoload
|
|
|
683 (defun python-mode ()
|
|
|
684 "Major mode for editing Python files.
|
|
|
685 To submit a problem report, enter `\\[py-submit-bug-report]' from a
|
|
|
686 `python-mode' buffer. Do `\\[py-describe-mode]' for detailed
|
|
|
687 documentation. To see what version of `python-mode' you are running,
|
|
|
688 enter `\\[py-version]'.
|
|
|
689
|
|
|
690 This mode knows about Python indentation, tokens, comments and
|
|
|
691 continuation lines. Paragraphs are separated by blank lines only.
|
|
|
692
|
|
|
693 COMMANDS
|
|
|
694 \\{py-mode-map}
|
|
|
695 VARIABLES
|
|
|
696
|
|
|
697 py-indent-offset\t\tindentation increment
|
|
|
698 py-block-comment-prefix\t\tcomment string used by comment-region
|
|
|
699 py-python-command\t\tshell command to invoke Python interpreter
|
|
|
700 py-scroll-process-buffer\t\talways scroll Python process buffer
|
|
|
701 py-temp-directory\t\tdirectory used for temp files (if needed)
|
|
|
702 py-beep-if-tab-change\t\tring the bell if tab-width is changed"
|
|
|
703 (interactive)
|
|
4
|
704 ;; set up local variables
|
|
2
|
705 (kill-all-local-variables)
|
|
4
|
706 (make-local-variable 'font-lock-defaults)
|
|
|
707 (make-local-variable 'paragraph-separate)
|
|
|
708 (make-local-variable 'paragraph-start)
|
|
|
709 (make-local-variable 'require-final-newline)
|
|
|
710 (make-local-variable 'comment-start)
|
|
98
|
711 (make-local-variable 'comment-end)
|
|
4
|
712 (make-local-variable 'comment-start-skip)
|
|
|
713 (make-local-variable 'comment-column)
|
|
|
714 (make-local-variable 'indent-region-function)
|
|
|
715 (make-local-variable 'indent-line-function)
|
|
|
716 (make-local-variable 'add-log-current-defun-function)
|
|
|
717 ;;
|
|
2
|
718 (set-syntax-table py-mode-syntax-table)
|
|
4
|
719 (setq major-mode 'python-mode
|
|
|
720 mode-name "Python"
|
|
|
721 local-abbrev-table python-mode-abbrev-table
|
|
|
722 paragraph-separate "^[ \t]*$"
|
|
|
723 paragraph-start "^[ \t]*$"
|
|
|
724 require-final-newline t
|
|
|
725 comment-start "# "
|
|
98
|
726 comment-end ""
|
|
4
|
727 comment-start-skip "# *"
|
|
|
728 comment-column 40
|
|
|
729 indent-region-function 'py-indent-region
|
|
|
730 indent-line-function 'py-indent-line
|
|
|
731 ;; tell add-log.el how to find the current function/method/variable
|
|
|
732 add-log-current-defun-function 'py-current-defun
|
|
|
733 )
|
|
2
|
734 (use-local-map py-mode-map)
|
|
|
735 ;; add the menu
|
|
|
736 (if py-menu
|
|
|
737 (easy-menu-add py-menu))
|
|
|
738 ;; Emacs 19 requires this
|
|
|
739 (if (or py-this-is-lucid-emacs-p py-this-is-emacs-19-p)
|
|
|
740 (setq comment-multi-line nil))
|
|
|
741 ;; hack to allow overriding the tabsize in the file (see tokenizer.c)
|
|
|
742 ;;
|
|
|
743 ;; not sure where the magic comment has to be; to save time
|
|
|
744 ;; searching for a rarity, we give up if it's not found prior to the
|
|
|
745 ;; first executable statement.
|
|
|
746 ;;
|
|
|
747 ;; BAW - on first glance, this seems like complete hackery. Why was
|
|
|
748 ;; this necessary, and is it still necessary?
|
|
|
749 (let ((case-fold-search nil)
|
|
|
750 (start (point))
|
|
|
751 new-tab-width)
|
|
|
752 (if (re-search-forward
|
|
|
753 "^[ \t]*#[ \t]*vi:set[ \t]+tabsize=\\([0-9]+\\):"
|
|
|
754 (prog2 (py-next-statement 1) (point) (goto-char 1))
|
|
|
755 t)
|
|
|
756 (progn
|
|
|
757 (setq new-tab-width
|
|
|
758 (string-to-int
|
|
|
759 (buffer-substring (match-beginning 1) (match-end 1))))
|
|
|
760 (if (= tab-width new-tab-width)
|
|
|
761 nil
|
|
|
762 (setq tab-width new-tab-width)
|
|
|
763 (message "Caution: tab-width changed to %d" new-tab-width)
|
|
|
764 (if py-beep-if-tab-change (beep)))))
|
|
|
765 (goto-char start))
|
|
|
766
|
|
|
767 ;; install imenu
|
|
|
768 (setq imenu-create-index-function
|
|
|
769 (function imenu-example--create-python-index))
|
|
|
770 (if (fboundp 'imenu-add-to-menubar)
|
|
|
771 (imenu-add-to-menubar (format "%s-%s" "IM" mode-name)))
|
|
|
772
|
|
|
773 ;; run the mode hook. py-mode-hook use is deprecated
|
|
|
774 (if python-mode-hook
|
|
|
775 (run-hooks 'python-mode-hook)
|
|
|
776 (run-hooks 'py-mode-hook)))
|
|
|
777
|
|
|
778
|
|
|
779 (defun py-keep-region-active ()
|
|
|
780 ;; do whatever is necessary to keep the region active in XEmacs.
|
|
|
781 ;; Ignore byte-compiler warnings you might see. Also note that
|
|
|
782 ;; FSF's Emacs 19 does it differently and doesn't its policy doesn't
|
|
|
783 ;; require us to take explicit action.
|
|
|
784 (and (boundp 'zmacs-region-stays)
|
|
|
785 (setq zmacs-region-stays t)))
|
|
|
786
|
|
|
787
|
|
|
788 ;; electric characters
|
|
|
789 (defun py-outdent-p ()
|
|
|
790 ;; returns non-nil if the current line should outdent one level
|
|
|
791 (save-excursion
|
|
|
792 (and (progn (back-to-indentation)
|
|
|
793 (looking-at py-outdent-re))
|
|
|
794 (progn (backward-to-indentation 1)
|
|
|
795 (while (or (looking-at py-blank-or-comment-re)
|
|
|
796 (bobp))
|
|
|
797 (backward-to-indentation 1))
|
|
|
798 (not (looking-at py-no-outdent-re)))
|
|
|
799 )))
|
|
|
800
|
|
|
801
|
|
|
802 (defun py-electric-colon (arg)
|
|
|
803 "Insert a colon.
|
|
|
804 In certain cases the line is outdented appropriately. If a numeric
|
|
|
805 argument is provided, that many colons are inserted non-electrically.
|
|
|
806 Electric behavior is inhibited inside a string or comment."
|
|
|
807 (interactive "P")
|
|
|
808 (self-insert-command (prefix-numeric-value arg))
|
|
|
809 ;; are we in a string or comment?
|
|
|
810 (if (save-excursion
|
|
|
811 (let ((pps (parse-partial-sexp (save-excursion
|
|
|
812 (beginning-of-python-def-or-class)
|
|
|
813 (point))
|
|
|
814 (point))))
|
|
|
815 (not (or (nth 3 pps) (nth 4 pps)))))
|
|
|
816 (save-excursion
|
|
|
817 (let ((here (point))
|
|
|
818 (outdent 0)
|
|
4
|
819 (indent (py-compute-indentation t)))
|
|
2
|
820 (if (and (not arg)
|
|
|
821 (py-outdent-p)
|
|
|
822 (= indent (save-excursion
|
|
4
|
823 (py-next-statement -1)
|
|
|
824 (py-compute-indentation t)))
|
|
2
|
825 )
|
|
|
826 (setq outdent py-indent-offset))
|
|
|
827 ;; Don't indent, only outdent. This assumes that any lines that
|
|
|
828 ;; are already outdented relative to py-compute-indentation were
|
|
|
829 ;; put there on purpose. Its highly annoying to have `:' indent
|
|
|
830 ;; for you. Use TAB, C-c C-l or C-c C-r to adjust. TBD: Is
|
|
|
831 ;; there a better way to determine this???
|
|
|
832 (if (< (current-indentation) indent) nil
|
|
|
833 (goto-char here)
|
|
|
834 (beginning-of-line)
|
|
|
835 (delete-horizontal-space)
|
|
|
836 (indent-to (- indent outdent))
|
|
|
837 )))))
|
|
|
838
|
|
|
839
|
|
|
840 ;;; Functions that execute Python commands in a subprocess
|
|
4
|
841 ;;;###autoload
|
|
2
|
842 (defun py-shell ()
|
|
|
843 "Start an interactive Python interpreter in another window.
|
|
|
844 This is like Shell mode, except that Python is running in the window
|
|
|
845 instead of a shell. See the `Interactive Shell' and `Shell Mode'
|
|
|
846 sections of the Emacs manual for details, especially for the key
|
|
|
847 bindings active in the `*Python*' buffer.
|
|
|
848
|
|
|
849 See the docs for variable `py-scroll-buffer' for info on scrolling
|
|
|
850 behavior in the process window.
|
|
|
851
|
|
|
852 Warning: Don't use an interactive Python if you change sys.ps1 or
|
|
|
853 sys.ps2 from their default values, or if you're running code that
|
|
|
854 prints `>>> ' or `... ' at the start of a line. `python-mode' can't
|
|
|
855 distinguish your output from Python's output, and assumes that `>>> '
|
|
|
856 at the start of a line is a prompt from Python. Similarly, the Emacs
|
|
|
857 Shell mode code assumes that both `>>> ' and `... ' at the start of a
|
|
|
858 line are Python prompts. Bad things can happen if you fool either
|
|
|
859 mode.
|
|
|
860
|
|
|
861 Warning: If you do any editing *in* the process buffer *while* the
|
|
|
862 buffer is accepting output from Python, do NOT attempt to `undo' the
|
|
|
863 changes. Some of the output (nowhere near the parts you changed!) may
|
|
|
864 be lost if you do. This appears to be an Emacs bug, an unfortunate
|
|
|
865 interaction between undo and process filters; the same problem exists in
|
|
|
866 non-Python process buffers using the default (Emacs-supplied) process
|
|
|
867 filter."
|
|
|
868 ;; BAW - should undo be disabled in the python process buffer, if
|
|
|
869 ;; this bug still exists?
|
|
|
870 (interactive)
|
|
|
871 (if py-this-is-emacs-19-p
|
|
|
872 (progn
|
|
|
873 (require 'comint)
|
|
|
874 (switch-to-buffer-other-window
|
|
|
875 (make-comint "Python" py-python-command)))
|
|
|
876 (progn
|
|
|
877 (require 'shell)
|
|
|
878 (switch-to-buffer-other-window
|
|
|
879 (apply (if (fboundp 'make-shell) 'make-shell 'make-comint)
|
|
|
880 "Python" py-python-command nil))))
|
|
|
881 (make-local-variable 'shell-prompt-pattern)
|
|
|
882 (setq shell-prompt-pattern "^>>> \\|^\\.\\.\\. ")
|
|
|
883 (set-process-filter (get-buffer-process (current-buffer))
|
|
|
884 'py-process-filter)
|
|
|
885 (set-syntax-table py-mode-syntax-table))
|
|
|
886
|
|
|
887 (defun py-execute-region (start end)
|
|
|
888 "Send the region between START and END to a Python interpreter.
|
|
|
889 If there is a *Python* process it is used.
|
|
|
890
|
|
|
891 Hint: If you want to execute part of a Python file several times
|
|
|
892 \(e.g., perhaps you're developing a function and want to flesh it out
|
|
|
893 a bit at a time), use `\\[narrow-to-region]' to restrict the buffer to
|
|
|
894 the region of interest, and send the code to a *Python* process via
|
|
|
895 `\\[py-execute-buffer]' instead.
|
|
|
896
|
|
|
897 Following are subtleties to note when using a *Python* process:
|
|
|
898
|
|
|
899 If a *Python* process is used, the region is copied into a temporary
|
|
|
900 file (in directory `py-temp-directory'), and an `execfile' command is
|
|
|
901 sent to Python naming that file. If you send regions faster than
|
|
|
902 Python can execute them, `python-mode' will save them into distinct
|
|
|
903 temp files, and execute the next one in the queue the next time it
|
|
|
904 sees a `>>> ' prompt from Python. Each time this happens, the process
|
|
|
905 buffer is popped into a window (if it's not already in some window) so
|
|
|
906 you can see it, and a comment of the form
|
|
|
907
|
|
|
908 \t## working on region in file <name> ...
|
|
|
909
|
|
|
910 is inserted at the end.
|
|
|
911
|
|
|
912 Caution: No more than 26 regions can be pending at any given time.
|
|
|
913 This limit is (indirectly) inherited from libc's mktemp(3).
|
|
|
914 `python-mode' does not try to protect you from exceeding the limit.
|
|
|
915 It's extremely unlikely that you'll get anywhere close to the limit in
|
|
|
916 practice, unless you're trying to be a jerk <grin>.
|
|
|
917
|
|
|
918 See the `\\[py-shell]' docs for additional warnings."
|
|
|
919 (interactive "r")
|
|
|
920 (or (< start end) (error "Region is empty"))
|
|
|
921 (let ((pyproc (get-process "Python"))
|
|
|
922 fname)
|
|
|
923 (if (null pyproc)
|
|
|
924 (shell-command-on-region start end py-python-command)
|
|
|
925 ;; else feed it thru a temp file
|
|
|
926 (setq fname (py-make-temp-name))
|
|
|
927 (write-region start end fname nil 'no-msg)
|
|
|
928 (setq py-file-queue (append py-file-queue (list fname)))
|
|
|
929 (if (cdr py-file-queue)
|
|
|
930 (message "File %s queued for execution" fname)
|
|
|
931 ;; else
|
|
|
932 (py-execute-file pyproc fname)))))
|
|
|
933
|
|
|
934 (defun py-execute-file (pyproc fname)
|
|
|
935 (py-append-to-process-buffer
|
|
|
936 pyproc
|
|
|
937 (format "## working on region in file %s ...\n" fname))
|
|
|
938 (process-send-string pyproc (format "execfile('%s')\n" fname)))
|
|
|
939
|
|
|
940 (defun py-process-filter (pyproc string)
|
|
|
941 (let ((curbuf (current-buffer))
|
|
|
942 (pbuf (process-buffer pyproc))
|
|
|
943 (pmark (process-mark pyproc))
|
|
|
944 file-finished)
|
|
|
945
|
|
|
946 ;; make sure we switch to a different buffer at least once. if we
|
|
|
947 ;; *don't* do this, then if the process buffer is in the selected
|
|
|
948 ;; window, and point is before the end, and lots of output is
|
|
|
949 ;; coming at a fast pace, then (a) simple cursor-movement commands
|
|
|
950 ;; like C-p, C-n, C-f, C-b, C-a, C-e take an incredibly long time
|
|
|
951 ;; to have a visible effect (the window just doesn't get updated,
|
|
|
952 ;; sometimes for minutes(!)), and (b) it takes about 5x longer to
|
|
|
953 ;; get all the process output (until the next python prompt).
|
|
|
954 ;;
|
|
|
955 ;; #b makes no sense to me at all. #a almost makes sense: unless
|
|
|
956 ;; we actually change buffers, set_buffer_internal in buffer.c
|
|
|
957 ;; doesn't set windows_or_buffers_changed to 1, & that in turn
|
|
|
958 ;; seems to make the Emacs command loop reluctant to update the
|
|
|
959 ;; display. Perhaps the default process filter in process.c's
|
|
|
960 ;; read_process_output has update_mode_lines++ for a similar
|
|
|
961 ;; reason? beats me ...
|
|
|
962
|
|
4
|
963 (unwind-protect
|
|
|
964 ;; make sure current buffer is restored
|
|
|
965 ;; BAW - we want to check to see if this still applies
|
|
|
966 (progn
|
|
|
967 ;; mysterious ugly hack
|
|
|
968 (if (eq curbuf pbuf)
|
|
|
969 (set-buffer (get-buffer-create "*scratch*")))
|
|
2
|
970
|
|
4
|
971 (set-buffer pbuf)
|
|
|
972 (let* ((start (point))
|
|
|
973 (goback (< start pmark))
|
|
|
974 (goend (and (not goback) (= start (point-max))))
|
|
|
975 (buffer-read-only nil))
|
|
|
976 (goto-char pmark)
|
|
|
977 (insert string)
|
|
|
978 (move-marker pmark (point))
|
|
|
979 (setq file-finished
|
|
|
980 (and py-file-queue
|
|
|
981 (equal ">>> "
|
|
|
982 (buffer-substring
|
|
|
983 (prog2 (beginning-of-line) (point)
|
|
|
984 (goto-char pmark))
|
|
|
985 (point)))))
|
|
|
986 (if goback (goto-char start)
|
|
|
987 ;; else
|
|
|
988 (if py-scroll-process-buffer
|
|
|
989 (let* ((pop-up-windows t)
|
|
|
990 (pwin (display-buffer pbuf)))
|
|
|
991 (set-window-point pwin (point)))))
|
|
|
992 (set-buffer curbuf)
|
|
|
993 (if file-finished
|
|
|
994 (progn
|
|
|
995 (py-delete-file-silently (car py-file-queue))
|
|
|
996 (setq py-file-queue (cdr py-file-queue))
|
|
|
997 (if py-file-queue
|
|
|
998 (py-execute-file pyproc (car py-file-queue)))))
|
|
|
999 (and goend
|
|
|
1000 (progn (set-buffer pbuf)
|
|
|
1001 (goto-char (point-max))))
|
|
|
1002 ))
|
|
|
1003 (set-buffer curbuf))))
|
|
2
|
1004
|
|
|
1005 (defun py-execute-buffer ()
|
|
|
1006 "Send the contents of the buffer to a Python interpreter.
|
|
|
1007 If there is a *Python* process buffer it is used. If a clipping
|
|
|
1008 restriction is in effect, only the accessible portion of the buffer is
|
|
|
1009 sent. A trailing newline will be supplied if needed.
|
|
|
1010
|
|
|
1011 See the `\\[py-execute-region]' docs for an account of some subtleties."
|
|
|
1012 (interactive)
|
|
|
1013 (py-execute-region (point-min) (point-max)))
|
|
|
1014
|
|
|
1015
|
|
|
1016
|
|
|
1017 ;; Functions for Python style indentation
|
|
|
1018 (defun py-delete-char (count)
|
|
|
1019 "Reduce indentation or delete character.
|
|
98
|
1020
|
|
2
|
1021 If point is at the leftmost column, deletes the preceding newline.
|
|
98
|
1022 Deletion is performed by calling the function in `py-delete-function'
|
|
|
1023 with a single argument (the number of characters to delete).
|
|
2
|
1024
|
|
|
1025 Else if point is at the leftmost non-blank character of a line that is
|
|
|
1026 neither a continuation line nor a non-indenting comment line, or if
|
|
|
1027 point is at the end of a blank line, reduces the indentation to match
|
|
|
1028 that of the line that opened the current block of code. The line that
|
|
|
1029 opened the block is displayed in the echo area to help you keep track
|
|
|
1030 of where you are. With numeric count, outdents that many blocks (but
|
|
|
1031 not past column zero).
|
|
|
1032
|
|
|
1033 Else the preceding character is deleted, converting a tab to spaces if
|
|
|
1034 needed so that only a single column position is deleted. Numeric
|
|
|
1035 argument delets that many characters."
|
|
|
1036 (interactive "*p")
|
|
|
1037 (if (or (/= (current-indentation) (current-column))
|
|
|
1038 (bolp)
|
|
|
1039 (py-continuation-line-p)
|
|
|
1040 (not py-honor-comment-indentation)
|
|
|
1041 (looking-at "#[^ \t\n]")) ; non-indenting #
|
|
98
|
1042 (funcall py-delete-function count)
|
|
2
|
1043 ;; else indent the same as the colon line that opened the block
|
|
|
1044
|
|
|
1045 ;; force non-blank so py-goto-block-up doesn't ignore it
|
|
|
1046 (insert-char ?* 1)
|
|
|
1047 (backward-char)
|
|
|
1048 (let ((base-indent 0) ; indentation of base line
|
|
|
1049 (base-text "") ; and text of base line
|
|
|
1050 (base-found-p nil))
|
|
|
1051 (save-excursion
|
|
|
1052 (while (< 0 count)
|
|
|
1053 (condition-case nil ; in case no enclosing block
|
|
|
1054 (progn
|
|
|
1055 (py-goto-block-up 'no-mark)
|
|
|
1056 (setq base-indent (current-indentation)
|
|
|
1057 base-text (py-suck-up-leading-text)
|
|
|
1058 base-found-p t))
|
|
|
1059 (error nil))
|
|
|
1060 (setq count (1- count))))
|
|
|
1061 (delete-char 1) ; toss the dummy character
|
|
|
1062 (delete-horizontal-space)
|
|
|
1063 (indent-to base-indent)
|
|
|
1064 (if base-found-p
|
|
|
1065 (message "Closes block: %s" base-text)))))
|
|
|
1066
|
|
|
1067 ;; required for pending-del and delsel modes
|
|
|
1068 (put 'py-delete-char 'delete-selection 'supersede)
|
|
|
1069 (put 'py-delete-char 'pending-delete 'supersede)
|
|
|
1070
|
|
4
|
1071 (defun py-indent-line (&optional arg)
|
|
|
1072 "Fix the indentation of the current line according to Python rules.
|
|
|
1073 With \\[universal-argument], ignore outdenting rules for block
|
|
|
1074 closing statements (e.g. return, raise, break, continue, pass)
|
|
|
1075
|
|
|
1076 This function is normally bound to `indent-line-function' so
|
|
|
1077 \\[indent-for-tab-command] will call it."
|
|
|
1078 (interactive "P")
|
|
2
|
1079 (let* ((ci (current-indentation))
|
|
|
1080 (move-to-indentation-p (<= (current-column) ci))
|
|
4
|
1081 (need (py-compute-indentation (not arg))))
|
|
2
|
1082 ;; see if we need to outdent
|
|
|
1083 (if (py-outdent-p)
|
|
|
1084 (setq need (- need py-indent-offset)))
|
|
|
1085 (if (/= ci need)
|
|
|
1086 (save-excursion
|
|
|
1087 (beginning-of-line)
|
|
|
1088 (delete-horizontal-space)
|
|
|
1089 (indent-to need)))
|
|
|
1090 (if move-to-indentation-p (back-to-indentation))))
|
|
|
1091
|
|
|
1092 (defun py-newline-and-indent ()
|
|
|
1093 "Strives to act like the Emacs `newline-and-indent'.
|
|
|
1094 This is just `strives to' because correct indentation can't be computed
|
|
|
1095 from scratch for Python code. In general, deletes the whitespace before
|
|
|
1096 point, inserts a newline, and takes an educated guess as to how you want
|
|
|
1097 the new line indented."
|
|
|
1098 (interactive)
|
|
|
1099 (let ((ci (current-indentation)))
|
|
|
1100 (if (< ci (current-column)) ; if point beyond indentation
|
|
|
1101 (newline-and-indent)
|
|
|
1102 ;; else try to act like newline-and-indent "normally" acts
|
|
|
1103 (beginning-of-line)
|
|
|
1104 (insert-char ?\n 1)
|
|
|
1105 (move-to-column ci))))
|
|
|
1106
|
|
4
|
1107 (defun py-compute-indentation (honor-block-close-p)
|
|
|
1108 ;; implements all the rules for indentation computation. when
|
|
|
1109 ;; honor-block-close-p is non-nil, statements such as return, raise,
|
|
|
1110 ;; break, continue, and pass force one level of outdenting.
|
|
2
|
1111 (save-excursion
|
|
|
1112 (let ((pps (parse-partial-sexp (save-excursion
|
|
|
1113 (beginning-of-python-def-or-class)
|
|
|
1114 (point))
|
|
|
1115 (point))))
|
|
|
1116 (beginning-of-line)
|
|
|
1117 (cond
|
|
|
1118 ;; are we inside a string or comment?
|
|
|
1119 ((or (nth 3 pps) (nth 4 pps))
|
|
|
1120 (save-excursion
|
|
|
1121 (if (not py-align-multiline-strings-p) 0
|
|
|
1122 ;; skip back over blank & non-indenting comment lines
|
|
|
1123 ;; note: will skip a blank or non-indenting comment line
|
|
|
1124 ;; that happens to be a continuation line too
|
|
|
1125 (re-search-backward "^[ \t]*\\([^ \t\n#]\\|#[ \t\n]\\)" nil 'move)
|
|
|
1126 (back-to-indentation)
|
|
|
1127 (current-column))))
|
|
|
1128 ;; are we on a continuation line?
|
|
|
1129 ((py-continuation-line-p)
|
|
|
1130 (let ((startpos (point))
|
|
|
1131 (open-bracket-pos (py-nesting-level))
|
|
|
1132 endpos searching found state)
|
|
|
1133 (if open-bracket-pos
|
|
|
1134 (progn
|
|
|
1135 ;; align with first item in list; else a normal
|
|
|
1136 ;; indent beyond the line with the open bracket
|
|
|
1137 (goto-char (1+ open-bracket-pos)) ; just beyond bracket
|
|
|
1138 ;; is the first list item on the same line?
|
|
|
1139 (skip-chars-forward " \t")
|
|
|
1140 (if (null (memq (following-char) '(?\n ?# ?\\)))
|
|
|
1141 ; yes, so line up with it
|
|
|
1142 (current-column)
|
|
|
1143 ;; first list item on another line, or doesn't exist yet
|
|
|
1144 (forward-line 1)
|
|
|
1145 (while (and (< (point) startpos)
|
|
|
1146 (looking-at "[ \t]*[#\n\\\\]")) ; skip noise
|
|
|
1147 (forward-line 1))
|
|
|
1148 (if (< (point) startpos)
|
|
|
1149 ;; again mimic the first list item
|
|
|
1150 (current-indentation)
|
|
|
1151 ;; else they're about to enter the first item
|
|
|
1152 (goto-char open-bracket-pos)
|
|
|
1153 (+ (current-indentation) py-indent-offset))))
|
|
|
1154
|
|
|
1155 ;; else on backslash continuation line
|
|
|
1156 (forward-line -1)
|
|
|
1157 (if (py-continuation-line-p) ; on at least 3rd line in block
|
|
|
1158 (current-indentation) ; so just continue the pattern
|
|
|
1159 ;; else started on 2nd line in block, so indent more.
|
|
|
1160 ;; if base line is an assignment with a start on a RHS,
|
|
|
1161 ;; indent to 2 beyond the leftmost "="; else skip first
|
|
|
1162 ;; chunk of non-whitespace characters on base line, + 1 more
|
|
|
1163 ;; column
|
|
|
1164 (end-of-line)
|
|
|
1165 (setq endpos (point) searching t)
|
|
|
1166 (back-to-indentation)
|
|
|
1167 (setq startpos (point))
|
|
|
1168 ;; look at all "=" from left to right, stopping at first
|
|
|
1169 ;; one not nested in a list or string
|
|
|
1170 (while searching
|
|
|
1171 (skip-chars-forward "^=" endpos)
|
|
|
1172 (if (= (point) endpos)
|
|
|
1173 (setq searching nil)
|
|
|
1174 (forward-char 1)
|
|
|
1175 (setq state (parse-partial-sexp startpos (point)))
|
|
|
1176 (if (and (zerop (car state)) ; not in a bracket
|
|
|
1177 (null (nth 3 state))) ; & not in a string
|
|
|
1178 (progn
|
|
|
1179 (setq searching nil) ; done searching in any case
|
|
|
1180 (setq found
|
|
|
1181 (not (or
|
|
|
1182 (eq (following-char) ?=)
|
|
|
1183 (memq (char-after (- (point) 2))
|
|
|
1184 '(?< ?> ?!)))))))))
|
|
|
1185 (if (or (not found) ; not an assignment
|
|
|
1186 (looking-at "[ \t]*\\\\")) ; <=><spaces><backslash>
|
|
|
1187 (progn
|
|
|
1188 (goto-char startpos)
|
|
|
1189 (skip-chars-forward "^ \t\n")))
|
|
|
1190 (1+ (current-column))))))
|
|
|
1191
|
|
|
1192 ;; not on a continuation line
|
|
|
1193 ((bobp) (current-indentation))
|
|
|
1194
|
|
|
1195 ;; Dfn: "Indenting comment line". A line containing only a
|
|
|
1196 ;; comment, but which is treated like a statement for
|
|
|
1197 ;; indentation calculation purposes. Such lines are only
|
|
|
1198 ;; treated specially by the mode; they are not treated
|
|
|
1199 ;; specially by the Python interpreter.
|
|
|
1200
|
|
|
1201 ;; The rules for indenting comment lines are a line where:
|
|
|
1202 ;; - the first non-whitespace character is `#', and
|
|
|
1203 ;; - the character following the `#' is whitespace, and
|
|
|
1204 ;; - the line is outdented with respect to (i.e. to the left
|
|
|
1205 ;; of) the indentation of the preceding non-blank line.
|
|
|
1206
|
|
|
1207 ;; The first non-blank line following an indenting comment
|
|
|
1208 ;; line is given the same amount of indentation as the
|
|
|
1209 ;; indenting comment line.
|
|
|
1210
|
|
|
1211 ;; All other comment-only lines are ignored for indentation
|
|
|
1212 ;; purposes.
|
|
|
1213
|
|
|
1214 ;; Are we looking at a comment-only line which is *not* an
|
|
|
1215 ;; indenting comment line? If so, we assume that its been
|
|
|
1216 ;; placed at the desired indentation, so leave it alone.
|
|
|
1217 ;; Indenting comment lines are aligned as statements down
|
|
|
1218 ;; below.
|
|
|
1219 ((and (looking-at "[ \t]*#[^ \t\n]")
|
|
|
1220 ;; NOTE: this test will not be performed in older Emacsen
|
|
|
1221 (fboundp 'forward-comment)
|
|
|
1222 (<= (current-indentation)
|
|
|
1223 (save-excursion
|
|
|
1224 (forward-comment (- (point-max)))
|
|
|
1225 (current-indentation))))
|
|
|
1226 (current-indentation))
|
|
|
1227
|
|
|
1228 ;; else indentation based on that of the statement that
|
|
|
1229 ;; precedes us; use the first line of that statement to
|
|
|
1230 ;; establish the base, in case the user forced a non-std
|
|
|
1231 ;; indentation for the continuation lines (if any)
|
|
|
1232 (t
|
|
|
1233 ;; skip back over blank & non-indenting comment lines note:
|
|
|
1234 ;; will skip a blank or non-indenting comment line that
|
|
|
1235 ;; happens to be a continuation line too. use fast Emacs 19
|
|
|
1236 ;; function if it's there.
|
|
|
1237 (if (and (eq py-honor-comment-indentation nil)
|
|
|
1238 (fboundp 'forward-comment))
|
|
|
1239 (forward-comment (- (point-max)))
|
|
|
1240 (let (done)
|
|
|
1241 (while (not done)
|
|
|
1242 (re-search-backward "^[ \t]*\\([^ \t\n#]\\|#[ \t\n]\\)"
|
|
|
1243 nil 'move)
|
|
|
1244 (setq done (or (eq py-honor-comment-indentation t)
|
|
|
1245 (bobp)
|
|
|
1246 (/= (following-char) ?#)
|
|
|
1247 (not (zerop (current-column)))))
|
|
|
1248 )))
|
|
|
1249 ;; if we landed inside a string, go to the beginning of that
|
|
|
1250 ;; string. this handles triple quoted, multi-line spanning
|
|
|
1251 ;; strings.
|
|
|
1252 (py-goto-initial-line)
|
|
|
1253 (+ (current-indentation)
|
|
|
1254 (if (py-statement-opens-block-p)
|
|
|
1255 py-indent-offset
|
|
4
|
1256 (if (and honor-block-close-p (py-statement-closes-block-p))
|
|
2
|
1257 (- py-indent-offset)
|
|
|
1258 0)))
|
|
|
1259 )))))
|
|
|
1260
|
|
|
1261 (defun py-guess-indent-offset (&optional global)
|
|
|
1262 "Guess a good value for, and change, `py-indent-offset'.
|
|
|
1263 By default (without a prefix arg), makes a buffer-local copy of
|
|
|
1264 `py-indent-offset' with the new value. This will not affect any other
|
|
|
1265 Python buffers. With a prefix arg, changes the global value of
|
|
|
1266 `py-indent-offset'. This affects all Python buffers (that don't have
|
|
|
1267 their own buffer-local copy), both those currently existing and those
|
|
|
1268 created later in the Emacs session.
|
|
|
1269
|
|
|
1270 Some people use a different value for `py-indent-offset' than you use.
|
|
|
1271 There's no excuse for such foolishness, but sometimes you have to deal
|
|
|
1272 with their ugly code anyway. This function examines the file and sets
|
|
|
1273 `py-indent-offset' to what it thinks it was when they created the
|
|
|
1274 mess.
|
|
|
1275
|
|
|
1276 Specifically, it searches forward from the statement containing point,
|
|
|
1277 looking for a line that opens a block of code. `py-indent-offset' is
|
|
|
1278 set to the difference in indentation between that line and the Python
|
|
|
1279 statement following it. If the search doesn't succeed going forward,
|
|
|
1280 it's tried again going backward."
|
|
|
1281 (interactive "P") ; raw prefix arg
|
|
|
1282 (let (new-value
|
|
|
1283 (start (point))
|
|
|
1284 restart
|
|
|
1285 (found nil)
|
|
|
1286 colon-indent)
|
|
|
1287 (py-goto-initial-line)
|
|
|
1288 (while (not (or found (eobp)))
|
|
|
1289 (if (re-search-forward ":[ \t]*\\($\\|[#\\]\\)" nil 'move)
|
|
|
1290 (progn
|
|
|
1291 (setq restart (point))
|
|
|
1292 (py-goto-initial-line)
|
|
|
1293 (if (py-statement-opens-block-p)
|
|
|
1294 (setq found t)
|
|
|
1295 (goto-char restart)))))
|
|
|
1296 (if found
|
|
|
1297 ()
|
|
|
1298 (goto-char start)
|
|
|
1299 (py-goto-initial-line)
|
|
|
1300 (while (not (or found (bobp)))
|
|
|
1301 (setq found
|
|
|
1302 (and
|
|
|
1303 (re-search-backward ":[ \t]*\\($\\|[#\\]\\)" nil 'move)
|
|
|
1304 (or (py-goto-initial-line) t) ; always true -- side effect
|
|
|
1305 (py-statement-opens-block-p)))))
|
|
|
1306 (setq colon-indent (current-indentation)
|
|
|
1307 found (and found (zerop (py-next-statement 1)))
|
|
|
1308 new-value (- (current-indentation) colon-indent))
|
|
|
1309 (goto-char start)
|
|
|
1310 (if found
|
|
|
1311 (progn
|
|
|
1312 (funcall (if global 'kill-local-variable 'make-local-variable)
|
|
|
1313 'py-indent-offset)
|
|
|
1314 (setq py-indent-offset new-value)
|
|
|
1315 (message "%s value of py-indent-offset set to %d"
|
|
|
1316 (if global "Global" "Local")
|
|
|
1317 py-indent-offset))
|
|
|
1318 (error "Sorry, couldn't guess a value for py-indent-offset"))))
|
|
|
1319
|
|
|
1320 (defun py-shift-region (start end count)
|
|
|
1321 (save-excursion
|
|
|
1322 (goto-char end) (beginning-of-line) (setq end (point))
|
|
|
1323 (goto-char start) (beginning-of-line) (setq start (point))
|
|
|
1324 (indent-rigidly start end count)))
|
|
|
1325
|
|
|
1326 (defun py-shift-region-left (start end &optional count)
|
|
|
1327 "Shift region of Python code to the left.
|
|
|
1328 The lines from the line containing the start of the current region up
|
|
|
1329 to (but not including) the line containing the end of the region are
|
|
|
1330 shifted to the left, by `py-indent-offset' columns.
|
|
|
1331
|
|
|
1332 If a prefix argument is given, the region is instead shifted by that
|
|
|
1333 many columns. With no active region, outdent only the current line.
|
|
|
1334 You cannot outdent the region if any line is already at column zero."
|
|
|
1335 (interactive
|
|
|
1336 (let ((p (point))
|
|
|
1337 (m (mark))
|
|
|
1338 (arg current-prefix-arg))
|
|
|
1339 (if m
|
|
|
1340 (list (min p m) (max p m) arg)
|
|
|
1341 (list p (save-excursion (forward-line 1) (point)) arg))))
|
|
|
1342 ;; if any line is at column zero, don't shift the region
|
|
|
1343 (save-excursion
|
|
|
1344 (goto-char start)
|
|
|
1345 (while (< (point) end)
|
|
|
1346 (back-to-indentation)
|
|
|
1347 (if (and (zerop (current-column))
|
|
|
1348 (not (looking-at "\\s *$")))
|
|
|
1349 (error "Region is at left edge."))
|
|
|
1350 (forward-line 1)))
|
|
|
1351 (py-shift-region start end (- (prefix-numeric-value
|
|
|
1352 (or count py-indent-offset))))
|
|
|
1353 (py-keep-region-active))
|
|
|
1354
|
|
|
1355 (defun py-shift-region-right (start end &optional count)
|
|
|
1356 "Shift region of Python code to the right.
|
|
|
1357 The lines from the line containing the start of the current region up
|
|
|
1358 to (but not including) the line containing the end of the region are
|
|
|
1359 shifted to the right, by `py-indent-offset' columns.
|
|
|
1360
|
|
|
1361 If a prefix argument is given, the region is instead shifted by that
|
|
|
1362 many columns. With no active region, indent only the current line."
|
|
|
1363 (interactive
|
|
|
1364 (let ((p (point))
|
|
|
1365 (m (mark))
|
|
|
1366 (arg current-prefix-arg))
|
|
|
1367 (if m
|
|
|
1368 (list (min p m) (max p m) arg)
|
|
|
1369 (list p (save-excursion (forward-line 1) (point)) arg))))
|
|
|
1370 (py-shift-region start end (prefix-numeric-value
|
|
|
1371 (or count py-indent-offset)))
|
|
|
1372 (py-keep-region-active))
|
|
|
1373
|
|
|
1374 (defun py-indent-region (start end &optional indent-offset)
|
|
|
1375 "Reindent a region of Python code.
|
|
|
1376
|
|
|
1377 The lines from the line containing the start of the current region up
|
|
|
1378 to (but not including) the line containing the end of the region are
|
|
|
1379 reindented. If the first line of the region has a non-whitespace
|
|
|
1380 character in the first column, the first line is left alone and the
|
|
|
1381 rest of the region is reindented with respect to it. Else the entire
|
|
|
1382 region is reindented with respect to the (closest code or indenting
|
|
|
1383 comment) statement immediately preceding the region.
|
|
|
1384
|
|
|
1385 This is useful when code blocks are moved or yanked, when enclosing
|
|
|
1386 control structures are introduced or removed, or to reformat code
|
|
|
1387 using a new value for the indentation offset.
|
|
|
1388
|
|
|
1389 If a numeric prefix argument is given, it will be used as the value of
|
|
|
1390 the indentation offset. Else the value of `py-indent-offset' will be
|
|
|
1391 used.
|
|
|
1392
|
|
|
1393 Warning: The region must be consistently indented before this function
|
|
|
1394 is called! This function does not compute proper indentation from
|
|
|
1395 scratch (that's impossible in Python), it merely adjusts the existing
|
|
|
1396 indentation to be correct in context.
|
|
|
1397
|
|
|
1398 Warning: This function really has no idea what to do with
|
|
|
1399 non-indenting comment lines, and shifts them as if they were indenting
|
|
|
1400 comment lines. Fixing this appears to require telepathy.
|
|
|
1401
|
|
|
1402 Special cases: whitespace is deleted from blank lines; continuation
|
|
|
1403 lines are shifted by the same amount their initial line was shifted,
|
|
|
1404 in order to preserve their relative indentation with respect to their
|
|
|
1405 initial line; and comment lines beginning in column 1 are ignored."
|
|
|
1406 (interactive "*r\nP") ; region; raw prefix arg
|
|
|
1407 (save-excursion
|
|
|
1408 (goto-char end) (beginning-of-line) (setq end (point-marker))
|
|
|
1409 (goto-char start) (beginning-of-line)
|
|
|
1410 (let ((py-indent-offset (prefix-numeric-value
|
|
|
1411 (or indent-offset py-indent-offset)))
|
|
|
1412 (indents '(-1)) ; stack of active indent levels
|
|
|
1413 (target-column 0) ; column to which to indent
|
|
|
1414 (base-shifted-by 0) ; amount last base line was shifted
|
|
|
1415 (indent-base (if (looking-at "[ \t\n]")
|
|
4
|
1416 (py-compute-indentation t)
|
|
2
|
1417 0))
|
|
|
1418 ci)
|
|
|
1419 (while (< (point) end)
|
|
|
1420 (setq ci (current-indentation))
|
|
|
1421 ;; figure out appropriate target column
|
|
|
1422 (cond
|
|
|
1423 ((or (eq (following-char) ?#) ; comment in column 1
|
|
|
1424 (looking-at "[ \t]*$")) ; entirely blank
|
|
|
1425 (setq target-column 0))
|
|
|
1426 ((py-continuation-line-p) ; shift relative to base line
|
|
|
1427 (setq target-column (+ ci base-shifted-by)))
|
|
|
1428 (t ; new base line
|
|
|
1429 (if (> ci (car indents)) ; going deeper; push it
|
|
|
1430 (setq indents (cons ci indents))
|
|
|
1431 ;; else we should have seen this indent before
|
|
|
1432 (setq indents (memq ci indents)) ; pop deeper indents
|
|
|
1433 (if (null indents)
|
|
|
1434 (error "Bad indentation in region, at line %d"
|
|
|
1435 (save-restriction
|
|
|
1436 (widen)
|
|
|
1437 (1+ (count-lines 1 (point)))))))
|
|
|
1438 (setq target-column (+ indent-base
|
|
|
1439 (* py-indent-offset
|
|
|
1440 (- (length indents) 2))))
|
|
|
1441 (setq base-shifted-by (- target-column ci))))
|
|
|
1442 ;; shift as needed
|
|
|
1443 (if (/= ci target-column)
|
|
|
1444 (progn
|
|
|
1445 (delete-horizontal-space)
|
|
|
1446 (indent-to target-column)))
|
|
|
1447 (forward-line 1))))
|
|
|
1448 (set-marker end nil))
|
|
|
1449
|
|
|
1450 (defun py-comment-region (beg end &optional arg)
|
|
|
1451 "Like `comment-region' but uses double hash (`#') comment starter."
|
|
|
1452 (interactive "r\nP")
|
|
|
1453 (let ((comment-start py-block-comment-prefix))
|
|
|
1454 (comment-region beg end arg)))
|
|
|
1455
|
|
|
1456
|
|
|
1457 ;; Functions for moving point
|
|
|
1458 (defun py-previous-statement (count)
|
|
|
1459 "Go to the start of previous Python statement.
|
|
|
1460 If the statement at point is the i'th Python statement, goes to the
|
|
|
1461 start of statement i-COUNT. If there is no such statement, goes to the
|
|
|
1462 first statement. Returns count of statements left to move.
|
|
|
1463 `Statements' do not include blank, comment, or continuation lines."
|
|
|
1464 (interactive "p") ; numeric prefix arg
|
|
|
1465 (if (< count 0) (py-next-statement (- count))
|
|
|
1466 (py-goto-initial-line)
|
|
|
1467 (let (start)
|
|
|
1468 (while (and
|
|
|
1469 (setq start (point)) ; always true -- side effect
|
|
|
1470 (> count 0)
|
|
|
1471 (zerop (forward-line -1))
|
|
|
1472 (py-goto-statement-at-or-above))
|
|
|
1473 (setq count (1- count)))
|
|
|
1474 (if (> count 0) (goto-char start)))
|
|
|
1475 count))
|
|
|
1476
|
|
|
1477 (defun py-next-statement (count)
|
|
|
1478 "Go to the start of next Python statement.
|
|
|
1479 If the statement at point is the i'th Python statement, goes to the
|
|
|
1480 start of statement i+COUNT. If there is no such statement, goes to the
|
|
|
1481 last statement. Returns count of statements left to move. `Statements'
|
|
|
1482 do not include blank, comment, or continuation lines."
|
|
|
1483 (interactive "p") ; numeric prefix arg
|
|
|
1484 (if (< count 0) (py-previous-statement (- count))
|
|
|
1485 (beginning-of-line)
|
|
|
1486 (let (start)
|
|
|
1487 (while (and
|
|
|
1488 (setq start (point)) ; always true -- side effect
|
|
|
1489 (> count 0)
|
|
|
1490 (py-goto-statement-below))
|
|
|
1491 (setq count (1- count)))
|
|
|
1492 (if (> count 0) (goto-char start)))
|
|
|
1493 count))
|
|
|
1494
|
|
|
1495 (defun py-goto-block-up (&optional nomark)
|
|
|
1496 "Move up to start of current block.
|
|
|
1497 Go to the statement that starts the smallest enclosing block; roughly
|
|
|
1498 speaking, this will be the closest preceding statement that ends with a
|
|
|
1499 colon and is indented less than the statement you started on. If
|
|
|
1500 successful, also sets the mark to the starting point.
|
|
|
1501
|
|
|
1502 `\\[py-mark-block]' can be used afterward to mark the whole code
|
|
|
1503 block, if desired.
|
|
|
1504
|
|
|
1505 If called from a program, the mark will not be set if optional argument
|
|
|
1506 NOMARK is not nil."
|
|
|
1507 (interactive)
|
|
|
1508 (let ((start (point))
|
|
|
1509 (found nil)
|
|
|
1510 initial-indent)
|
|
|
1511 (py-goto-initial-line)
|
|
|
1512 ;; if on blank or non-indenting comment line, use the preceding stmt
|
|
|
1513 (if (looking-at "[ \t]*\\($\\|#[^ \t\n]\\)")
|
|
|
1514 (progn
|
|
|
1515 (py-goto-statement-at-or-above)
|
|
|
1516 (setq found (py-statement-opens-block-p))))
|
|
|
1517 ;; search back for colon line indented less
|
|
|
1518 (setq initial-indent (current-indentation))
|
|
|
1519 (if (zerop initial-indent)
|
|
|
1520 ;; force fast exit
|
|
|
1521 (goto-char (point-min)))
|
|
|
1522 (while (not (or found (bobp)))
|
|
|
1523 (setq found
|
|
|
1524 (and
|
|
|
1525 (re-search-backward ":[ \t]*\\($\\|[#\\]\\)" nil 'move)
|
|
|
1526 (or (py-goto-initial-line) t) ; always true -- side effect
|
|
|
1527 (< (current-indentation) initial-indent)
|
|
|
1528 (py-statement-opens-block-p))))
|
|
|
1529 (if found
|
|
|
1530 (progn
|
|
|
1531 (or nomark (push-mark start))
|
|
|
1532 (back-to-indentation))
|
|
|
1533 (goto-char start)
|
|
|
1534 (error "Enclosing block not found"))))
|
|
|
1535
|
|
|
1536 (defun beginning-of-python-def-or-class (&optional class)
|
|
|
1537 "Move point to start of def (or class, with prefix arg).
|
|
|
1538
|
|
|
1539 Searches back for the closest preceding `def'. If you supply a prefix
|
|
|
1540 arg, looks for a `class' instead. The docs assume the `def' case;
|
|
|
1541 just substitute `class' for `def' for the other case.
|
|
|
1542
|
|
|
1543 If point is in a def statement already, and after the `d', simply
|
|
|
1544 moves point to the start of the statement.
|
|
|
1545
|
|
|
1546 Else (point is not in a def statement, or at or before the `d' of a
|
|
|
1547 def statement), searches for the closest preceding def statement, and
|
|
|
1548 leaves point at its start. If no such statement can be found, leaves
|
|
|
1549 point at the start of the buffer.
|
|
|
1550
|
|
|
1551 Returns t iff a def statement is found by these rules.
|
|
|
1552
|
|
|
1553 Note that doing this command repeatedly will take you closer to the
|
|
|
1554 start of the buffer each time.
|
|
|
1555
|
|
|
1556 If you want to mark the current def/class, see
|
|
|
1557 `\\[mark-python-def-or-class]'."
|
|
|
1558 (interactive "P") ; raw prefix arg
|
|
|
1559 (let ((at-or-before-p (<= (current-column) (current-indentation)))
|
|
|
1560 (start-of-line (progn (beginning-of-line) (point)))
|
|
|
1561 (start-of-stmt (progn (py-goto-initial-line) (point))))
|
|
|
1562 (if (or (/= start-of-stmt start-of-line)
|
|
|
1563 (not at-or-before-p))
|
|
|
1564 (end-of-line)) ; OK to match on this line
|
|
|
1565 (re-search-backward (if class "^[ \t]*class\\>" "^[ \t]*def\\>")
|
|
|
1566 nil 'move)))
|
|
|
1567
|
|
|
1568 (defun end-of-python-def-or-class (&optional class)
|
|
|
1569 "Move point beyond end of def (or class, with prefix arg) body.
|
|
|
1570
|
|
|
1571 By default, looks for an appropriate `def'. If you supply a prefix arg,
|
|
|
1572 looks for a `class' instead. The docs assume the `def' case; just
|
|
|
1573 substitute `class' for `def' for the other case.
|
|
|
1574
|
|
|
1575 If point is in a def statement already, this is the def we use.
|
|
|
1576
|
|
|
1577 Else if the def found by `\\[beginning-of-python-def-or-class]'
|
|
|
1578 contains the statement you started on, that's the def we use.
|
|
|
1579
|
|
|
1580 Else we search forward for the closest following def, and use that.
|
|
|
1581
|
|
|
1582 If a def can be found by these rules, point is moved to the start of
|
|
|
1583 the line immediately following the def block, and the position of the
|
|
|
1584 start of the def is returned.
|
|
|
1585
|
|
|
1586 Else point is moved to the end of the buffer, and nil is returned.
|
|
|
1587
|
|
|
1588 Note that doing this command repeatedly will take you closer to the
|
|
|
1589 end of the buffer each time.
|
|
|
1590
|
|
|
1591 If you want to mark the current def/class, see
|
|
|
1592 `\\[mark-python-def-or-class]'."
|
|
|
1593 (interactive "P") ; raw prefix arg
|
|
|
1594 (let ((start (progn (py-goto-initial-line) (point)))
|
|
|
1595 (which (if class "class" "def"))
|
|
|
1596 (state 'not-found))
|
|
|
1597 ;; move point to start of appropriate def/class
|
|
|
1598 (if (looking-at (concat "[ \t]*" which "\\>")) ; already on one
|
|
|
1599 (setq state 'at-beginning)
|
|
|
1600 ;; else see if beginning-of-python-def-or-class hits container
|
|
|
1601 (if (and (beginning-of-python-def-or-class class)
|
|
|
1602 (progn (py-goto-beyond-block)
|
|
|
1603 (> (point) start)))
|
|
|
1604 (setq state 'at-end)
|
|
|
1605 ;; else search forward
|
|
|
1606 (goto-char start)
|
|
|
1607 (if (re-search-forward (concat "^[ \t]*" which "\\>") nil 'move)
|
|
|
1608 (progn (setq state 'at-beginning)
|
|
|
1609 (beginning-of-line)))))
|
|
|
1610 (cond
|
|
|
1611 ((eq state 'at-beginning) (py-goto-beyond-block) t)
|
|
|
1612 ((eq state 'at-end) t)
|
|
|
1613 ((eq state 'not-found) nil)
|
|
|
1614 (t (error "internal error in end-of-python-def-or-class")))))
|
|
|
1615
|
|
|
1616
|
|
|
1617 ;; Functions for marking regions
|
|
|
1618 (defun py-mark-block (&optional extend just-move)
|
|
|
1619 "Mark following block of lines. With prefix arg, mark structure.
|
|
|
1620 Easier to use than explain. It sets the region to an `interesting'
|
|
|
1621 block of succeeding lines. If point is on a blank line, it goes down to
|
|
|
1622 the next non-blank line. That will be the start of the region. The end
|
|
|
1623 of the region depends on the kind of line at the start:
|
|
|
1624
|
|
|
1625 - If a comment, the region will include all succeeding comment lines up
|
|
|
1626 to (but not including) the next non-comment line (if any).
|
|
|
1627
|
|
|
1628 - Else if a prefix arg is given, and the line begins one of these
|
|
|
1629 structures:
|
|
|
1630
|
|
|
1631 if elif else try except finally for while def class
|
|
|
1632
|
|
|
1633 the region will be set to the body of the structure, including
|
|
|
1634 following blocks that `belong' to it, but excluding trailing blank
|
|
|
1635 and comment lines. E.g., if on a `try' statement, the `try' block
|
|
|
1636 and all (if any) of the following `except' and `finally' blocks
|
|
|
1637 that belong to the `try' structure will be in the region. Ditto
|
|
|
1638 for if/elif/else, for/else and while/else structures, and (a bit
|
|
|
1639 degenerate, since they're always one-block structures) def and
|
|
|
1640 class blocks.
|
|
|
1641
|
|
|
1642 - Else if no prefix argument is given, and the line begins a Python
|
|
|
1643 block (see list above), and the block is not a `one-liner' (i.e.,
|
|
|
1644 the statement ends with a colon, not with code), the region will
|
|
|
1645 include all succeeding lines up to (but not including) the next
|
|
|
1646 code statement (if any) that's indented no more than the starting
|
|
|
1647 line, except that trailing blank and comment lines are excluded.
|
|
|
1648 E.g., if the starting line begins a multi-statement `def'
|
|
|
1649 structure, the region will be set to the full function definition,
|
|
|
1650 but without any trailing `noise' lines.
|
|
|
1651
|
|
|
1652 - Else the region will include all succeeding lines up to (but not
|
|
|
1653 including) the next blank line, or code or indenting-comment line
|
|
|
1654 indented strictly less than the starting line. Trailing indenting
|
|
|
1655 comment lines are included in this case, but not trailing blank
|
|
|
1656 lines.
|
|
|
1657
|
|
|
1658 A msg identifying the location of the mark is displayed in the echo
|
|
|
1659 area; or do `\\[exchange-point-and-mark]' to flip down to the end.
|
|
|
1660
|
|
|
1661 If called from a program, optional argument EXTEND plays the role of
|
|
|
1662 the prefix arg, and if optional argument JUST-MOVE is not nil, just
|
|
|
1663 moves to the end of the block (& does not set mark or display a msg)."
|
|
|
1664 (interactive "P") ; raw prefix arg
|
|
|
1665 (py-goto-initial-line)
|
|
|
1666 ;; skip over blank lines
|
|
|
1667 (while (and
|
|
|
1668 (looking-at "[ \t]*$") ; while blank line
|
|
|
1669 (not (eobp))) ; & somewhere to go
|
|
|
1670 (forward-line 1))
|
|
|
1671 (if (eobp)
|
|
|
1672 (error "Hit end of buffer without finding a non-blank stmt"))
|
|
|
1673 (let ((initial-pos (point))
|
|
|
1674 (initial-indent (current-indentation))
|
|
|
1675 last-pos ; position of last stmt in region
|
|
|
1676 (followers
|
|
|
1677 '((if elif else) (elif elif else) (else)
|
|
|
1678 (try except finally) (except except) (finally)
|
|
|
1679 (for else) (while else)
|
|
|
1680 (def) (class) ) )
|
|
|
1681 first-symbol next-symbol)
|
|
|
1682
|
|
|
1683 (cond
|
|
|
1684 ;; if comment line, suck up the following comment lines
|
|
|
1685 ((looking-at "[ \t]*#")
|
|
|
1686 (re-search-forward "^[ \t]*[^ \t#]" nil 'move) ; look for non-comment
|
|
|
1687 (re-search-backward "^[ \t]*#") ; and back to last comment in block
|
|
|
1688 (setq last-pos (point)))
|
|
|
1689
|
|
|
1690 ;; else if line is a block line and EXTEND given, suck up
|
|
|
1691 ;; the whole structure
|
|
|
1692 ((and extend
|
|
|
1693 (setq first-symbol (py-suck-up-first-keyword) )
|
|
|
1694 (assq first-symbol followers))
|
|
|
1695 (while (and
|
|
|
1696 (or (py-goto-beyond-block) t) ; side effect
|
|
|
1697 (forward-line -1) ; side effect
|
|
|
1698 (setq last-pos (point)) ; side effect
|
|
|
1699 (py-goto-statement-below)
|
|
|
1700 (= (current-indentation) initial-indent)
|
|
|
1701 (setq next-symbol (py-suck-up-first-keyword))
|
|
|
1702 (memq next-symbol (cdr (assq first-symbol followers))))
|
|
|
1703 (setq first-symbol next-symbol)))
|
|
|
1704
|
|
|
1705 ;; else if line *opens* a block, search for next stmt indented <=
|
|
|
1706 ((py-statement-opens-block-p)
|
|
|
1707 (while (and
|
|
|
1708 (setq last-pos (point)) ; always true -- side effect
|
|
|
1709 (py-goto-statement-below)
|
|
|
1710 (> (current-indentation) initial-indent))
|
|
|
1711 nil))
|
|
|
1712
|
|
|
1713 ;; else plain code line; stop at next blank line, or stmt or
|
|
|
1714 ;; indenting comment line indented <
|
|
|
1715 (t
|
|
|
1716 (while (and
|
|
|
1717 (setq last-pos (point)) ; always true -- side effect
|
|
|
1718 (or (py-goto-beyond-final-line) t)
|
|
|
1719 (not (looking-at "[ \t]*$")) ; stop at blank line
|
|
|
1720 (or
|
|
|
1721 (>= (current-indentation) initial-indent)
|
|
|
1722 (looking-at "[ \t]*#[^ \t\n]"))) ; ignore non-indenting #
|
|
|
1723 nil)))
|
|
|
1724
|
|
|
1725 ;; skip to end of last stmt
|
|
|
1726 (goto-char last-pos)
|
|
|
1727 (py-goto-beyond-final-line)
|
|
|
1728
|
|
|
1729 ;; set mark & display
|
|
|
1730 (if just-move
|
|
|
1731 () ; just return
|
|
|
1732 (push-mark (point) 'no-msg)
|
|
|
1733 (forward-line -1)
|
|
|
1734 (message "Mark set after: %s" (py-suck-up-leading-text))
|
|
|
1735 (goto-char initial-pos))))
|
|
|
1736
|
|
|
1737 (defun mark-python-def-or-class (&optional class)
|
|
|
1738 "Set region to body of def (or class, with prefix arg) enclosing point.
|
|
|
1739 Pushes the current mark, then point, on the mark ring (all language
|
|
|
1740 modes do this, but although it's handy it's never documented ...).
|
|
|
1741
|
|
|
1742 In most Emacs language modes, this function bears at least a
|
|
|
1743 hallucinogenic resemblance to `\\[end-of-python-def-or-class]' and
|
|
|
1744 `\\[beginning-of-python-def-or-class]'.
|
|
|
1745
|
|
|
1746 And in earlier versions of Python mode, all 3 were tightly connected.
|
|
|
1747 Turned out that was more confusing than useful: the `goto start' and
|
|
|
1748 `goto end' commands are usually used to search through a file, and
|
|
|
1749 people expect them to act a lot like `search backward' and `search
|
|
|
1750 forward' string-search commands. But because Python `def' and `class'
|
|
|
1751 can nest to arbitrary levels, finding the smallest def containing
|
|
|
1752 point cannot be done via a simple backward search: the def containing
|
|
|
1753 point may not be the closest preceding def, or even the closest
|
|
|
1754 preceding def that's indented less. The fancy algorithm required is
|
|
|
1755 appropriate for the usual uses of this `mark' command, but not for the
|
|
|
1756 `goto' variations.
|
|
|
1757
|
|
|
1758 So the def marked by this command may not be the one either of the
|
|
|
1759 `goto' commands find: If point is on a blank or non-indenting comment
|
|
|
1760 line, moves back to start of the closest preceding code statement or
|
|
|
1761 indenting comment line. If this is a `def' statement, that's the def
|
|
|
1762 we use. Else searches for the smallest enclosing `def' block and uses
|
|
|
1763 that. Else signals an error.
|
|
|
1764
|
|
|
1765 When an enclosing def is found: The mark is left immediately beyond
|
|
|
1766 the last line of the def block. Point is left at the start of the
|
|
|
1767 def, except that: if the def is preceded by a number of comment lines
|
|
|
1768 followed by (at most) one optional blank line, point is left at the
|
|
|
1769 start of the comments; else if the def is preceded by a blank line,
|
|
|
1770 point is left at its start.
|
|
|
1771
|
|
|
1772 The intent is to mark the containing def/class and its associated
|
|
|
1773 documentation, to make moving and duplicating functions and classes
|
|
|
1774 pleasant."
|
|
|
1775 (interactive "P") ; raw prefix arg
|
|
|
1776 (let ((start (point))
|
|
|
1777 (which (if class "class" "def")))
|
|
|
1778 (push-mark start)
|
|
|
1779 (if (not (py-go-up-tree-to-keyword which))
|
|
|
1780 (progn (goto-char start)
|
|
|
1781 (error "Enclosing %s not found" which))
|
|
|
1782 ;; else enclosing def/class found
|
|
|
1783 (setq start (point))
|
|
|
1784 (py-goto-beyond-block)
|
|
|
1785 (push-mark (point))
|
|
|
1786 (goto-char start)
|
|
|
1787 (if (zerop (forward-line -1)) ; if there is a preceding line
|
|
|
1788 (progn
|
|
|
1789 (if (looking-at "[ \t]*$") ; it's blank
|
|
|
1790 (setq start (point)) ; so reset start point
|
|
|
1791 (goto-char start)) ; else try again
|
|
|
1792 (if (zerop (forward-line -1))
|
|
|
1793 (if (looking-at "[ \t]*#") ; a comment
|
|
|
1794 ;; look back for non-comment line
|
|
|
1795 ;; tricky: note that the regexp matches a blank
|
|
|
1796 ;; line, cuz \n is in the 2nd character class
|
|
|
1797 (and
|
|
|
1798 (re-search-backward "^[ \t]*[^ \t#]" nil 'move)
|
|
|
1799 (forward-line 1))
|
|
|
1800 ;; no comment, so go back
|
|
|
1801 (goto-char start))))))))
|
|
|
1802
|
|
|
1803 ;; ripped from cc-mode
|
|
|
1804 (defun py-forward-into-nomenclature (&optional arg)
|
|
|
1805 "Move forward to end of a nomenclature section or word.
|
|
|
1806 With arg, to it arg times.
|
|
|
1807
|
|
|
1808 A `nomenclature' is a fancy way of saying AWordWithMixedCaseNotUnderscores."
|
|
|
1809 (interactive "p")
|
|
|
1810 (let ((case-fold-search nil))
|
|
|
1811 (if (> arg 0)
|
|
4
|
1812 (re-search-forward
|
|
|
1813 "\\(\\W\\|[_]\\)*\\([A-Z]*[a-z0-9]*\\)"
|
|
|
1814 (point-max) t arg)
|
|
2
|
1815 (while (and (< arg 0)
|
|
|
1816 (re-search-backward
|
|
4
|
1817 "\\(\\W\\|[a-z0-9]\\)[A-Z]+\\|\\(\\W\\|[_]\\)\\w+"
|
|
2
|
1818 (point-min) 0))
|
|
|
1819 (forward-char 1)
|
|
|
1820 (setq arg (1+ arg)))))
|
|
|
1821 (py-keep-region-active))
|
|
|
1822
|
|
|
1823 (defun py-backward-into-nomenclature (&optional arg)
|
|
|
1824 "Move backward to beginning of a nomenclature section or word.
|
|
|
1825 With optional ARG, move that many times. If ARG is negative, move
|
|
|
1826 forward.
|
|
|
1827
|
|
|
1828 A `nomenclature' is a fancy way of saying AWordWithMixedCaseNotUnderscores."
|
|
|
1829 (interactive "p")
|
|
|
1830 (py-forward-into-nomenclature (- arg))
|
|
|
1831 (py-keep-region-active))
|
|
|
1832
|
|
|
1833
|
|
|
1834
|
|
|
1835 ;; Documentation functions
|
|
|
1836
|
|
|
1837 ;; dump the long form of the mode blurb; does the usual doc escapes,
|
|
|
1838 ;; plus lines of the form ^[vc]:name$ to suck variable & command docs
|
|
|
1839 ;; out of the right places, along with the keys they're on & current
|
|
|
1840 ;; values
|
|
|
1841 (defun py-dump-help-string (str)
|
|
|
1842 (with-output-to-temp-buffer "*Help*"
|
|
|
1843 (let ((locals (buffer-local-variables))
|
|
|
1844 funckind funcname func funcdoc
|
|
|
1845 (start 0) mstart end
|
|
|
1846 keys )
|
|
|
1847 (while (string-match "^%\\([vc]\\):\\(.+\\)\n" str start)
|
|
|
1848 (setq mstart (match-beginning 0) end (match-end 0)
|
|
|
1849 funckind (substring str (match-beginning 1) (match-end 1))
|
|
|
1850 funcname (substring str (match-beginning 2) (match-end 2))
|
|
|
1851 func (intern funcname))
|
|
|
1852 (princ (substitute-command-keys (substring str start mstart)))
|
|
|
1853 (cond
|
|
|
1854 ((equal funckind "c") ; command
|
|
|
1855 (setq funcdoc (documentation func)
|
|
|
1856 keys (concat
|
|
|
1857 "Key(s): "
|
|
|
1858 (mapconcat 'key-description
|
|
|
1859 (where-is-internal func py-mode-map)
|
|
|
1860 ", "))))
|
|
|
1861 ((equal funckind "v") ; variable
|
|
4
|
1862 (setq funcdoc (documentation-property func 'variable-documentation)
|
|
2
|
1863 keys (if (assq func locals)
|
|
|
1864 (concat
|
|
|
1865 "Local/Global values: "
|
|
|
1866 (prin1-to-string (symbol-value func))
|
|
|
1867 " / "
|
|
|
1868 (prin1-to-string (default-value func)))
|
|
|
1869 (concat
|
|
|
1870 "Value: "
|
|
|
1871 (prin1-to-string (symbol-value func))))))
|
|
|
1872 (t ; unexpected
|
|
|
1873 (error "Error in py-dump-help-string, tag `%s'" funckind)))
|
|
|
1874 (princ (format "\n-> %s:\t%s\t%s\n\n"
|
|
|
1875 (if (equal funckind "c") "Command" "Variable")
|
|
|
1876 funcname keys))
|
|
|
1877 (princ funcdoc)
|
|
|
1878 (terpri)
|
|
|
1879 (setq start end))
|
|
|
1880 (princ (substitute-command-keys (substring str start))))
|
|
|
1881 (print-help-return-message)))
|
|
|
1882
|
|
|
1883 (defun py-describe-mode ()
|
|
|
1884 "Dump long form of Python-mode docs."
|
|
|
1885 (interactive)
|
|
|
1886 (py-dump-help-string "Major mode for editing Python files.
|
|
|
1887 Knows about Python indentation, tokens, comments and continuation lines.
|
|
|
1888 Paragraphs are separated by blank lines only.
|
|
|
1889
|
|
|
1890 Major sections below begin with the string `@'; specific function and
|
|
|
1891 variable docs begin with `->'.
|
|
|
1892
|
|
|
1893 @EXECUTING PYTHON CODE
|
|
|
1894
|
|
|
1895 \\[py-execute-buffer]\tsends the entire buffer to the Python interpreter
|
|
|
1896 \\[py-execute-region]\tsends the current region
|
|
|
1897 \\[py-shell]\tstarts a Python interpreter window; this will be used by
|
|
|
1898 \tsubsequent \\[py-execute-buffer] or \\[py-execute-region] commands
|
|
|
1899 %c:py-execute-buffer
|
|
|
1900 %c:py-execute-region
|
|
|
1901 %c:py-shell
|
|
|
1902
|
|
|
1903 @VARIABLES
|
|
|
1904
|
|
|
1905 py-indent-offset\tindentation increment
|
|
|
1906 py-block-comment-prefix\tcomment string used by comment-region
|
|
|
1907
|
|
|
1908 py-python-command\tshell command to invoke Python interpreter
|
|
|
1909 py-scroll-process-buffer\talways scroll Python process buffer
|
|
|
1910 py-temp-directory\tdirectory used for temp files (if needed)
|
|
|
1911
|
|
|
1912 py-beep-if-tab-change\tring the bell if tab-width is changed
|
|
|
1913 %v:py-indent-offset
|
|
|
1914 %v:py-block-comment-prefix
|
|
|
1915 %v:py-python-command
|
|
|
1916 %v:py-scroll-process-buffer
|
|
|
1917 %v:py-temp-directory
|
|
|
1918 %v:py-beep-if-tab-change
|
|
|
1919
|
|
|
1920 @KINDS OF LINES
|
|
|
1921
|
|
|
1922 Each physical line in the file is either a `continuation line' (the
|
|
|
1923 preceding line ends with a backslash that's not part of a comment, or
|
|
|
1924 the paren/bracket/brace nesting level at the start of the line is
|
|
|
1925 non-zero, or both) or an `initial line' (everything else).
|
|
|
1926
|
|
|
1927 An initial line is in turn a `blank line' (contains nothing except
|
|
|
1928 possibly blanks or tabs), a `comment line' (leftmost non-blank
|
|
|
1929 character is `#'), or a `code line' (everything else).
|
|
|
1930
|
|
|
1931 Comment Lines
|
|
|
1932
|
|
|
1933 Although all comment lines are treated alike by Python, Python mode
|
|
|
1934 recognizes two kinds that act differently with respect to indentation.
|
|
|
1935
|
|
|
1936 An `indenting comment line' is a comment line with a blank, tab or
|
|
|
1937 nothing after the initial `#'. The indentation commands (see below)
|
|
|
1938 treat these exactly as if they were code lines: a line following an
|
|
|
1939 indenting comment line will be indented like the comment line. All
|
|
|
1940 other comment lines (those with a non-whitespace character immediately
|
|
|
1941 following the initial `#') are `non-indenting comment lines', and
|
|
|
1942 their indentation is ignored by the indentation commands.
|
|
|
1943
|
|
|
1944 Indenting comment lines are by far the usual case, and should be used
|
|
|
1945 whenever possible. Non-indenting comment lines are useful in cases
|
|
|
1946 like these:
|
|
|
1947
|
|
|
1948 \ta = b # a very wordy single-line comment that ends up being
|
|
|
1949 \t #... continued onto another line
|
|
|
1950
|
|
|
1951 \tif a == b:
|
|
|
1952 ##\t\tprint 'panic!' # old code we've `commented out'
|
|
|
1953 \t\treturn a
|
|
|
1954
|
|
|
1955 Since the `#...' and `##' comment lines have a non-whitespace
|
|
|
1956 character following the initial `#', Python mode ignores them when
|
|
|
1957 computing the proper indentation for the next line.
|
|
|
1958
|
|
|
1959 Continuation Lines and Statements
|
|
|
1960
|
|
|
1961 The Python-mode commands generally work on statements instead of on
|
|
|
1962 individual lines, where a `statement' is a comment or blank line, or a
|
|
|
1963 code line and all of its following continuation lines (if any)
|
|
|
1964 considered as a single logical unit. The commands in this mode
|
|
|
1965 generally (when it makes sense) automatically move to the start of the
|
|
|
1966 statement containing point, even if point happens to be in the middle
|
|
|
1967 of some continuation line.
|
|
|
1968
|
|
|
1969
|
|
|
1970 @INDENTATION
|
|
|
1971
|
|
|
1972 Primarily for entering new code:
|
|
|
1973 \t\\[indent-for-tab-command]\t indent line appropriately
|
|
|
1974 \t\\[py-newline-and-indent]\t insert newline, then indent
|
|
|
1975 \t\\[py-delete-char]\t reduce indentation, or delete single character
|
|
|
1976
|
|
|
1977 Primarily for reindenting existing code:
|
|
|
1978 \t\\[py-guess-indent-offset]\t guess py-indent-offset from file content; change locally
|
|
|
1979 \t\\[universal-argument] \\[py-guess-indent-offset]\t ditto, but change globally
|
|
|
1980
|
|
|
1981 \t\\[py-indent-region]\t reindent region to match its context
|
|
|
1982 \t\\[py-shift-region-left]\t shift region left by py-indent-offset
|
|
|
1983 \t\\[py-shift-region-right]\t shift region right by py-indent-offset
|
|
|
1984
|
|
|
1985 Unlike most programming languages, Python uses indentation, and only
|
|
|
1986 indentation, to specify block structure. Hence the indentation supplied
|
|
|
1987 automatically by Python-mode is just an educated guess: only you know
|
|
|
1988 the block structure you intend, so only you can supply correct
|
|
|
1989 indentation.
|
|
|
1990
|
|
|
1991 The \\[indent-for-tab-command] and \\[py-newline-and-indent] keys try to suggest plausible indentation, based on
|
|
|
1992 the indentation of preceding statements. E.g., assuming
|
|
|
1993 py-indent-offset is 4, after you enter
|
|
|
1994 \tif a > 0: \\[py-newline-and-indent]
|
|
|
1995 the cursor will be moved to the position of the `_' (_ is not a
|
|
|
1996 character in the file, it's just used here to indicate the location of
|
|
|
1997 the cursor):
|
|
|
1998 \tif a > 0:
|
|
|
1999 \t _
|
|
|
2000 If you then enter `c = d' \\[py-newline-and-indent], the cursor will move
|
|
|
2001 to
|
|
|
2002 \tif a > 0:
|
|
|
2003 \t c = d
|
|
|
2004 \t _
|
|
|
2005 Python-mode cannot know whether that's what you intended, or whether
|
|
|
2006 \tif a > 0:
|
|
|
2007 \t c = d
|
|
|
2008 \t_
|
|
|
2009 was your intent. In general, Python-mode either reproduces the
|
|
|
2010 indentation of the (closest code or indenting-comment) preceding
|
|
|
2011 statement, or adds an extra py-indent-offset blanks if the preceding
|
|
|
2012 statement has `:' as its last significant (non-whitespace and non-
|
|
|
2013 comment) character. If the suggested indentation is too much, use
|
|
|
2014 \\[py-delete-char] to reduce it.
|
|
|
2015
|
|
|
2016 Continuation lines are given extra indentation. If you don't like the
|
|
|
2017 suggested indentation, change it to something you do like, and Python-
|
|
|
2018 mode will strive to indent later lines of the statement in the same way.
|
|
|
2019
|
|
|
2020 If a line is a continuation line by virtue of being in an unclosed
|
|
|
2021 paren/bracket/brace structure (`list', for short), the suggested
|
|
|
2022 indentation depends on whether the current line contains the first item
|
|
|
2023 in the list. If it does, it's indented py-indent-offset columns beyond
|
|
|
2024 the indentation of the line containing the open bracket. If you don't
|
|
|
2025 like that, change it by hand. The remaining items in the list will mimic
|
|
|
2026 whatever indentation you give to the first item.
|
|
|
2027
|
|
|
2028 If a line is a continuation line because the line preceding it ends with
|
|
|
2029 a backslash, the third and following lines of the statement inherit their
|
|
|
2030 indentation from the line preceding them. The indentation of the second
|
|
|
2031 line in the statement depends on the form of the first (base) line: if
|
|
|
2032 the base line is an assignment statement with anything more interesting
|
|
|
2033 than the backslash following the leftmost assigning `=', the second line
|
|
|
2034 is indented two columns beyond that `='. Else it's indented to two
|
|
|
2035 columns beyond the leftmost solid chunk of non-whitespace characters on
|
|
|
2036 the base line.
|
|
|
2037
|
|
|
2038 Warning: indent-region should not normally be used! It calls \\[indent-for-tab-command]
|
|
|
2039 repeatedly, and as explained above, \\[indent-for-tab-command] can't guess the block
|
|
|
2040 structure you intend.
|
|
|
2041 %c:indent-for-tab-command
|
|
|
2042 %c:py-newline-and-indent
|
|
|
2043 %c:py-delete-char
|
|
|
2044
|
|
|
2045
|
|
|
2046 The next function may be handy when editing code you didn't write:
|
|
|
2047 %c:py-guess-indent-offset
|
|
|
2048
|
|
|
2049
|
|
|
2050 The remaining `indent' functions apply to a region of Python code. They
|
|
|
2051 assume the block structure (equals indentation, in Python) of the region
|
|
|
2052 is correct, and alter the indentation in various ways while preserving
|
|
|
2053 the block structure:
|
|
|
2054 %c:py-indent-region
|
|
|
2055 %c:py-shift-region-left
|
|
|
2056 %c:py-shift-region-right
|
|
|
2057
|
|
|
2058 @MARKING & MANIPULATING REGIONS OF CODE
|
|
|
2059
|
|
|
2060 \\[py-mark-block]\t mark block of lines
|
|
|
2061 \\[mark-python-def-or-class]\t mark smallest enclosing def
|
|
|
2062 \\[universal-argument] \\[mark-python-def-or-class]\t mark smallest enclosing class
|
|
|
2063 \\[comment-region]\t comment out region of code
|
|
|
2064 \\[universal-argument] \\[comment-region]\t uncomment region of code
|
|
|
2065 %c:py-mark-block
|
|
|
2066 %c:mark-python-def-or-class
|
|
|
2067 %c:comment-region
|
|
|
2068
|
|
|
2069 @MOVING POINT
|
|
|
2070
|
|
|
2071 \\[py-previous-statement]\t move to statement preceding point
|
|
|
2072 \\[py-next-statement]\t move to statement following point
|
|
|
2073 \\[py-goto-block-up]\t move up to start of current block
|
|
|
2074 \\[beginning-of-python-def-or-class]\t move to start of def
|
|
|
2075 \\[universal-argument] \\[beginning-of-python-def-or-class]\t move to start of class
|
|
|
2076 \\[end-of-python-def-or-class]\t move to end of def
|
|
|
2077 \\[universal-argument] \\[end-of-python-def-or-class]\t move to end of class
|
|
|
2078
|
|
|
2079 The first two move to one statement beyond the statement that contains
|
|
|
2080 point. A numeric prefix argument tells them to move that many
|
|
|
2081 statements instead. Blank lines, comment lines, and continuation lines
|
|
|
2082 do not count as `statements' for these commands. So, e.g., you can go
|
|
|
2083 to the first code statement in a file by entering
|
|
|
2084 \t\\[beginning-of-buffer]\t to move to the top of the file
|
|
|
2085 \t\\[py-next-statement]\t to skip over initial comments and blank lines
|
|
|
2086 Or do `\\[py-previous-statement]' with a huge prefix argument.
|
|
|
2087 %c:py-previous-statement
|
|
|
2088 %c:py-next-statement
|
|
|
2089 %c:py-goto-block-up
|
|
|
2090 %c:beginning-of-python-def-or-class
|
|
|
2091 %c:end-of-python-def-or-class
|
|
|
2092
|
|
|
2093 @LITTLE-KNOWN EMACS COMMANDS PARTICULARLY USEFUL IN PYTHON MODE
|
|
|
2094
|
|
|
2095 `\\[indent-new-comment-line]' is handy for entering a multi-line comment.
|
|
|
2096
|
|
|
2097 `\\[set-selective-display]' with a `small' prefix arg is ideally suited for viewing the
|
|
|
2098 overall class and def structure of a module.
|
|
|
2099
|
|
|
2100 `\\[back-to-indentation]' moves point to a line's first non-blank character.
|
|
|
2101
|
|
|
2102 `\\[indent-relative]' is handy for creating odd indentation.
|
|
|
2103
|
|
|
2104 @OTHER EMACS HINTS
|
|
|
2105
|
|
|
2106 If you don't like the default value of a variable, change its value to
|
|
|
2107 whatever you do like by putting a `setq' line in your .emacs file.
|
|
|
2108 E.g., to set the indentation increment to 4, put this line in your
|
|
|
2109 .emacs:
|
|
|
2110 \t(setq py-indent-offset 4)
|
|
|
2111 To see the value of a variable, do `\\[describe-variable]' and enter the variable
|
|
|
2112 name at the prompt.
|
|
|
2113
|
|
|
2114 When entering a key sequence like `C-c C-n', it is not necessary to
|
|
|
2115 release the CONTROL key after doing the `C-c' part -- it suffices to
|
|
|
2116 press the CONTROL key, press and release `c' (while still holding down
|
|
|
2117 CONTROL), press and release `n' (while still holding down CONTROL), &
|
|
|
2118 then release CONTROL.
|
|
|
2119
|
|
|
2120 Entering Python mode calls with no arguments the value of the variable
|
|
|
2121 `python-mode-hook', if that value exists and is not nil; for backward
|
|
|
2122 compatibility it also tries `py-mode-hook'; see the `Hooks' section of
|
|
|
2123 the Elisp manual for details.
|
|
|
2124
|
|
|
2125 Obscure: When python-mode is first loaded, it looks for all bindings
|
|
|
2126 to newline-and-indent in the global keymap, and shadows them with
|
|
|
2127 local bindings to py-newline-and-indent."))
|
|
|
2128
|
|
|
2129
|
|
|
2130 ;; Helper functions
|
|
|
2131 (defvar py-parse-state-re
|
|
|
2132 (concat
|
|
|
2133 "^[ \t]*\\(if\\|elif\\|else\\|while\\|def\\|class\\)\\>"
|
|
|
2134 "\\|"
|
|
|
2135 "^[^ #\t\n]"))
|
|
|
2136
|
|
|
2137 ;; returns the parse state at point (see parse-partial-sexp docs)
|
|
|
2138 (defun py-parse-state ()
|
|
|
2139 (save-excursion
|
|
|
2140 (let ((here (point))
|
|
|
2141 pps done ci)
|
|
|
2142 (while (not done)
|
|
|
2143 ;; back up to the first preceding line (if any; else start of
|
|
|
2144 ;; buffer) that begins with a popular Python keyword, or a
|
|
|
2145 ;; non- whitespace and non-comment character. These are good
|
|
|
2146 ;; places to start parsing to see whether where we started is
|
|
|
2147 ;; at a non-zero nesting level. It may be slow for people who
|
|
|
2148 ;; write huge code blocks or huge lists ... tough beans.
|
|
|
2149 (re-search-backward py-parse-state-re nil 'move)
|
|
|
2150 (setq ci (current-indentation))
|
|
|
2151 (beginning-of-line)
|
|
|
2152 (save-excursion
|
|
|
2153 (setq pps (parse-partial-sexp (point) here)))
|
|
|
2154 ;; make sure we don't land inside a triple-quoted string
|
|
|
2155 (setq done (or (zerop ci)
|
|
|
2156 (not (nth 3 pps))
|
|
|
2157 (bobp)))
|
|
|
2158 )
|
|
|
2159 pps)))
|
|
|
2160
|
|
|
2161 ;; if point is at a non-zero nesting level, returns the number of the
|
|
|
2162 ;; character that opens the smallest enclosing unclosed list; else
|
|
|
2163 ;; returns nil.
|
|
|
2164 (defun py-nesting-level ()
|
|
|
2165 (let ((status (py-parse-state)) )
|
|
|
2166 (if (zerop (car status))
|
|
|
2167 nil ; not in a nest
|
|
|
2168 (car (cdr status))))) ; char# of open bracket
|
|
|
2169
|
|
|
2170 ;; t iff preceding line ends with backslash that's not in a comment
|
|
|
2171 (defun py-backslash-continuation-line-p ()
|
|
|
2172 (save-excursion
|
|
|
2173 (beginning-of-line)
|
|
|
2174 (and
|
|
|
2175 ;; use a cheap test first to avoid the regexp if possible
|
|
|
2176 ;; use 'eq' because char-after may return nil
|
|
|
2177 (eq (char-after (- (point) 2)) ?\\ )
|
|
|
2178 ;; make sure; since eq test passed, there is a preceding line
|
|
|
2179 (forward-line -1) ; always true -- side effect
|
|
|
2180 (looking-at py-continued-re))))
|
|
|
2181
|
|
|
2182 ;; t iff current line is a continuation line
|
|
|
2183 (defun py-continuation-line-p ()
|
|
|
2184 (save-excursion
|
|
|
2185 (beginning-of-line)
|
|
|
2186 (or (py-backslash-continuation-line-p)
|
|
|
2187 (py-nesting-level))))
|
|
|
2188
|
|
|
2189 ;; go to initial line of current statement; usually this is the line
|
|
|
2190 ;; we're on, but if we're on the 2nd or following lines of a
|
|
|
2191 ;; continuation block, we need to go up to the first line of the
|
|
|
2192 ;; block.
|
|
|
2193 ;;
|
|
|
2194 ;; Tricky: We want to avoid quadratic-time behavior for long continued
|
|
|
2195 ;; blocks, whether of the backslash or open-bracket varieties, or a
|
|
|
2196 ;; mix of the two. The following manages to do that in the usual
|
|
|
2197 ;; cases.
|
|
|
2198 (defun py-goto-initial-line ()
|
|
|
2199 (let ( open-bracket-pos )
|
|
|
2200 (while (py-continuation-line-p)
|
|
|
2201 (beginning-of-line)
|
|
|
2202 (if (py-backslash-continuation-line-p)
|
|
|
2203 (while (py-backslash-continuation-line-p)
|
|
|
2204 (forward-line -1))
|
|
|
2205 ;; else zip out of nested brackets/braces/parens
|
|
|
2206 (while (setq open-bracket-pos (py-nesting-level))
|
|
|
2207 (goto-char open-bracket-pos)))))
|
|
|
2208 (beginning-of-line))
|
|
|
2209
|
|
|
2210 ;; go to point right beyond final line of current statement; usually
|
|
|
2211 ;; this is the start of the next line, but if this is a multi-line
|
|
|
2212 ;; statement we need to skip over the continuation lines. Tricky:
|
|
|
2213 ;; Again we need to be clever to avoid quadratic time behavior.
|
|
|
2214 (defun py-goto-beyond-final-line ()
|
|
|
2215 (forward-line 1)
|
|
|
2216 (let (state)
|
|
|
2217 (while (and (py-continuation-line-p)
|
|
|
2218 (not (eobp)))
|
|
|
2219 ;; skip over the backslash flavor
|
|
|
2220 (while (and (py-backslash-continuation-line-p)
|
|
|
2221 (not (eobp)))
|
|
|
2222 (forward-line 1))
|
|
|
2223 ;; if in nest, zip to the end of the nest
|
|
|
2224 (setq state (py-parse-state))
|
|
|
2225 (if (and (not (zerop (car state)))
|
|
|
2226 (not (eobp)))
|
|
|
2227 (progn
|
|
98
|
2228 (parse-partial-sexp (point) (point-max)
|
|
|
2229 (if py-parse-partial-sexp-works-p
|
|
|
2230 0 (- 0 (car state)))
|
|
2
|
2231 nil state)
|
|
|
2232 (forward-line 1))))))
|
|
|
2233
|
|
|
2234 ;; t iff statement opens a block == iff it ends with a colon that's
|
|
|
2235 ;; not in a comment. point should be at the start of a statement
|
|
|
2236 (defun py-statement-opens-block-p ()
|
|
|
2237 (save-excursion
|
|
|
2238 (let ((start (point))
|
|
|
2239 (finish (progn (py-goto-beyond-final-line) (1- (point))))
|
|
|
2240 (searching t)
|
|
|
2241 (answer nil)
|
|
|
2242 state)
|
|
|
2243 (goto-char start)
|
|
|
2244 (while searching
|
|
|
2245 ;; look for a colon with nothing after it except whitespace, and
|
|
|
2246 ;; maybe a comment
|
|
|
2247 (if (re-search-forward ":\\([ \t]\\|\\\\\n\\)*\\(#.*\\)?$"
|
|
|
2248 finish t)
|
|
|
2249 (if (eq (point) finish) ; note: no `else' clause; just
|
|
|
2250 ; keep searching if we're not at
|
|
|
2251 ; the end yet
|
|
|
2252 ;; sure looks like it opens a block -- but it might
|
|
|
2253 ;; be in a comment
|
|
|
2254 (progn
|
|
|
2255 (setq searching nil) ; search is done either way
|
|
|
2256 (setq state (parse-partial-sexp start
|
|
|
2257 (match-beginning 0)))
|
|
|
2258 (setq answer (not (nth 4 state)))))
|
|
|
2259 ;; search failed: couldn't find another interesting colon
|
|
|
2260 (setq searching nil)))
|
|
|
2261 answer)))
|
|
|
2262
|
|
|
2263 (defun py-statement-closes-block-p ()
|
|
|
2264 ;; true iff the current statement `closes' a block == the line
|
|
4
|
2265 ;; starts with `return', `raise', `break', `continue', and `pass'.
|
|
|
2266 ;; doesn't catch embedded statements
|
|
2
|
2267 (let ((here (point)))
|
|
|
2268 (back-to-indentation)
|
|
|
2269 (prog1
|
|
4
|
2270 (looking-at "\\(return\\|raise\\|break\\|continue\\|pass\\)\\>")
|
|
2
|
2271 (goto-char here))))
|
|
|
2272
|
|
|
2273 ;; go to point right beyond final line of block begun by the current
|
|
|
2274 ;; line. This is the same as where py-goto-beyond-final-line goes
|
|
|
2275 ;; unless we're on colon line, in which case we go to the end of the
|
|
|
2276 ;; block. assumes point is at bolp
|
|
|
2277 (defun py-goto-beyond-block ()
|
|
|
2278 (if (py-statement-opens-block-p)
|
|
|
2279 (py-mark-block nil 'just-move)
|
|
|
2280 (py-goto-beyond-final-line)))
|
|
|
2281
|
|
|
2282 ;; go to start of first statement (not blank or comment or
|
|
|
2283 ;; continuation line) at or preceding point. returns t if there is
|
|
|
2284 ;; one, else nil
|
|
|
2285 (defun py-goto-statement-at-or-above ()
|
|
|
2286 (py-goto-initial-line)
|
|
|
2287 (if (looking-at py-blank-or-comment-re)
|
|
|
2288 ;; skip back over blank & comment lines
|
|
|
2289 ;; note: will skip a blank or comment line that happens to be
|
|
|
2290 ;; a continuation line too
|
|
|
2291 (if (re-search-backward "^[ \t]*[^ \t#\n]" nil t)
|
|
|
2292 (progn (py-goto-initial-line) t)
|
|
|
2293 nil)
|
|
|
2294 t))
|
|
|
2295
|
|
|
2296 ;; go to start of first statement (not blank or comment or
|
|
|
2297 ;; continuation line) following the statement containing point returns
|
|
|
2298 ;; t if there is one, else nil
|
|
|
2299 (defun py-goto-statement-below ()
|
|
|
2300 (beginning-of-line)
|
|
|
2301 (let ((start (point)))
|
|
|
2302 (py-goto-beyond-final-line)
|
|
|
2303 (while (and
|
|
|
2304 (looking-at py-blank-or-comment-re)
|
|
|
2305 (not (eobp)))
|
|
|
2306 (forward-line 1))
|
|
|
2307 (if (eobp)
|
|
|
2308 (progn (goto-char start) nil)
|
|
|
2309 t)))
|
|
|
2310
|
|
|
2311 ;; go to start of statement, at or preceding point, starting with
|
|
|
2312 ;; keyword KEY. Skips blank lines and non-indenting comments upward
|
|
|
2313 ;; first. If that statement starts with KEY, done, else go back to
|
|
|
2314 ;; first enclosing block starting with KEY. If successful, leaves
|
|
|
2315 ;; point at the start of the KEY line & returns t. Else leaves point
|
|
|
2316 ;; at an undefined place & returns nil.
|
|
|
2317 (defun py-go-up-tree-to-keyword (key)
|
|
|
2318 ;; skip blanks and non-indenting #
|
|
|
2319 (py-goto-initial-line)
|
|
|
2320 (while (and
|
|
|
2321 (looking-at "[ \t]*\\($\\|#[^ \t\n]\\)")
|
|
|
2322 (zerop (forward-line -1))) ; go back
|
|
|
2323 nil)
|
|
|
2324 (py-goto-initial-line)
|
|
|
2325 (let* ((re (concat "[ \t]*" key "\\b"))
|
|
|
2326 (case-fold-search nil) ; let* so looking-at sees this
|
|
|
2327 (found (looking-at re))
|
|
|
2328 (dead nil))
|
|
|
2329 (while (not (or found dead))
|
|
|
2330 (condition-case nil ; in case no enclosing block
|
|
|
2331 (py-goto-block-up 'no-mark)
|
|
|
2332 (error (setq dead t)))
|
|
|
2333 (or dead (setq found (looking-at re))))
|
|
|
2334 (beginning-of-line)
|
|
|
2335 found))
|
|
|
2336
|
|
|
2337 ;; return string in buffer from start of indentation to end of line;
|
|
|
2338 ;; prefix "..." if leading whitespace was skipped
|
|
|
2339 (defun py-suck-up-leading-text ()
|
|
|
2340 (save-excursion
|
|
|
2341 (back-to-indentation)
|
|
|
2342 (concat
|
|
|
2343 (if (bolp) "" "...")
|
|
|
2344 (buffer-substring (point) (progn (end-of-line) (point))))))
|
|
|
2345
|
|
|
2346 ;; assuming point at bolp, return first keyword ([a-z]+) on the line,
|
|
|
2347 ;; as a Lisp symbol; return nil if none
|
|
|
2348 (defun py-suck-up-first-keyword ()
|
|
|
2349 (let ((case-fold-search nil))
|
|
|
2350 (if (looking-at "[ \t]*\\([a-z]+\\)\\b")
|
|
|
2351 (intern (buffer-substring (match-beginning 1) (match-end 1)))
|
|
|
2352 nil)))
|
|
|
2353
|
|
|
2354 (defun py-make-temp-name ()
|
|
|
2355 (make-temp-name
|
|
|
2356 (concat (file-name-as-directory py-temp-directory) "python")))
|
|
|
2357
|
|
|
2358 (defun py-delete-file-silently (fname)
|
|
|
2359 (condition-case nil
|
|
|
2360 (delete-file fname)
|
|
|
2361 (error nil)))
|
|
|
2362
|
|
|
2363 (defun py-kill-emacs-hook ()
|
|
|
2364 ;; delete our temp files
|
|
|
2365 (while py-file-queue
|
|
|
2366 (py-delete-file-silently (car py-file-queue))
|
|
|
2367 (setq py-file-queue (cdr py-file-queue)))
|
|
|
2368 (if (not (or py-this-is-lucid-emacs-p py-this-is-emacs-19-p))
|
|
|
2369 ;; run the hook we inherited, if any
|
|
|
2370 (and py-inherited-kill-emacs-hook
|
|
|
2371 (funcall py-inherited-kill-emacs-hook))))
|
|
|
2372
|
|
|
2373 ;; make PROCESS's buffer visible, append STRING to it, and force
|
|
|
2374 ;; display; also make shell-mode believe the user typed this string,
|
|
|
2375 ;; so that kill-output-from-shell and show-output-from-shell work
|
|
|
2376 ;; "right"
|
|
|
2377 (defun py-append-to-process-buffer (process string)
|
|
|
2378 (let ((cbuf (current-buffer))
|
|
|
2379 (pbuf (process-buffer process))
|
|
|
2380 (py-scroll-process-buffer t))
|
|
|
2381 (set-buffer pbuf)
|
|
|
2382 (goto-char (point-max))
|
|
|
2383 (move-marker (process-mark process) (point))
|
|
|
2384 (if (not (or py-this-is-emacs-19-p
|
|
|
2385 py-this-is-lucid-emacs-p))
|
|
|
2386 (move-marker last-input-start (point))) ; muck w/ shell-mode
|
|
|
2387 (funcall (process-filter process) process string)
|
|
|
2388 (if (not (or py-this-is-emacs-19-p
|
|
|
2389 py-this-is-lucid-emacs-p))
|
|
|
2390 (move-marker last-input-end (point))) ; muck w/ shell-mode
|
|
|
2391 (set-buffer cbuf))
|
|
|
2392 (sit-for 0))
|
|
|
2393
|
|
98
|
2394 ;; older Emacsen don't have this function
|
|
|
2395 (if (not (fboundp 'match-string))
|
|
|
2396 (defun match-string (n)
|
|
|
2397 (let ((beg (match-beginning n))
|
|
|
2398 (end (match-end n)))
|
|
|
2399 (if (and beg end)
|
|
|
2400 (buffer-substring beg end)
|
|
|
2401 nil))))
|
|
|
2402
|
|
4
|
2403 (defun py-current-defun ()
|
|
|
2404 ;; tell add-log.el how to find the current function/method/variable
|
|
|
2405 (save-excursion
|
|
|
2406 (if (re-search-backward py-defun-start-re nil t)
|
|
|
2407 (or (match-string 3)
|
|
|
2408 (let ((method (match-string 2)))
|
|
|
2409 (if (and (not (zerop (length (match-string 1))))
|
|
|
2410 (re-search-backward py-class-start-re nil t))
|
|
|
2411 (concat (match-string 1) "." method)
|
|
|
2412 method)))
|
|
|
2413 nil)))
|
|
2
|
2414
|
|
|
2415
|
|
102
|
2416 (defconst py-version "2.90"
|
|
2
|
2417 "`python-mode' version number.")
|
|
|
2418 (defconst py-help-address "python-mode@python.org"
|
|
|
2419 "Address accepting submission of bug reports.")
|
|
|
2420
|
|
|
2421 (defun py-version ()
|
|
|
2422 "Echo the current version of `python-mode' in the minibuffer."
|
|
|
2423 (interactive)
|
|
|
2424 (message "Using `python-mode' version %s" py-version)
|
|
|
2425 (py-keep-region-active))
|
|
|
2426
|
|
|
2427 ;; only works under Emacs 19
|
|
|
2428 ;(eval-when-compile
|
|
|
2429 ; (require 'reporter))
|
|
|
2430
|
|
|
2431 (defun py-submit-bug-report (enhancement-p)
|
|
|
2432 "Submit via mail a bug report on `python-mode'.
|
|
|
2433 With \\[universal-argument] just submit an enhancement request."
|
|
|
2434 (interactive
|
|
|
2435 (list (not (y-or-n-p
|
|
|
2436 "Is this a bug report? (hit `n' to send other comments) "))))
|
|
|
2437 (let ((reporter-prompt-for-summary-p (if enhancement-p
|
|
|
2438 "(Very) brief summary: "
|
|
|
2439 t)))
|
|
|
2440 (require 'reporter)
|
|
|
2441 (reporter-submit-bug-report
|
|
|
2442 py-help-address ;address
|
|
|
2443 (concat "python-mode " py-version) ;pkgname
|
|
|
2444 ;; varlist
|
|
|
2445 (if enhancement-p nil
|
|
|
2446 '(py-python-command
|
|
|
2447 py-indent-offset
|
|
|
2448 py-block-comment-prefix
|
|
|
2449 py-scroll-process-buffer
|
|
|
2450 py-temp-directory
|
|
|
2451 py-beep-if-tab-change))
|
|
|
2452 nil ;pre-hooks
|
|
|
2453 nil ;post-hooks
|
|
|
2454 "Dear Barry,") ;salutation
|
|
|
2455 (if enhancement-p nil
|
|
|
2456 (set-mark (point))
|
|
|
2457 (insert
|
|
|
2458 "Please replace this text with a sufficiently large code sample\n\
|
|
|
2459 and an exact recipe so that I can reproduce your problem. Failure\n\
|
|
|
2460 to do so may mean a greater delay in fixing your bug.\n\n")
|
|
|
2461 (exchange-point-and-mark)
|
|
|
2462 (py-keep-region-active))))
|
|
|
2463
|
|
|
2464
|
|
|
2465 ;; arrange to kill temp files when Emacs exists
|
|
|
2466 (if (or py-this-is-emacs-19-p py-this-is-lucid-emacs-p)
|
|
|
2467 (add-hook 'kill-emacs-hook 'py-kill-emacs-hook)
|
|
|
2468 ;; have to trust that other people are as respectful of our hook
|
|
|
2469 ;; fiddling as we are of theirs
|
|
|
2470 (if (boundp 'py-inherited-kill-emacs-hook)
|
|
|
2471 ;; we were loaded before -- trust others not to have screwed us
|
|
|
2472 ;; in the meantime (no choice, really)
|
|
|
2473 nil
|
|
|
2474 ;; else arrange for our hook to run theirs
|
|
|
2475 (setq py-inherited-kill-emacs-hook kill-emacs-hook)
|
|
|
2476 (setq kill-emacs-hook 'py-kill-emacs-hook)))
|
|
|
2477
|
|
|
2478
|
|
|
2479
|
|
|
2480 (provide 'python-mode)
|
|
|
2481 ;;; python-mode.el ends here
|
