Hi Michael,
> I'd like to globally disable the summary mode (as a workaround, as
> it seems to be to a large part responsible for the
> cpu-consumption-while-actually-idle problem). However I always have
> to disable it manually for every newly loaded buffer, as
> 'global-semantic-idle-summary-mode' doesn't seem to have any
> effect. Even though it's set correctly (as C-h v shows)
> 'semantic-idle-summary-mode' is always t after loading a file, and
> thus summary mode is always on. Also grepping through the semantic
> sources, AFAICS, 'global-semantic-idle-summary-mode' doesn't seem to
> be evaluated anywhere? Or did I do anything wrong?
That's weird, it works well for me. Did you tried to eval:
(global-semantic-idle-summary-mode -1)
and see if it actually disables the minor mode?
> Btw Eric: While being at it, regarding that
> cpu-consumption-while-actually-idle problem with XEmacs:
>
> sometime back you asked me to add
>
> (add-hook 'semantic-before-idle-scheduler-reparse-hooks
> (lambda () (message "Idle reparse...")))
>
> (add-hook 'semantic-after-idle-scheduler-reparse-hooks
> (lambda () (message "Idle reparse...done")))
>
> to see whether the idle timer is only called once, as it should
> be. And I said it is. But that was wrong, as further usage
> showed. Its just that the time between before and after is so short
> that there is only a hardly noticeable flicker:) So, to confirm
> this, the idle timer is called on and on when it should be called
> only once.
No the idle scheduler is called repeatedly through a timer after
`semantic-idle-scheduler-idle-time' seconds of idle time. It does
nothing when there is no buffer which need to be re-parsed (nothing
has been changed since its last run). This is why the time before and
after the scheduler-reparse-hooks is so short.
Hope it helps.
David

>>> "mak kwak" <makwak@...> seems to think that:
>Hallo
>This problem was known to me from semantic version 1.4.4
>Then I solved it by adding to my .emacs:
>
>(global-semantic-show-dirty-mode -1)
>(global-semantic-show-unmatched-syntax-mode -1)
>
>I've installed cedet 1.0beta3. it uses semantic 2.0beta3. while
>(global-semantic-show-unmatched-syntax-mode -1) helped with
>highlighting regions, `global-semantic-show-dirty-mode' function is no
>longer present and hence a lot of underlines still remain.
>
>Do You know a way how to dissable this feature gently.
[ ... ]
Hi,
The new install has several new functions you can call to specify
how much stuff you want enabled. Read the INSTALL file, and chances
are there is something you can use that won't require turning stuff
off since they won't be on in the first place.
Eric
--
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org

Hi
I'd like to globally disable the summary mode (as a workaround, as it seems to
be to a large part responsible for the cpu-consumption-while-actually-idle
problem). However I always have to disable it manually for every newly loaded
buffer, as 'global-semantic-idle-summary-mode' doesn't seem to have any
effect. Even though it's set correctly (as C-h v shows)
'semantic-idle-summary-mode' is always t after loading a file, and thus
summary mode is always on. Also grepping through the semantic sources,
AFAICS, 'global-semantic-idle-summary-mode' doesn't seem to be evaluated
anywhere? Or did I do anything wrong?
Btw Eric:
While being at it, regarding that cpu-consumption-while-actually-idle problem
with XEmacs:
sometime back you asked me to add
(add-hook 'semantic-before-idle-scheduler-reparse-hooks
(lambda () (message "Idle reparse...")))
(add-hook 'semantic-after-idle-scheduler-reparse-hooks
(lambda () (message "Idle reparse...done")))
to see whether the idle timer is only called once, as it should be. And I said
it is. But that was wrong, as further usage showed. Its just that the time
between before and after is so short that there is only a hardly noticeable
flicker:) So, to confirm this, the idle timer is called on and on when it
should be called only once.
Greets Michael

Hallo
This problem was known to me from semantic version 1.4.4
Then I solved it by adding to my .emacs:
(global-semantic-show-dirty-mode -1)
(global-semantic-show-unmatched-syntax-mode -1)
I've installed cedet 1.0beta3. it uses semantic 2.0beta3.
while (global-semantic-show-unmatched-syntax-mode -1) helped with highlighting regions,
`global-semantic-show-dirty-mode' function is no longer present and hence a lot of underlines still remain.
Do You know a way how to dissable this feature gently.
Greetings
----------------------------------------------------
Jesteś pracodawcą? Szukasz pracownika?
Zamieść ogłoszenie w Praca.wp.pl!
Internet to skuteczne narzędzie rekrutacyjne!
http://klik.wp.pl/?adr=http%3A%2F%2Fpraca.wp.pl%2Fzamiesc.html&sid=345

Hello, Eric.
On Thu, 31 Mar 2005 21:58:45 -0500
Eric M. Ludlam wrote:
EML> All changes, execpt the last I have checked into CVS. In the brief
EML> moments I have used it with these new changes, the functionality and
EML> behavior is vastly improved. Thanks for pointing this stuff out.
Thanks a lot! I'll try these changes out as soon as possible.
--
Regards,
Alexander Syrov.

>>> Alexander Syrov <asyrov@...> seems to think that:
[ ... ]
> EML> The function the cursor is in needs to have been successfully parsed
> EML> at least once before code completion works. Once this is the case,
> EML> you can type an opening brace and the completion engine should get a
> EML> parse-update failure, and use the old cached values, but it does need
> EML> the old cached values to exist.
>
> EML> The success of that operation tends to be a little fragile at times.
> EML> It may have also gotten broken at some point recently.
>
>Well, it seems it had indeed. After I type the opening brace, all I get is
>"Buffer not currently parsable (semantic-list)" in the minibuffer. I would
>prefer displaying summary for the function in the minibuffer. Completion
>for the arguments I type doesn't work either showing "Scan error:
>"Unbalanced parentheses".
[ ... ]
Hi,
I finally had a moment to delve into this problem.
Problem 1 is that if the idle scheduler detected that the buffer was
lexically unsafe, no services (such as the help or completion) was
run. Easy enough.
Next problem, the context parser couldn't handle the bad list
syntax. That took a bit of fiddling.
Third problem, your suggestion of showing the function help if the
arg is not completing just wasn't implemented. I added a new API to
the analyzer to provide an "interesting" tag for a given context.
Next, while I was there I discovered problems when the idle
scheduler was turned off, because buffer's that were not parseable
were never marked as such, and programs would error out. For those
interested, I added `semantic-refresh-tags-safe' to semantic.el for
use to make sure things are good to go. You can also custom-wrap your
code in `semantic-lex-catch-errors' for more detailed handling.
Next-to-last, there is a new lex option `semantic-lex-debug-analyzers' so
you can still have debug-on-error, but not geck whacked by the
idle-scheduler all the time.
Finally: I have a relativly new Emacs from CVS, and it cannot byte
compile the semantic-flex function. I may just eliminate it.
All changes, execpt the last I have checked into CVS. In the brief
moments I have used it with these new changes, the functionality and
behavior is vastly improved. Thanks for pointing this stuff out.
Eric
--
Eric Ludlam: zappo@..., eric@...
Home: http://www.ludlam.net Siege: http://www.siege-engine.com
Emacs: http://cedet.sourceforge.net GNU: http://www.gnu.org