2 Aug 2008 18:29
Re: Parse errors and smart completion in ELisp buffers
Eric M. Ludlam <eric <at> siege-engine.com>
2008-08-02 16:29:02 GMT
2008-08-02 16:29:02 GMT
>>> David <de_bb <at> arcor.de> seems to think that: >David <de_bb <at> arcor.de> writes: >> OK, this was easy enough.(Continue reading)I attached a patch for semantic-ia.el and >> semantic-el.el which works for me. > >Here's already a new one which is slightly more intelligent by looking >if the function needs any arguments. Maybe one could also print the >function arguments in the modeline, but I guess people already use eldoc >for that. The problem is that eldoc is somehow not triggered by the >completion - I always have to type another character first. Thanks for the patch. I have finally merged it into CVS. Thanks. I am not that familiar w/ how eldoc works. In theory, you can use the semantic-idle-summary-mode instead of eldoc, but eldoc has much better output. >By the way, another thing I noticed: When I want to complete a symbol >from the Gnus package, I get asked if I want to enable the Gnus >registry. It seems that somehow gnus-registry-install gets invoked by >the semantic parsing... But maybe that's more of Gnus bug (I use Gnus >from CVS)? [ ... ] Semantic will attempt put .el files into a buffer in order to parse them. Perhaps gnus files have buffer-local variables that run code in them? Eric
I attached a patch for semantic-ia.el and
>> semantic-el.el which works for me.
>
>Here's already a new one which is slightly more intelligent by looking
>if the function needs any arguments. Maybe one could also print the
>function arguments in the modeline, but I guess people already use eldoc
>for that. The problem is that eldoc is somehow not triggered by the
>completion - I always have to type another character first.
Thanks for the patch. I have finally merged it into CVS. Thanks.
I am not that familiar w/ how eldoc works. In theory, you can use the
semantic-idle-summary-mode instead of eldoc, but eldoc has much better
output.
>By the way, another thing I noticed: When I want to complete a symbol
>from the Gnus package, I get asked if I want to enable the Gnus
>registry. It seems that somehow gnus-registry-install gets invoked by
>the semantic parsing... But maybe that's more of Gnus bug (I use Gnus
>from CVS)?
[ ... ]
Semantic will attempt put .el files into a buffer in order to parse
them. Perhaps gnus files have buffer-local variables that run code in
them?
Eric
RSS Feed