[Python-mode] highlight bug?
Before I wasn't sure if it was an old bug, but today I got the last revision from bzr and I see the same. Function and variable names containing reserved keywords are not highlighted correctly. For example in def generate_random_tuple() tuple is colored as it was the tuple function call... Anyone else seeing this? By the way I've seen many comments about it but I never really understood, why this python-mode is not included in emacs instead of the crappy default one? ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] highlight bug?
On Feb 25, 2011, at 12:18 PM, andrea crotti wrote: Before I wasn't sure if it was an old bug, but today I got the last revision from bzr and I see the same. Function and variable names containing reserved keywords are not highlighted correctly. For example in def generate_random_tuple() tuple is colored as it was the tuple function call... Anyone else seeing this? Not me. With r396 of python-mode.el I see this highlighting correctly. Cheers, -Barry signature.asc Description: PGP signature ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] highlight bug?
Am 25.02.2011 13:32, schrieb andrea crotti: Ok first I need to be sure I'm up to date. I'm at revision 396, and also here https://code.launchpad.net/~python-mode-devs/+ownedbranches I see the same as last commit done... Are there any more advanced branches? usually I start here: https://code.launchpad.net/python-mode BTW my components branch is still heavily changed, major changes underway... Have a look at the thing-at-point utils stuff nonetheless, for me it's a rocket~~~:=== For python-mode/python.el good to know, as long as it's sharing and helping and not fighting is not a problem... ___ Python-mode mailing list Python-mode@python.org http://mail.python.org/mailman/listinfo/python-mode
Re: [Python-mode] highlight bug?
Am 25.02.2011 16:30, schrieb andrea crotti: 2011/2/25 Andreas Röhlerandreas.roeh...@online.de: usually I start here: https://code.launchpad.net/python-mode BTW my components branch is still heavily changed, major changes underway... Have a look at the thing-at-point utils stuff nonetheless, for me it's a rocket~~~:=== For python-mode/python.el good to know, as long as it's sharing and helping and not fighting is not a problem... Oh God I found the problem, I think probably after the last update of cedet I have this not so funny behaviour When emacs starts I get this: python-mode is an interactive compiled Lisp function in `python-mode.el'. After I open the first python file it becomes: python-mode is an interactive compiled Lisp function in `python.el'. (python-mode) So I'm just using the wrong thing but I didn't notice because locate-library also gave me the right file. Any way to solve this conflict once for all? Using some function to toggle several branches/modes like this (set-buffer (get-buffer-create test.py)) (erase-buffer) (when (featurep 'python-mode)(unload-feature 'python-mode t)) (fundamental-mode) (setq py-python-command-args '(-colors Linux)) (add-to-list 'load-path NEW-PATH... then load some python-stuff into, call python-mode again. HTH 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
