>>>> "Marco" == Marco Walther
<Marco.Walther(a)eng.sun.com> writes:
>>>>> "AA" == Adrian Aichner <Adrian.Aichner(a)t-online.de>
writes:
>>>> "Marco" == Marco Walther
<Marco.Walther(a)eng.sun.com> writes:
Marco> This bug report will be sent
to the XEmacs Development Team,
Marco> not to your local site managers!!
Marco> Please write in English, because the XEmacs maintainers do not have
Marco> translators to read other languages for them.
Marco> Please describe as succinctly as possible:
Marco> - What happened.
Marco> - What you thought should have happened.
Marco> - Precisely what you were doing at the time.
Marco> Please also include any C or lisp back-traces that you may have.
Marco> ================================================================
Marco> Dear Bug Team!
Marco> Adrian's new net-utils package helped to give me the correct form of
Marco> reporting this bug;-) Sorry for the duplicate.
AA> Hi Marco, it's not my package personally, just the current fixed version.
AA> Your Load-Path Lisp Shadows below make me tremble a bit.
Marco> No reason;-)
AA> In your XEmacs
AA> /export/home/marcow/gnu/emacs/lisp/ctypes
AA> is keeping XEmacs from seeing (and loading)
AA> /export/home/marcow/usr/local/lib/xemacs/xemacs-packages/lisp/c-support/ctypes
AA> etc.
Marco> This particular file/directory is not even there any more;-) But for
Marco> some of the others they where put there when the files/packages where
Marco> not yet available as XEmacs packages. (I had some newer JDE stuff in
Marco> there which had no packages etc.)
Marco> The problem I have, is that I want to update packages which are not
Marco> yet available as XEmacs packages. In the beginning I tried to manually
Marco> update the files in the package structure manually because I could not
Marco> find an easy way to get a complete package built out of a VM/JDE etc
Marco> source drop;-) But this does not work to well once I wanted to update
Marco> `everything else' with a sumo-package.
Marco> So I'm stuck with this shadowing setup:-( Yes, I should probaly clean
Marco> this up again;-)
No, you're not stuck.
This is what site-packages was conceived for:
See
http://www.xemacs.org/Documentation/21.5/html/lispref_4.html#SEC20
and
http://www.xemacs.org/Documentation/packageGuide.html#Package_hierarchies
and search for occurences of site-packages in them.
Both can be found via
http://www.xemacs.org/cgi-bin/namazu.cgi?query=site-packages&max=20&a...
Hope this helps,
Adrian
AA> Are the former files of GNU Emacs?
Marco> No. Even if the directory structure suggests otherwise;-)
AA> XEmacs byte-compiled lisp is NOT compatible with GNU Emacs
AA> byte-compiled lisp!
Marco> I know and at least one complains about the wrong bytecompile
Marco> format;-)
Marco> (I played lately with an Java speach synthesizer and emacspeak but the
Marco> test environment wanted the GNU Emacs;-)
Marco> Thanks,
Marco> -- Marco
AA> Best regards,
AA> Adrian
Marco> I was in the process of opening a (noexisting) C++ file to create a
Marco> little verification case for a bug and I got the following
Marco> backtraces:-(
Marco> * I was running VM at that time.
Marco> * Maybe it's relevant that I had connected to the running XEmacs (On
Marco> S8) using gnuclient to open another frame on a Linux box this morning?
Marco> The remote frame was already closed again but maybe some X code was
Marco> somehow confused there?
Marco> Since this is a new XEmacs process there is no other information
Marco> left:-( (Like extra packages loaded or the messages or key strokes)
Marco> Please let me know if I can help you with more information out of the
Marco> core file or anything else.
Marco> Thanks,
Marco> -- Marco
<lines deleted by Adrian>
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/