After spending the whole day tracking down some problems I was having
with Gnus (Oort, not the XEmacs package one), I stumbled across a
problem in comint.el.
Byte-compiling comint.el reports that the function
'comint-extract-current-pathname' isn't defined. A grep through my
XEmacs sources (21.1, 21.4, 21.5 core and packages) reveals that the
only place 'comint-extract-current-pathname' exists is in comint.el.
Here's the relevant doc string from comint.el, it explains it better
than I could:
,----[ from 'comint-find-source-code' in comint.el ]
| Search backward from point for a source location.
| If a source location is found in the current line,
| go to that location.
| If MULTI-LINE is false (this is the interactive prefix flag),
| then only look for source locations in the current line.
| Otherwise, look within comint-find-source-code-max-lines
| before point. If a source location is found on a previous line, move
| point to that location, so that another use of \\[comint-find-source-code\\]
| will go to the indicated place.
| If no source location is found, then try to extract a filename
| around the point, using comint-extract-current-pathname.
| In any case, if the file does not exist, prompt the user for
| a pathname that does. Sometimes the file's directory needs
| hand adjustment.
| This command uses comint-extract-source-location, which is customizable.
| Also, once a source file and line have been extracted, it uses
| comint-find-source-file-hook and comint-goto-source-line-hook
| to interpret them.
It'd be great if someone could take a look at this and maybe write a
'comint-extract-current-pathname' function that does what the doc
string says it does.
|---<Steve Youngs>---------------<GnuPG KeyID: 9E7E2820>---|
| XEmacs - It's not just an editor. |
| It's a way of life. |