Improving the Emacs OPI

[Torsten Anders]

On Feb 18, 2008, at 9:38 AM, Yves Jaradin wrote:
> Le dimanche 17 février 2008 à 10:14 +0100, Antoine Cailliau a écrit :
>> Hi,
>>
>> I'm also one of the student who would like to develop a plugin for
>> Gedit. Our goal is not to port the Emacs plugin to Gedit, with all
>> functionnalities. Our goal is more to do a plugin which will be  
>> usable
>> for everyone. We would like to keep the plugin quiet simple and
>> usable.
> If anything, I feel the Emacs plugin is too short (no intelligent code
> completion, no source outline, etc.) To be usable by everyone, a  
> plugin
> has to be usable by really everyone, including advanced users. I
> wouldn't like to have used it for let's say two years and when wanting
> to do something more complex, be told "Umh, you will have to use the
> Emacs OPI to do this."

I would highly welcome any improvements to the Emacs OPI. For  
example, I once started working on creating a TAGS file for Oz which  
would then allow for code completition etc. Unfortunately, this  
attempt got never to a stage where it really got useful.  
Nevertheless, I am posting the present shell command here (see  
below). Perhaps someone is interested to collaborate so we get this  
thing working, or someone already has even finished something related..


find $OZPATHES -name '*.oz' | xargs etags \
     --regex='/[ \t]*\(fun\|proc\)[ \t]+{\([^ \t$}]+\)/\2/' \
     --regex='/[ \t]*meth[ \t]+\([^ \t()]+\)/\1/'

Best
Torsten

--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
Office: +44-1752-233667
Private: +44-1752-558917
http://strasheela.sourceforge.net
http://www.torsten-anders.de


----------------------------