Re: [CEDET-devel] [PDEE] CEDET integration with python.el, python-mode.el, et al?
Brought to you by:
zappo
From: Tom R. <Tom...@po...> - 2010-03-17 02:22:37
|
OK, so it sounds like the todo-list is as follows (please let me know if I'm missing or misconstruing anything): 0 Check the syntax tables for python*el. Eric M. Ludlam Tue, 16 Mar 2010 19:16:56 -0400 (rearranged) > [mode requirements are] a hook [and] a good syntax table Probably identical, but > If there are differences between syntax tables, this can be overcome > easily in the CEDET python support with a lexical table > modifications feature. 1 Configure CEDET for use with each python*el. > a simple (load "~/cedet/common/cedet.el") does all the setup. Another aside: another reason to leverage CEDET is that it's an ubuntu package (err, 2). For future doc you might want to note the appropriate stanza for that kind of installation. For my {ubuntu=karmic, packages=emacs-snapshot, cedet-common, cedet-contrib} me@it:~$ for TLD in "etc" "opt" "usr" "var" ; do > echo -e "/${TLD}:" > find "/${TLD}" -type d | fgrep -ie 'cedet' > echo > done ... /usr/share/emacs-snapshot/site-lisp/cedet-common /usr/share/emacs-snapshot/site-lisp/cedet-contrib /usr/share/doc/cedet-common /usr/share/doc/cedet-contrib /usr/share/emacs/site-lisp/cedet-common /usr/share/emacs/site-lisp/cedet-common/icons /usr/share/emacs/site-lisp/cedet-contrib tlroche@tlrPanP5:~$ for D in "doc" "emacs" "emacs-snapshot" ; do > TLD="/usr/share/${D}" > echo -e "${TLD}:" > find "${TLD}" -type f -name 'cedet.el' > echo > done ... /usr/share/emacs/site-lisp/cedet-common/cedet.el it's apparently http://cedet.sourceforge.net/setup.shtml (slightly modified) >> (load-file "/usr/share/emacs/site-lisp/cedet-common/cedet.el") >> (global-ede-mode 1) ; project management system >> (semantic-load-enable-code-helpers) ; prototypes, smart completion >> (global-srecode-minor-mode 1) ; template insertion menu No? Start simpler? 2 Vet the parser with each python*.el: > The base language support does do smart completion if the parser > provides the right kinds of tags. Someone just needs to try it out > for a while, and work out the kinks to claim that this is well > supported. So is there a more systematic way to check? Testcases? Otherwise, just run with it and bug-report this list. 3 Try the provided auto-complete UI. I prefer push mode, so, presuming this is invokable from the init file rather than the minibuffer, in python-mode-hook (which both python*el define) put http://cedet.sourceforge.net/intellisense.shtml (slightly modified) >> (semantic-complete-analyze-inline) >> This is a command that does completion inline (underlining the >> target symbol) and allows TAB to be used for completion purposes. 4 Release changes (if any). > You will need to provide a release for any changes so that they can > eventually be made a part of Emacs. NP. How is this done? (I'd also like to know because something is very weird about the python-mode.el copyright-assignment situation.) Your assistance is appreciated, Tom Roche <Tom...@po...> |