Re: [Python-mode] upcoming release
Am 28.01.2011 23:09, schrieb Barry Warsaw: On Jan 28, 2011, at 10:56 PM, Andreas Röhler wrote: enabling XEmacs' handling of triple-quoted-strings fixing bugs known for now seems an interesting item from my perspective. paragraph-fill-warts branch should enable this. https://code.launchpad.net/~a-roehler/python-mode/paragraph-fill-warts It comes with a lot of utilities though, some required, some just part of the tool-box, where singling-out the required here is possible. I'm hesitating to propose that for general release, as people might be scared by the material, which is just partly python-related. OTOH, what I'm promessing: it pays. These utilities will fasten up editing, python-mode and all other. What about to release a thus experimental brunch for XEmacs users first, while it will work for all? Andreas Andreas, as always, thanks for your hard work on python-mode! It's very much appreciated. I've merged your branch and will play with it over the weekend. Hi Barry, sounds great. I'm going to leave it to Skip to verify the XEmacs compatibility issues (Skip please let us know if you need help getting Andreas's branch). python-mode.el has always been self-contained, meaning people can easily download or copy one file and get great Python support in Emacs. Requiring your utilities changes that, and can make it harder for some folks to adopt python-mode.el. Indeed, that's my concern too. I'm not saying that necessarily means it can't be done, but we do have to think about the ramifications. I'd like to get other folks thoughts on that. OTOH, I encourage you to get your code into upstream Emacs and XEmacs. That would certainly make our lives easy again. :) Do you think it would be possible and easy to pull out just the parts that python-mode.el needs and include those in that file? That can be done. OTOH it's rather hard keeping that stuff parallel. If not, then what about making sure python-mode.el gracefully degrades when those extra files aren't there? Don't see that, comment below. By that I mean, if someone does not have your new utilities, python-mode.el should at least work as well as it does currently. python-mode.el should then take advantage of your utilities if they're available. Thoughts? -Barry As it's XEmacs only, which enforced the re-write, maybe we should wait if it works there. In case it works, could extract the needed stuff to it's required minimum. Nontheless GNU Emacs won't need it, so keeping the syntax-parsing as it is for GNU Emacs users will be an option. Also in case XEmacs merges up to GNU code, the regexp-backed parser will not be needed any more. OTOH there are some gains adressed already in the second-level-command blueprint. For me the best would be maintaining for a certain time basically three branches - the classic, presently de facto GNU only - XEmacs special triple quoted string debugged, but fine for GNU Emacs also - a second-level-command enabled IDE. As this slc's will count in thousands and ten-thousands, using it needs an understandings of it's construction, i.e. of the cross-use of it's underlying lists: `ar-hide-bracketed-in-line-atpt' for example hides everything insides brackets within the given line. Resp. `ar-show-bracketed-in-line-atpt' displays it again, `ar-hide-show-bracketed-in-line-atpt' toggles this state. You have `ar-hide-bracketed-in-parentized-atpt' and so on. See the comment in `thingatpt-utils-base.el' for more. As for the latter, think we still need some time to discuss and check it's usefulness. Andreas -- https://code.launchpad.net/~a-roehler/python-mode/python-mode-components https://code.launchpad.net/s-x-emacs-werkstatt/ ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] upcoming release
Andreas Could you pull again and check? I get failures when I visit a .py file. load-path includes your version at the front: (/Users/skip/src/paragraph-fill-warts /Users/skip/emacs/sql /Users/skip/emacs/url /Users/skip/emacs /Users/skip/local/lib/xemacs/site-lisp ... /Users/skip/local/lib/xemacs-21.4.22/lisp/) and (find-library python-mode) confirms that it finds your version. When I visit a .py file I get this error though: File mode specification error: (file-error Cannot open load file: %s misc-utils) Skip ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] upcoming release
Am 29.01.2011 17:12, schrieb s...@pobox.com: Andreas Ok, so let's have it. Pushed just now. File mode specification error: (file-error Cannot open load file: %s string-strip) ehm... pushed load-path: `load-path' is a simple built-in variable. Value: (/Users/skip/src/paragraph-fill-warts ... Skip ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] upcoming release
Latest error: File mode specification error: (file-error Cannot open load file: %s sh-beg-end) Skip ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
[Python-mode] Latest error
Looks like thingatpt-utils-base requires thingatpt-highlight which doesn't exist in the checkout. I evaled all the (require) statements from the .el files in a (progn) block: (progn (require 'easymenu) (require 'ansi-color) (require 'ar-comment-lor) (require 'beg-end) (require 'cl) (require 'comint) (require 'compile) (require 'custom) (require 'info-look) (require 'misc-utils) (require 'mmm-auto) (require 'pymacs) (require 'reporter) (require 'sh-beg-end) (require 'sh-script) (require 'string-strip) (require 'thingatpt-utils-base) (require 'overlay) (require 'imenu) (require 'thing-at-point-utils) (require 'thingatpt-highlight) (require 'python-mode) ) thingatpt-highlight was the only one it complained about. Skip ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] Latest error
Am 29.01.2011 18:16, schrieb s...@pobox.com: Looks like thingatpt-utils-base requires thingatpt-highlight which doesn't exist in the checkout. I evaled all the (require) statements from the .el files in a (progn) block: (progn (require 'easymenu) (require 'ansi-color) (require 'ar-comment-lor) (require 'beg-end) (require 'cl) (require 'comint) (require 'compile) (require 'custom) (require 'info-look) (require 'misc-utils) (require 'mmm-auto) (require 'pymacs) (require 'reporter) (require 'sh-beg-end) (require 'sh-script) (require 'string-strip) (require 'thingatpt-utils-base) (require 'overlay) (require 'imenu) (require 'thing-at-point-utils) (require 'thingatpt-highlight) (require 'python-mode) ) thingatpt-highlight was the only one it complained about. Skip Hmm, seems I underestimated the issue. added and pushed. Thanks being that attentive. ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] Latest error
thingatpt-highlight was the only one it complained about. Andreas Hmm, seems I underestimated the issue. Andreas added and pushed. I'm getting farther. Looks like thingatpt-highlight was missing (when (featurep 'xemacs) (require 'overlay)) so I added that to get the make-overlay function. Then I could visit the Python file without errors. Recall the file looks like this (without the extra indentation): triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. class Foo(object): @staticmethod def bar(aList): for x in aList: for y in x: print y When I try to fill the docstring using fill-paragraph-or-region (M-q) with point ahead of the first 't', it still deletes the space ahead of the first single quotation mark, leaving me with this: triple-quoted string containingquotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. If I place point at the beginning of the last line and fill, I get this: triple-quoted string containingquotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containingquotation marks. Repeat again, and I get: triple-quoted string containingquotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containingquotation marks. triple-quoted string containingquotation marks. I can proceed to do this until I'm left with a single line in the docstring. Skip ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] Latest error
Am 29.01.2011 18:52, schrieb s...@pobox.com: thingatpt-highlight was the only one it complained about. Andreas Hmm, seems I underestimated the issue. Andreas added and pushed. I'm getting farther. Looks like thingatpt-highlight was missing (when (featurep 'xemacs) (require 'overlay)) so I added that to get the make-overlay function. Then I could visit the Python file without errors. Recall the file looks like this (without the extra indentation): triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. class Foo(object): @staticmethod def bar(aList): for x in aList: for y in x: print y When I try to fill the docstring using fill-paragraph-or-region (M-q) with point ahead of the first 't', it still deletes the space ahead of the first single quotation mark, leaving me with this: triple-quoted string containingquotation marks. which is the charateristic error of failing forward-sexp, As that form doesn't exist in new version, it means, we got the old chunk back See the error was done with revision 391 Will take some minutes to get it back. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. If I place point at the beginning of the last line and fill, I get this: triple-quoted string containingquotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containingquotation marks. Repeat again, and I get: triple-quoted string containingquotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containingquotation marks. triple-quoted string containingquotation marks. I can proceed to do this until I'm left with a single line in the docstring. Skip ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] paragraph-fill-warts branch
Andreas the old bug should be gone now. Andreas As its redone from the bottom, filling isn't correct yet. Andreas However, borders of triple-quoted-string now are recognised, Andreas `ar-bounds-of-triplequoted-atpt' should report it for example, Andreas the remaining should not be a rocky mountain. Looks much better. Goes from this: triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. to this: triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. triple-quoted string containing quotation marks. no matter where I place the cursor. Thanks, Skip ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
