Re: debugging "Lisp nesting exceeds max-lisp-eval-dept" error??

[Kim F. Storm]

Jason Rumney <address@hidden> writes:

>> We don't normally delete packages that are obsolete, we normally put
>> them in the `obsolete' directory.  Is there a reason to treat these
>> differently?
>
> If we alias their main functions to a function from a non-obsolete
> package, we are treating them differently from the other packages in
> obsolete.

If people really want to use, e.g. fast-lock-mode, they just need
to load fast-lock explicitly to get the original non-aliased
functions back ...

-- 
Kim F. Storm <address@hidden> http://www.cua.dk