slime-apropos is behaving strangely on my system:
PowerBook G4 Mac OS X 10.4.6 sbcl 0.9.13 Aquamacs 0.9.9c
Here is what happens:
1. Start SLIME
M-x slime
2. Try slime-apropos on "*package*"
C-c C-d a
SLIME Apropos: *package*
3. Check % CPU activity in Activity Monitor.app: the sbcl process hovers constantly at around 85%.
It makes the fans come on :-).
slime-apropos seems to work ok with e.g. "defun".
Try it with "*default-pathname-defaults*", and it'll peg the sbcl process.
This behavior happens with both SLIME from CVS and SLIME 2.0.
Clues? Known issue? Anymore info needed...?
Thanks..
bug2splat@yahoo.com wrote:
SLIME Apropos: *package*
- Check % CPU activity in Activity Monitor.app: the sbcl process
hovers constantly at around 85%.
[...]
Clues? Known issue? Anymore info needed...?
slime-apropos does a regular expression search, try *package*. IIRC that's caused by a bug in the handling of a leading `*` or `+` in nregex.
Juho Snellman jsnell@iki.fi writes:
slime-apropos does a regular expression search, try *package*. IIRC that's caused by a bug in the handling of a leading `*` or `+` in nregex.
This is a really funny common problem in simple regexp matchers. For example "x?*" will put many of them into an infinite loop as they try to find the longest match, first with zero nothings, then one nothing, then two nothings, etc. :-)
Must remember to try entering such expressions the next time some program offers a regexp interface. :-)
Cheers, Luke