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?
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
Is this still an issue with the latest version?
Mass re-assign of really stale bugs; xemacs herd, please verify the status and close them if these issues no longer exist.
No response from user. Please test the latest version and reopen if you still have problems.
