[Python-mode] highlight bug?

[Andreas Röhler]

Am 25.02.2011 16:30, schrieb andrea crotti:
> 2011/2/25 Andreas Röhler<andreas.roehler at 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/