From noreply at sourceforge.net Wed May 4 02:44:39 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 03 May 2005 17:44:39 -0700 Subject: [Python-mode] [ python-mode-Patches-1194875 ] better (and more) coloring Message-ID: Patches item #1194875, was opened at 2005-05-04 02:44 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581351&aid=1194875&group_id=86916 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jonas K?lker (jonaskoelker) Assigned to: Nobody/Anonymous (nobody) Summary: better (and more) coloring Initial Comment: this patch fixes some coloring problems. It's made against 4.70 (I diffed the CVS version against my debian/sarge python-mode.el: equal) --- fixed stuff try:pass colors everything except the : (same for except and finally) they still color the colon turquoise if there's at least one space or newline. If colon-coloring should be turned off, it's a simple swap-three-lines operation. it also correctly colors str(id(type(len))); but only (damn!) because it alternates between typenames and builtins. fixes not coloring the last exception in a tuple (and probably other similar things). (imo) correctly colors ValueError in `exceptions.ValueError'. adds set and frozenset to typenames. --- tweakable stuff: selecting alternate face for typenames (int, dict, type) selecting alternate face for builtins (exceptions, len, id) (these two defaults to kw-turquoise) selecting alternate face for numeric literals (but currently the RE-matching is dodgy) selecting alternate face for the first variable name in a for ... in (both expressions and statements) (it should be extended to more than just the first). (these two default to a vanilla face, 'py-plain-face) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581351&aid=1194875&group_id=86916 From noreply at sourceforge.net Wed May 4 02:46:44 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 03 May 2005 17:46:44 -0700 Subject: [Python-mode] [ python-mode-Patches-1194875 ] better (and more) coloring Message-ID: Patches item #1194875, was opened at 2005-05-04 02:44 Message generated for change (Comment added) made by jonaskoelker You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581351&aid=1194875&group_id=86916 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Jonas K?lker (jonaskoelker) Assigned to: Nobody/Anonymous (nobody) Summary: better (and more) coloring Initial Comment: this patch fixes some coloring problems. It's made against 4.70 (I diffed the CVS version against my debian/sarge python-mode.el: equal) --- fixed stuff try:pass colors everything except the : (same for except and finally) they still color the colon turquoise if there's at least one space or newline. If colon-coloring should be turned off, it's a simple swap-three-lines operation. it also correctly colors str(id(type(len))); but only (damn!) because it alternates between typenames and builtins. fixes not coloring the last exception in a tuple (and probably other similar things). (imo) correctly colors ValueError in `exceptions.ValueError'. adds set and frozenset to typenames. --- tweakable stuff: selecting alternate face for typenames (int, dict, type) selecting alternate face for builtins (exceptions, len, id) (these two defaults to kw-turquoise) selecting alternate face for numeric literals (but currently the RE-matching is dodgy) selecting alternate face for the first variable name in a for ... in (both expressions and statements) (it should be extended to more than just the first). (these two default to a vanilla face, 'py-plain-face) ---------------------------------------------------------------------- >Comment By: Jonas K?lker (jonaskoelker) Date: 2005-05-04 02:46 Message: Logged In: YES user_id=1153395 sorry, I (something)ed up uploading the patch. Scene 24, take 2. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581351&aid=1194875&group_id=86916 From noreply at sourceforge.net Sun May 15 01:39:24 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 14 May 2005 16:39:24 -0700 Subject: [Python-mode] [ python-mode-Bugs-1202144 ] Uncommenting incomplete on xemacs beta Message-ID: Bugs item #1202144, was opened at 2005-05-14 16:39 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581349&aid=1202144&group_id=86916 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: David M. Cook (daverz) Assigned to: Nobody/Anonymous (nobody) Summary: Uncommenting incomplete on xemacs beta Initial Comment: This looks a new xemacs bug or feature, but the xemacs beta (21.5.20 currently) puts an extra space after the '##' so that uncommenting still leaves '# ' at the beginning of lines. Tested with py-version 4.52 and 4.63. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581349&aid=1202144&group_id=86916 From noreply at sourceforge.net Fri May 27 02:52:10 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 26 May 2005 17:52:10 -0700 Subject: [Python-mode] [ python-mode-Bugs-1180180 ] Proposed improvement for pycomplete Message-ID: Bugs item #1180180, was opened at 2005-04-10 09:33 Message generated for change (Comment added) made by errebepe You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581349&aid=1180180&group_id=86916 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Hugo Haas (hugoh) Assigned to: Nobody/Anonymous (nobody) Summary: Proposed improvement for pycomplete Initial Comment: Hi. I really like the idea of pycomplete a lot. However, it only completes simple cases: "sys.cl" becomes "sys.clock" once completed. What would be interesting would be to get a list of completions for "sys.". I believe that what needs to be changed is the following: - have pycomplete.py return a list of all possibilities - in py-complete() in pycomplete.el, use the output of pycomplete.py to call try-completion; if it works, use it, if not and there are several possibilities, display all the possibilities given by all-completions and allow to chose between them. The former is trivial (patch attached). I tried to do the latter, but my lack of knowledge in elisp put a rapid stop to it, so in case somebody knows elisp and is interested by this (I think it would be a cool feature), I thought I'd record the idea here. Regards, Hugo ---------------------------------------------------------------------- Comment By: Rodrigo Bernardo Pimentel (errebepe) Date: 2005-05-26 21:52 Message: Logged In: YES user_id=374783 I've implemented these suggestions and put the resulting files at http://isnomore.net/prog/pycomplete/ . Please take a look and let me know what you (all) think. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581349&aid=1180180&group_id=86916 From noreply at sourceforge.net Tue May 31 02:08:36 2005 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 30 May 2005 17:08:36 -0700 Subject: [Python-mode] [ python-mode-Bugs-813266 ] better indentation for lambda bodies Message-ID: Bugs item #813266, was opened at 2003-09-26 15:37 Message generated for change (Comment added) made by montanaro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581349&aid=813266&group_id=86916 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Matthias Klose (doko) >Assigned to: Nobody/Anonymous (nobody) Summary: better indentation for lambda bodies Initial Comment: [forwarded from http://bugs.debian.org/208303] Currently, if you place the body of a lambda on the next line (to curb rightward drift), the Emacs Python mode indents it like this: ... lambda x: body_of_lambda() ... In keeping with Lisp traditions, and to improve readability, I suggest a small amount of indentation for the lambda body, eg: lambda x: body_of_lambda() or lambda x: body_of_lambda() ---------------------------------------------------------------------- >Comment By: Skip Montanaro (montanaro) Date: 2005-05-30 19:08 Message: Logged In: YES user_id=44345 Matthias, I'm sympathetic to your plight, but the code that's responsible for computing indentation is already too complex and my lisp-fu isn't sufficient for the problem. Unassigning in case some other intrepid Lisp cowboy wants to tackle this. ---------------------------------------------------------------------- Comment By: Matthias Klose (doko) Date: 2004-03-28 08:21 Message: Logged In: YES user_id=60903 The bug submitter responded in the original report: It looks like there's some indentation now, which is certainly an improvement, but it's relative to the entire statement, so (eg) function_with_callback(1, 2, 3, lambda args: body_of_the_lambda) He prefers: function_with_callback(1, 2, 3, lambda args: body_of_the_lambda) so that the lambda body is visually attached to the lambda. ---------------------------------------------------------------------- Comment By: Skip Montanaro (montanaro) Date: 2003-12-19 09:19 Message: Logged In: YES user_id=44345 Matthias, is this still a problem for you? In XEmacs, I get a four-space indent if I end the line with "lambda:" and hit the TAB key on the next line. (Please check with the latest version. It's accumulated several changes in the past day.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=581349&aid=813266&group_id=86916