*slime-inspector* [set value] and current package not in synch

Bug #728576 reported by mon_key
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Slime
New
Undecided
Unassigned

Bug Description

From the *slime-inspector* window, with the *slime-inspector* as
current-buffer when I evaluate the elisp form:
 (slime-interactive-eval *package*)
the return value is a package descriptor for PKG-A.

When inspecting a class instance INSTANCE-I interned in package PKG-A I'm
given the option of setting the slot value for SLOT-S of INSTANCE-I.

This option is presented as a button "[set value]" in the *slime-inspector*.
The elisp command `slime-inspector-operate-on-point' is attached to the button.

SLOT-S of INSTANCE-I has neither :reader :writer nor :accessor methods,
e.g. it its spec is:
 (slot-s :initarg slot-s :initform nil)

When attempting to set SLOT-S of INSTANCE-I from *slime-inspector* to the
value of a defvar'd variable PKG-A:VAR-V interned in package PKG-A as VAR-V, I
get the warning that:

 "The variable COMMON-LISP-USER::<VAR-V> is unbound."

If instead I set the slot value to the value of PKG-A:VAR-V it works fine.

When invoking the "[set value]" action from the *slime-inspector* buffer why
does it not recognize that the current package is PKG-A and not
COMMON-LISP-USER?

Description pasted here as well: http://paste.lisp.org/+2KQ5

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.