"J. K. Cunningham" <J.k.cunningham@...> writes:
> I miss the old behavior - particularly as very often the name
> conflicts are caused by including a package I had forgotten, so that
> one of the "packages" is the interned function name which doesn't even
> exist (i.e., there is no real conflict).
Yes, I miss it too. It seems there are some hairy issues with packages,
hash tables, and threads. IIRC, they are supposed to be resolved at some
> If so, short of killing the *inferior-lisp* instance and restarting
> the whole thing, how might one proceed once a name conflict is
> encountered. FMAKUNBOUND doesn't fix anything.
(unintern 'symbol :package)