Re: [Python-mode] one more myrkwid bug
Am 16.04.2011 13:01, schrieb Georg Brandl: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 15.04.2011 23:41, schrieb Andreas Röhler: Am 15.04.2011 22:24, schrieb Barry Warsaw: On Apr 15, 2011, at 10:28 PM, Andreas Röhler wrote: Am 15.04.2011 22:09, schrieb Barry Warsaw: On Apr 15, 2011, at 10:01 PM, Andreas Röhler wrote: checked in the fix meanwhile. Behavior of trunk now default again. I just grabbed the update and it looks good. Thanks, I'll use this version over the weekend. As for the new variable, would prefer a pure boolean for simplicity. Maybe `py-indent-honor-listing' docstring already tells what's in question? So would t or nil give the default behavior? Nil - it's negligent now, doesn't care for listing... How about then, calling it py-indent-honor-open-paren? Also good. But let's reflect maybe a little further: point for me is not just the open paren, but the multiline-form it introduces. Open paren followed by a closing same line are not of interest here. Therefore the `listing', which doesn't express that sufficiently either. FWIW, I would have no idea at all what py-indent-honor-listing does if I just saw the name. Georg what about `py-indent-honor-multiline-listing' ? Cheers Andreas ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] one more myrkwid bug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 16.04.2011 09:42, schrieb Andreas Röhler: Am 16.04.2011 13:01, schrieb Georg Brandl: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am 15.04.2011 23:41, schrieb Andreas Röhler: Am 15.04.2011 22:24, schrieb Barry Warsaw: On Apr 15, 2011, at 10:28 PM, Andreas Röhler wrote: Am 15.04.2011 22:09, schrieb Barry Warsaw: On Apr 15, 2011, at 10:01 PM, Andreas Röhler wrote: checked in the fix meanwhile. Behavior of trunk now default again. I just grabbed the update and it looks good. Thanks, I'll use this version over the weekend. As for the new variable, would prefer a pure boolean for simplicity. Maybe `py-indent-honor-listing' docstring already tells what's in question? So would t or nil give the default behavior? Nil - it's negligent now, doesn't care for listing... How about then, calling it py-indent-honor-open-paren? Also good. But let's reflect maybe a little further: point for me is not just the open paren, but the multiline-form it introduces. Open paren followed by a closing same line are not of interest here. Therefore the `listing', which doesn't express that sufficiently either. FWIW, I would have no idea at all what py-indent-honor-listing does if I just saw the name. Georg what about `py-indent-honor-multiline-listing' ? I think the listing is the strange word here. For me, a listing is a snippet of code printed in a book. Georg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk2poQYACgkQN9GcIYhpnLDchACfQ/UvFKHyR87MVovONm3n/e3d V6AAnR+h4X8iYYp6e7ATWNt7Tmg7JoQ0 =n/q/ -END PGP SIGNATURE- ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
[Python-mode] xemacs or Python mode
(I originally sent this to the xemacs list and forgot to send it here) Only Your friendly list mates can tell for sure In some buffers of Python code and not others when I press the backspace key, it tells me: symbols function definition is void: looking-back. I'm testing out on the latest branches of Python-mode and I'm trying to figure out if this is something I'm doing wrong with xemacs or it is a bug. What do I need to do to debug this? --- eric ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] xemacs or Python mode
Am 16.04.2011 18:11, schrieb Eric S. Johansson: (I originally sent this to the xemacs list and forgot to send it here) Only Your friendly list mates can tell for sure In some buffers of Python code and not others when I press the backspace key, it tells me: symbols function definition is void: looking-back. I'm testing out on the latest branches of Python-mode and I'm trying to figure out if this is something I'm doing wrong with xemacs or it is a bug. What do I need to do to debug this? --- eric ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode XEmacs should implement it. Here it is for the moment: (when (featurep 'xemacs) (unless (functionp 'looking-back) ;; from GNU Emacs subr.el (defun looking-back (regexp optional limit greedy) Return non-nil if text before point matches regular expression REGEXP. Like `looking-at' except matches before point, and is slower. LIMIT if non-nil speeds up the search by specifying a minimum starting position, to avoid checking matches that would start before LIMIT. If GREEDY is non-nil, extend the match backwards as far as possible, stopping when a single additional previous character cannot be part of a match for REGEXP. (let ((start (point)) (pos (save-excursion (and (re-search-backward (concat \\(?: regexp \\)\\=) limit t) (point) (if (and greedy pos) (save-restriction (narrow-to-region (point-min) start) (while (and ( pos (point-min)) (save-excursion (goto-char pos) (backward-char 1) (looking-at (concat \\(?: regexp \\)\\' (setq pos (1- pos))) (save-excursion (goto-char pos) (looking-at (concat \\(?: regexp \\)\\') (not (null pos)) ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] xemacs or Python mode
Am 16.04.2011 21:44, schrieb Eric S. Johansson: On 4/16/2011 1:31 PM, Andreas Röhler wrote: Am 16.04.2011 18:11, schrieb Eric S. Johansson: XEmacs should implement it. it should but I'm getting the exception. Here it is for the moment: hmm could not find this code in the myrkid branch. Do another `bzr pull' to get it. Just pushed it up. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
