That's not quite what you are asking, but if you want things to be faster
try byte-compiling. I byte compiled my JDE and it became *much* faster on
start-up.
Yaroslav
On Thu, 31 Aug 2000, Dave Zelnis wrote:
> Actually, I'm mistaken (I think) about the symptoms. I *thought* it was
> fontifying because I see the following progress bar in my minibuffer
> (shortened for clarity)
>
> Contents.java: [######################################] ... done
>
> But this doesn't appear to be font-lock's message because if I call
> "M-x font-lock-fontify-buffer" I get the following in my minibuffer:
>
> Fontifying Contents.java... (regexps.............)
>
> So what exactly is being done? I looked all over and I haven't yet
> found who is generating this message. Bovinator??
>
> Dave
>
>
>
> Wednesday, August 30, 2000, 9:29:50 AM, you wrote:
>
> > try using lazy font lock -- much faster.
>
> > -- from sample.emacs --
> > ;;; ********************
> > ;;; lazy-lock is a package which speeds up the highlighting of files
> > ;;; by doing it "on-the-fly" -- only the visible portion of the
> > ;;; buffer is fontified. The results may not always be quite as
> > ;;; accurate as using full font-lock or fast-lock, but it's *much*
> > ;;; faster. No more annoying pauses when you load files.
>
> > (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)
> > ;; I personally don't like "stealth mode" (where lazy-lock starts
> > ;; fontifying in the background if you're idle for 30 seconds)
> > ;; because it takes too long to wake up again on my piddly Sparc 1+.
> > (setq lazy-lock-stealth-time nil)
>
>
> >> -----Original Message-----
> >> From: Dave Zelnis [mailto:[EMAIL PROTECTED]]
> >> Sent: Wednesday, August 30, 2000 7:38 AM
> >> To: [EMAIL PROTECTED]
> >> Subject: font-locking and javadoc
> >>
> >>
> >> I'm using a fairly vanilla font-lock mode along with the JDE. I can
> >> insert a Javadoc comment (C-c C-v j) the *first* time no problem.
> >> However, the second time (and beyond) that I insert a Javadoc comment
> >> in that same source file, font-lock decides to re-fontify the entire
> >> buffer. This can be a pain on larger buffers on slower machines. It
> >> doesn't matter what I'm documenting (class/variable/method).
> >>
> >> If I run a macro (instead of jde-javadoc-generate-javadoc-template)
> >> that inserts some Javadoc text into the buffer at that point I don't
> >> see this behavior.
> >>
> >> Does anyone else see this? Is this a "bug" or a "feature"?
> >> Can I stop
> >> it from happening?
> >>
> >> I do NOT see this behavior running "emacs -q" so I don't
> >> think it's in my
> >> setup.
> >>
> >> Dave
> >>
> >>
> >>
> >> __________________________________________________
> >> Do You Yahoo!?
> >> Talk to your friends online with Yahoo! Messenger.
> >> http://im.yahoo.com
> >>
>
>
> try using lazy font lock -- much faster.
>
> -- from sample.emacs --
> ;;; ********************
> ;;; lazy-lock is a package which speeds up the highlighting of files
> ;;; by doing it "on-the-fly" -- only the visible portion of the
> ;;; buffer is fontified. The results may not always be quite as
> ;;; accurate as using full font-lock or fast-lock, but it's *much*
> ;;; faster. No more annoying pauses when you load files.
>
> (add-hook 'font-lock-mode-hook 'turn-on-lazy-lock)
> ;; I personally don't like "stealth mode" (where lazy-lock starts
> ;; fontifying in the background if you're idle for 30 seconds)
> ;; because it takes too long to wake up again on my piddly Sparc 1+.
> (setq lazy-lock-stealth-time nil)
>
>
> > -----Original Message-----
> > From: Dave Zelnis [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, August 30, 2000 7:38 AM
> > To: [EMAIL PROTECTED]
> > Subject: font-locking and javadoc
> >
> >
> > I'm using a fairly vanilla font-lock mode along with the JDE. I can
> > insert a Javadoc comment (C-c C-v j) the *first* time no problem.
> > However, the second time (and beyond) that I insert a Javadoc comment
> > in that same source file, font-lock decides to re-fontify the entire
> > buffer. This can be a pain on larger buffers on slower machines. It
> > doesn't matter what I'm documenting (class/variable/method).
> >
> > If I run a macro (instead of jde-javadoc-generate-javadoc-template)
> > that inserts some Javadoc text into the buffer at that point I don't
> > see this behavior.
> >
> > Does anyone else see this? Is this a "bug" or a "feature"?
> > Can I stop
> > it from happening?
> >
> > I do NOT see this behavior running "emacs -q" so I don't
> > think it's in my
> > setup.
> >
> > Dave
> >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Talk to your friends online with Yahoo! Messenger.
> > http://im.yahoo.com
> >
>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
