4 of 4, stripped on request.
Will send it to xemacs-review, if that's OK with Karl?
Adrian
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/
>>>>> "Ian" == Ian Walker <ian-walker(a)btconnect.com> writes:
Ian> Adrian,
Ian> Thanks for the reply. It looks like the menu is set up correctly.
Ian, please don't drop xemacs-beta off the thread.
Those guys need something to read :-)
>> Try
>> C-h k
>> then select File->Print
>>
>> This should report:
>>
>> misc-user runs `generic-print-buffer'
>> ...
>>
&…
[View More]gt;> What do you get?
>>
Ian> misc-user runs `generic-print-buffer'
Ian> `generic-print-buffer' is an interactive compiled Lisp function
Ian> -- loaded from "d:\xemacs\xemacs-21.4-release\lisp\printer.elc"
Ian> (generic-print-buffer &optional BUFFER DISPLAY-PRINT-DIALOG)
<20 lines deleted by Adrian Aichner>
Ian> Now I'm not sure if its significant, but whenever xemacs reports where
You bet.
Please use
Help->Send Bug Report...
or
M-x report-emacs-bug
as suggested in
http://www.xemacs.org/Debug/index.html
This will tell us enough about your XEmacs installation so that we
should be able to help you.
Ian, you may figure out what's wrong by looking thru that report.
Watch out for the shadows.
If you can't figure it out, send the report, including the usual
- What happened.
- What you thought should have happened.
- Precisely what you were doing at the time.
Hope this helps,
Adrian
Ian> it has loaded a lisp file from it reports the incorrect path to that
Ian> file. E.g. In above d:\xemacs\xemacs-21.4-release\lisp\printer.elc
Ian> should read
Ian> c:\Program Files\Xemacs\Xemacs-21.4.13\lisp\printer.elc
>> Also, in a buffer you would like to print (start with a simple one,
>> let *scratch*), try:
>> M-x generic-print-buffer
>>
>>
Ian> I get exactly same behaviour, dialogue pops up, I click 'print', I get
Ian> the same error message.
Ian> Regards, Ian
--
Adrian Aichner
mailto:adrian@xemacs.org
http://www.xemacs.org/
[View Less]
I expand x-symbol-1.03-pkg.tar.gz and failed to complain:
% tar vzxf /usr/ports/distfiles/xemacs/x-symbol-1.03-pkg.tar.gz
pkginfo/MANIFEST.x-symbol
lisp/x-symbol/ChangeLog
lisp/x-symbol/ChangeLog.2.upstream
(snip)
etc/x-symbol/pcf/xsymb1_12sup.pcf
etc/x-symbol/pcf/xsymb1_14.pcf
etc/x-symbol/pcf/xsymb1_14sub.pcf
etc/x-symbol/pcf/xsymb1_14sup.pcf
etc/../man/x-symbol/.ispell_xsymb
tar: etc/../man/x-symbol/.ispell_xsymb: Member name contains `..'
etc/../man/x-symbol/Makefile.upstream
tar: etc/../…
[View More]man/x-symbol/Makefile.upstream: Member name contains `..'
etc/../man/x-symbol/x-symbol.css
tar: etc/../man/x-symbol/x-symbol.css: Member name contains `..'
etc/../man/x-symbol/x-symbol.init
tar: etc/../man/x-symbol/x-symbol.init: Member name contains `..'
tar: Error exit delayed from previous errors
Is that miss-archived?
[View Less]
Hi!
Since approximately last weekend (sorry, can't nail it done closer) I
see an error in Gnus v5.10.3 independent of the XEmacs version, 21.4.13
or 21.5-b13.
I've asked on the Gnus mailing list
,----
| > Signaling: (void-variable to-address)
| > gnus-post-news(nil "nnml:xemacs-winnt" [73 "Re: \"packages/sasl-1.12-pkg.tar.gz too short\" " "Darryl Okahata <darrylo(a)soco.agilent.com>" "Wed, 28 May 2003 16:58:33 -0700" "<200305282358.QAA01059(a)mina.soco.agilent.com>" "<…
[View More]vz4r3ergtj.fsf(a)viteno.dyns.net>" 600 18 "viteno.dyns.net xemacs-winnt:73" ((To . "Norbert Koch <viteno(a)xemacs.org>"))] "*Article*" (73) nil nil)
| > gnus-summary-followup((73) nil)
| > gnus-summary-followup-with-original(nil)
| > call-interactively(gnus-summary-followup-with-original)
| >
| > which I don't really understand, because to my watering eyes
| > to-address is bound in gnus-post-news.
|
| But it gets unbound by (gnus-msg.el, rev 6.135, line 947):
|
| (set-buffer gnus-article-copy)
`----
and got the following answer from Dave Love:
,----
| I haven't checked the code, but if I understand correctly, that's
| expected if XEmacs doesn't have rms and gerd's changes to the binding
| mechanism for buffer-local variables. See Info `(elisp)Intro to
| Buffer-Local' in Emacs, though I think that text is obsolete in Emacs
| 21.
`----
Has anything changed recently which might trigger this behaviour?
Thanks,
norbert.
[View Less]