Bug 12228 – XEmacs records incorrect location for functions defined in dumped lisp files.

• Product: Gentoo Linux
• Status: RESOLVED TEST-REQUEST

[Description Evgeny Roubinchtein 2002-12-15 21:12:13 UTC]

With the way ebuilds build XEmacs currently, XEmacs seems to record 
incorrect locations (the build locations) for the functions defined in the 
lisp files which are dumped with XEmacs.

To reproduce:
emerge xemacs # unless already merged
C-h k C-f
C-f runs `forward-char-command'

`forward-char-command' is an interactive compiled Lisp function
  -- loaded from 
"/var/tmp/portage/xemacs-21.4.10-r1/work/xemacs-21.4.10/lisp/simple.elc"
(forward-char-command &optional ARG BUFFER)

Notice that /var/tmp/portage/xemacs/... is the build path, not the 
installation path.

Typing `f' with the point on `forward-char-command' to look up the 
function's definition produces the following message:
The library 
"/var/tmp/portage/xemacs-21.4.10-r1/work/xemacs-21.4.10/lisp/simple" is not 
in the path.

Contrast this behavior with 
C-h f efs-set-user

For this function, the recorded location is "efs-cu", and hitting the `f' 
key with the point on the function name while in the *Help...* buffer does 
take me to the definition of the function.

WIBNI I could find the source for any Elisp function, regardless of whether 
or not the file it is defined in happened to be dumped with XEmacs?

[Comment 1 Rendhalver (RETIRED) 2002-12-16 00:41:56 UTC]

this is a know problem with XEmacs
i believe it is being addressed by the XEmacs development team
i will find out what is happening with this and let you know

it is still like this in 21.4.11rc1

[Comment 2 Maurice van der Pot (RETIRED) 2005-01-08 06:46:40 UTC]

Is this still an issue with the latest version?

[Comment 3 Jakub Moc (RETIRED) 2005-07-21 15:37:03 UTC]

Mass re-assign of really stale bugs; xemacs herd, please verify the status and
close them if these issues no longer exist. 

[Comment 4 Jakub Moc (RETIRED) 2005-07-21 17:56:10 UTC]

No response from user. Please test the latest version and reopen if you still
have problems.