Problem loading icicles.el after my .emacs is loaded

Problem loading icicles.el after my .emacs is loaded

[Nordlöw]

Hey, there.

icicles seems to be a marvellous emacs-must-have and works very nicely
for me when I load it without first loading my .emacs. But when I do
load my .emacs first it fails and spits out this single error message
that I cannot relate to any of my previous emacs lisp knowledge:


load-with-code-conversion: Symbol's value as variable is void: Obsolete
\.


I have googled it but I could not find any pages related to my
problem.

I have also searched for the string "Obselete" in the emacs cvs
sources and in my own .emacs, extensions and configurations without
getting any hits.

What am I doing wrong? How can I trace the problem? I would really
like to get icicles working with my other emacs add-ons.


Thanks in advance,
Nordlöw

Problem loading icicles.el after my .emacs is loaded

[Nordlöw]

Hey, there.

icicles seems to be a marvellous emacs-must-have and works very nicely
for me when I load it without first loading my .emacs. But when I do
load my .emacs first it fails and spits out this single error message
that I cannot relate to any of my previous emacs lisp knowledge:


load-with-code-conversion: Symbol's value as variable is void: Obsolete
\.


I have googled it but I could not find any pages related to my
problem.

I have also searched for the string "Obselete" in the emacs cvs
sources and in my own .emacs, extensions and configurations without
getting any hits.

What am I doing wrong? How can I trace the problem? I would really
like to get icicles working with my other emacs add-ons.


Thanks in advance,
Nordlöw

RE: Problem loading icicles.el after my .emacs is loaded

[Drew Adams]

> icicles seems to be a marvellous emacs-must-have and works very nicely
> for me when I load it without first loading my .emacs. But when I do
> load my .emacs first it fails and spits out this single error message
> that I cannot relate to any of my previous emacs lisp knowledge:
>
> load-with-code-conversion: Symbol's value as variable is void: Obsolete
> \.
>
> I have googled it but I could not find any pages related to my
> problem. I have also searched for the string "Obselete" in the emacs cvs
> sources and in my own .emacs, extensions and configurations without
> getting any hits.
>
> What am I doing wrong? How can I trace the problem? I would really
> like to get icicles working with my other emacs add-ons.

I unfortunately know nothing about `load-with-code-conversion' (so far).
Perhaps someone else will be able to offer a suggestion regarding the error
message.

The first step for something like this is generally to try to find out
exactly which part of your .emacs provokes the error. To do that, use a
binary search: Comment out half of the .emacs to find which half is
problematic, then comment half of that half, and so on. Binary search is
extremely quick - in a few iterations you will have at least located what,
in combination with Icicles, is provoking the error.

Also, please always report which version of Emacs you are using. The more
info you provide (platform/OS, Icicles update #, phase of the moon...), the
better.

Re: Problem loading icicles.el after my .emacs is loaded

[Eli Zaretskii]

> From: "Drew Adams" <drew.adams@oracle.com>
> Date: Tue, 22 May 2007 06:24:04 -0700
> Cc: 
> 
> > load-with-code-conversion: Symbol's value as variable is void: Obsolete
> > \.
> [...]
> I unfortunately know nothing about `load-with-code-conversion' (so far).

It's a function defined on mule.el.  It is called (through
`load-source-file-function') by `load' when a *.el file is being
loaded.

> Perhaps someone else will be able to offer a suggestion regarding the error
> message.

The message is quite clear, but its reason is not.  Perhaps setting
debug-on-error non-nil will show some useful backtrace.

Re: Problem loading icicles.el after my .emacs is loaded

[Nordlöw]

I solved it. My fault. I thought "Obsolete" was spelled "Obselete".
That's why my grep did not find the file causing the problem. A grep
falling back to fuzzy/partial match would have discovered my
mistake...

I had an obselete emacs lisp file in my load path called pp+.el that
contained a line

Obsolete. Replaced by `+.el'.

and that icicles (optionally?) used. I removed the file and icicles
now works brilliantly!


Thanks Drew Adams!

/Nordlöw

RE: Problem loading icicles.el after my .emacs is loaded

[Drew Adams]

> I had an obselete emacs lisp file in my load path called pp+.el that
> contained a line
>
> Obsolete. Replaced by `+.el'.

That's odd.  pp+.el on Emacs Wiki is a library I wrote, but it does not
contain any such text.  pp+.el just contains some minor enhancements to
standard library pp.el.

Icicles does do a soft require of pp+.el, that is, (require 'pp+ nil t), so
that you can pick up its version of `pp-eval-expression' if you happen to
have it. There is no problem or error if you don't have pp+.el.

> and that icicles (optionally?) used.

Yes; pp+.el is optional.

> I removed the file and icicles now works brilliantly!

It should also work with pp+.el. It sounds like your pp+.el file was not the
same - http://www.emacswiki.org/cgi-bin/wiki/pp%2b.el.

Glad to hear you fixed your problem - that's the main thing.

Re: Problem loading icicles.el after my .emacs is loaded

[Tim X]

Nordlöw <per.nordlow@gmail.com> writes:

> Hey, there.
>
> icicles seems to be a marvellous emacs-must-have and works very nicely
> for me when I load it without first loading my .emacs. But when I do
> load my .emacs first it fails and spits out this single error message
> that I cannot relate to any of my previous emacs lisp knowledge:
>
>
> load-with-code-conversion: Symbol's value as variable is void: Obsolete
> \.
>
>
> I have googled it but I could not find any pages related to my
> problem.
>
> I have also searched for the string "Obselete" in the emacs cvs
> sources and in my own .emacs, extensions and configurations without
> getting any hits.
>
> What am I doing wrong? How can I trace the problem? I would really
> like to get icicles working with my other emacs add-ons.
>
>

start emacs with the command line switch --debug-init

This will give you a stack trace and a better idea of what is being called that
led to the problem.

tim


-- 
tcross (at) rapttech dot com dot au