((eq class 'module)
right before the cond default branch in semantic-ectag-parse-one-tag I
obtained to have semantic-tag-folding-mode properly handled for modules.
Andrea Fedeli wrote:
> Hi there,
> I'd like to get back to a topic left sleeping for a few months:
> Semantic support for (System)Verilog.
> I'm running emacs 23.2.1 (locally installed) under Ubuntu 10.4.
> I've performed the various steps described below to see whether I may take
> advantage of exuberant ctags, before embarquing in Verilog grammar writing.
> I've installed, locally, cedet 1.0 and exuberant ctags 5.8;
> I've modified the semantic-ectag-lang.el uncommenting the
> verilog/related line ;
> I've modified my .emacs so to let emacs start with all right settings
> to cedet 1.0 and perform
> (semantic-load-enable-primary-exuberent-ctags-support) during
> With all this set, taken a simple verilog file, I've tried
> M-x bovinate
> in *Parser Output*
> CTAG: Unknown output kind module [7 times]
> in *Messages*
> I've tried to find the source of the *Messages* message, and found it
> in semantic-ectag-parse-one-tag function in semantic-ectag-parse.el.
> The message is reached as cond default branch when trying to identify
> tag type. I've run exuberant ctags myself, seeing that the produced
> ctags file contains, properly, a few lines with the word module in
> them ['module' is a verilog main keyword; the tags correspond to lines
> where module declarations start in the Verilog file].
> What do you recommend as next step? Shall I try to fiddle with
> semantic-ectag-parse-one-tag [appearing pretty 6 levels deep inside
> semantic-ectag-simple-setup call], or shall I consider a more formal
> approach? I'd also like to customize speedbar to let it behave the
> way it does in VHDL mode (e.g. hierarchy browsing) and to let folding
> act following module, block and control structures nesting; if the
> formal choice eased reaching all these targets I would already have my
> answer ;), but my cedet knowledge is not really deep enough yet to let
> me draw a yes/no myself.
> What happens now with your Lotus Notes apps - do you make another costly
> upgrade, or settle for being marooned without product support? Time to move
> off Lotus Notes and onto the cloud with Force.com, apps are easier to build,
> use, and manage than apps on traditional platforms. Sign up for the Lotus
> Notes Migration Kit to learn more. http://p.sf.net/sfu/salesforce-d2d
> Cedet-devel mailing list