Large verilog file editing with EMACS

Large verilog file editing with EMACS

[SENTHIL S]

Hello,

The Emacs editor hangs when browsing thru large
verilog
files say 40,000 lines.I saw thru the known bugs and
found the below ... But it doesnt help .. 

Plz HELP me out with a solution .. 

The version is 21.2 and the machine UltraSPARC-IIIi
OS - SUN5.9

Thanks
Regards
Senthil.s.

========================================

* Font Lock displays portions of the bufefr in
incorrect faces.

By far the most frequent cause of this is a
parenthesis `(' or a brace
`{' in column zero.  Font Lock assumes that such a
paren is outside of
any comment or string.  This is of course not true in
general, but the
vast majority of well-formatted program source files
don't have such
parens, and therefore this assumption is used to allow
optimizations
in Font Lock's syntactical analysis.  These
optimizations avoid some
patological cases where jit-lock, the Just-in-Time
fontification
introduced with Emacs 21.1, could significantly slow
down scrolling
through the buffer, especially scrolling backwards,
and also jumping
to the end of a very large buffer.

If you don't use large buffers, or have a very fast
machine which
makes the delays insignificant, you can avoid the
incorrect
fontification by setting the variable
`font-lock-beginning-of-syntax-function' to a nil
value.  (This must
be done _after_ turning on Font Lock.)

====================================
Even JESUS is criticized
and Buddha is criticized
but noone criticizes himself !!


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Easier than ever with enhanced search. Learn more. 
http://info.mail.yahoo.com/mail_250

Re: Large verilog file editing with EMACS

[Stefan Monnier]

> The Emacs editor hangs when browsing thru large verilog files
> say 40,000 lines.

Can you be more specific?

Try it with "emacs -q" first.  If the problem disappears, then try and see
which part of your .emacs triggers the problem.

Then when Emacs seems to hang, does C-g interrupt it?  If yes, set
Options -> Enter Debugger on Quit/C-g, try again, and post the (hopefully)
resulting backtrace.
If C-g doesn't help, then run your Emacs under a debugger (like gdb)
and when Emacs hangs, interrupt it in the debugger and look at
the backtrace.  My wild guess in that case is that it's stuck in
a looooonnnng regexp-match.  You can figure out which regexp by going up the
stack and inspecting the "regexp" argument (using the `xstring' command
if you're under gdb).


        Stefan