* ERROR AGAIN !!
@ 1999-11-12 13:36 Pieter Wenk
1999-11-15 19:15 ` Lars Magne Ingebrigtsen
1999-11-15 23:06 ` ERROR AGAIN !! Jan Vroonhof
0 siblings, 2 replies; 22+ messages in thread
From: Pieter Wenk @ 1999-11-12 13:36 UTC (permalink / raw)
Hello to all:
Obviously, something is wrong. Either with my .gnus or xemacs.
Or naturally both.
For two subsribed groups I am getting now:
p.wenk@sre-4-139:~ > xemacs -q
Fatal error (11).
Your files have been auto-saved.
Use `M-x recover-session' to recover them.
Please report this bug by running the send-pr script included
with XEmacs, or selecting `Send Bug Report' from the help menu.
As a last resort send ordinary email to `crashes@xemacs.org'.
*MAKE SURE* to include as much configuration information as
possible; at the very least what OS and hardware you are running
on, and hopefully also what compiler and compiler options the
binary was compiled with, what options XEmacs was compiled with,
whether you are using a prebuilt binary from ftp.xemacs.org or
compiled XEmacs yourself for your system, etc.
If at all possible, *please* try to obtain a C stack backtrace;
it will help us immensely in determining what went wrong.
To do this, locate the core file that was produced as a result
of this crash (it's usually called `core' and is located in the
directory in which you started XEmacs, or maybe in your home
directory), and type
gdb /usr/X11R6/bin/xemacs core
then type `where' when the debugger prompt comes up.
\x01\x01
Lisp backtrace follows:
# (unwind-protect ...)
insert-file-contents-internal("/home/p.wenk/News/" nil nil nil nil undecided used-codesys)
byte-code("ÀÁ\n
#ˆ
®‘ÅÆ\n
#®ŠÇ\n!®®É‰\\x0f:«†\\x0f
ªŸÌ\\x0f!¬‰ÍÎ\\x0f\"ˆÏ\\x0fÐ\\x0f
\\x0fÔ&
À‡" [\x13\x16\x0f- \x10\x10\f-\x18
\x15 -\x02\x13\b\x14
\x0f\x14\x06\x13\x15-\a
\r\x06-\x04\x10\x0f\x15\x06\x0f\x15\x14-\x02\x04\x04\x06\x14\x14- \x10\x10\f \a
\r\x06\x0f\x02\x0e\x06 \x17
\x14
\x15 \x04\x10\x05
\x0f\b-\x14\x1a\x14\x15\x06\x0e-\a\x10\x13-\x13\x06\x02\x05 \x13\x16\x0f-\x14\x11\x06\x04
\x02\r- \x10\x10\f-\x18
\x15 -\x02\x13\b\x14
\x0f\x14\x06\x13\x15-\a
\r\x06-\x04\x10\x0f\x15\x06\x0f\x15\x14-\x11\x13\x06- \x10\x10\f \a
\x0f\x05-\a
\r\x06-\x04\x10\x05
\x0f\b-\x14\x1a\x14\x15\x06\x0e-\a\x10\x13-\x13\x06\x02\x05-\a\x13\x10\x0e-\a
\r\x06\x0f\x02\x0e\x06 \x03\x16\a\a\x06\x13-\a
\r\x06-\x04\x10\x05
\x0f\b-\x14\x1a\x14\x15\x06\x0e-\a\x10\x13-\x13\x06\x02\x05 \x0f\x10-\x04\x10\x0f\x17\x06\x13\x14
\x10\x0f \x04\x10\x05
\x0f\b-\x14\x1a\x14\x15\x06\x0e \x13\x06\x15\x16\x13\x0f-\x17\x02\r \a
\x0f\x05-\x04\x10\x05
\x0f\b-\x14\x1a\x14\x15\x06\x0e \x0e\x06\x14\x14\x02\b\x06 "I\x0f\x17\x02
\x05 \x04\x10\x05
\x0f\b-\x14\x1a\x14\x15\x06\x0e (%\x14), \x16\x14
\x0f\b '\x16\x0f\x05\x06\x04
\x05\x06\x05" \x16\x0f\x05\x06\x04
\x05\x06\x05
\x0f\x14\x06\x13\x15-\a
\r\x06-\x04\x10\x0f\x15\x06\x0f\x15\x14-
\x0f\x15\x06\x13\x0f\x02\r \x03\x06\b \x06\x0f\x05 \x13\x06\x11\r\x02\x04\x06 \x16\x14\x06\x05-\x04\x10\x05\x06\x14\x1a\x14] 9)
# (\x04\x10\x0f\x05
\x15
\x10\x0f-\x04\x02\x14\x06 ... . ((\a
\r\x06-\x06\x13\x13\x10\x13 (\x03\x1a\x15\x06-\x04\x10\x05\x06 "ÀÁ\\x0f
$ˆÅ
@
A\"‡" ... 5))))
# \x03
\x0f\x05 (\x13\x06\x15\x16\x13\x0f-\x17\x02\r \x04\x10\x05
\x0f\b-\x14\x1a\x14\x15\x06\x0e \x16\x14\x06\x05-\x04\x10\x05\x06\x14\x1a\x14 \x04\x10\x0f\x17\x06\x13\x14
\x10\x0f-\a\x16\x0f\x04 \x13\x06\x11\r\x02\x04\x06 \x06\x0f\x05 \x03\x06\b \x17
\x14
\x15 \a
\r\x06\x0f\x02\x0e\x06)
\x0f\x14\x06\x13\x15-\a
\r\x06-\x04\x10\x0f\x15\x06\x0f\x15\x14("/ \x10\x0e\x06/\x11.\x18\x06\x0f\f/N\x06\x18\x14/")
# (\x16\x0f\x18
\x0f\x05-\x11\x13\x10\x15\x06\x04\x15 ...)
# \x03
\x0f\x05 (\x02
\x14\x15 \a
\r\x06)
\b\x0f\x16\x14-\x14\x04\x10\x13\x06-\r\x10\x02\x05-\x14\x04\x10\x13\x06-\x02
\x14\x15("/ \x10\x0e\x06/\x11.\x18\x06\x0f\f/N\x06\x18\x14/")
# \x03
\x0f\x05 (\x02
\x14\x15
\x14\x15\x14 \b\r\x10\x03\x02\r \x04\x02\x04 \x06\x05 \a
\r\x06 \a
\r\x06)
\b\x0f\x16\x14-\x14\x04\x10\x13\x06-\r\x10\x02\x05-\a
\r\x06("")
# (\x16\x0f\x18
\x0f\x05-\x11\x13\x10\x15\x06\x04\x15 ...)
\b\x0f\x16\x14-\x14\x04\x10\x13\x06-\x02\x05\x02\x11\x15
\x17\x06()
# \x03
\x0f\x05 ( \x06\x02\x05\x06\x13\x14 \b\x13\x10\x16\x11)
# (\x16\x0f\x18
\x0f\x05-\x11\x13\x10\x15\x06\x04\x15 ...)
# \x03
\x0f\x05 (\x0f\x10\x0f-\x05\x06\x14\x15\x13\x16\x04\x15
\x17\x06)
\b\x0f\x16\x14-\x14\x16\x0e\x0e\x02\x13\x1a-\x16\x11\x05\x02\x15\x06-
\x0f\a\x10()
# \x03
\x0f\x05 (\x03\x16\a \b\x13\x10\x16\x11-\x11\x10
\x0f\x15 \x0e\x10\x05\x06 \x12\x16
\x15-\x04\x10\x0f\a
\b \b\x13\x10\x16\x11 \x15\x06\x0e\x11\x10\x13\x02\x13\x1a)
#<\x04\x10\x0e\x11
\r\x06\x05-\a\x16\x0f\x04\x15
\x10\x0f (\a\x13\x10\x0e "\b\x0f\x16\x14-\x14\x16\x0e.\x06\r\x04") (&\x10\x11\x15
\x10\x0f\x02\r \x15\x06\x0e\x11\x10\x13\x02\x13\x1a) "...(462)" [\b\x0f\x16\x14-\x14\x06\x15-\b\r\x10\x03\x02\r-\x17\x02\x13
\x02\x03\r\x06\x14 \b\x0f\x16\x14-\f
\r\r-\x14\x02\x17\x06-\f
\r\r-\x03\x16\a\a\x06\x13 \b\x0f\x16\x14-\x0f\x06\x18\x14\b\x13\x10\x16\x11-\x0f\x02\x0e\x06 \b\x13\x10\x16\x11 \b\x0f\x16\x14-\b\x13\x10\x16\x11-\x12\x16
\x15-\x04\x10\x0f\a
\b \x12\x16
\x15-\x04\x10\x0f\a
\b \x0e\x02\v\x10\x13-\x0e\x10\x05\x06 \x0e\x10\x05\x06 \x0f
\r \b\x13\x10\x16\x11-\x11\x10
\x0f\x15 \x03\x16\a \x13\x16\x0f- \x10\x10\f\x14 \b\x0f\x16\x14-\x14\x16\x0e\x0e\x02\x13\x1a-\x11\x13\x06\x11\x02\x13\x06-\x06\x19
\x15- \x10\x10\f \b\x0f\x16\x14-\x14
\x0f\b\r\x06-\x02\x13\x15
\x04\r\x06-\x03\x16\a\a\x06\x13 \b\x0f\x16\x14-\x10\x13
\b
\x0f\x02\r-\x02\x13\x15
\x04\r\x06-\x03\x16\a\a\x06\x13 \x03\x16\a\a\x06\x13 \b\x06\x15-\x03\x16\a\a\x06\x13 \x03\x16\a\a\x06\x13-\x0f\x02\x0e\x06 \f
\r\r-\x03\x16\a\a\x06\x13 \b\x0f\x16\x14-\x02\x13\x15
\x04\r\x06-\x04\x16\x13\x13\x06\x0f\x15 \b\x0f\x16\x14-\x16\x14\x06-\x04\x02\x04 \x06 \b\x0f\x16\x14-\x04\x02\x04 \x06-\x11\x10\x14\x14
\x03\r\x1a-\x13\x06\x0e\x10\x17\x06-\x02\x13\x15
\x04\r\x06\x14 \b\x0f\x16\x14-\x04\x02\x04 \x06-\x14\x02\x17\x06-\x03\x16\a\a\x06\x13\x14 \b\x0f\x16\x14-\x02\x14\x1a\x0f\x04-\x11\x13\x06\a\x06\x15\x04 -\x13\x06\x0e\x10\x17\x06-\b\x13\x10\x16\x11
\b\x0f\x16\x14-\x14\x16\x11\x11\x13\x06\x14\x14-\x05\x16\x11
\x04\x02\x15\x06\x14 \b\x0f\x16\x14-\x05\x16\x11-\x06\x0f\x15\x06\x13-\x02\x13\x15
\x04\r\x06\x14 \b\x0f\x16\x14-\x16\x14\x06-\x15\x13\x06\x06\x14 \b\x0f\x16\x14-\x15\x13\x06\x06-\x04\r\x10\x14\x06 \b\x0f\x16\x14-\x06\x19
\x15-\b\x13\x10\x16\x11- \x10\x10\f \b\x0f\x16\x14-\x14\x16\x0e\x0e\x02\x13\x1a-\x16\x11\x05\x02\x15\x06-
\x0f\a\x10 \b\x0f\x16\x14-\x04\r\x10\x14\x06-\b\x13\x10\x16\x11 \b\x0f\x16\x14-\b\x13\x10\x16\x11-\x03\x16\a\a\x06\x13 \b\x0f\x16\x14-\b\x13\x10\x16\x11-\v\x16\x0e\x11-\x15\x10-\b\x13\x10\x16\x11 \b\x0f\x16\x14-\x14\x16\x0e\x0e\x02\x13\x1a-\x06\x19
\x15- \x10\x10\f \b\x0f\x16\x14-\b\x13\x10\x16\x11-\x0f\x06\x19\x15-\x16\x0f\x13\x06\x02\x05-\b\x13\x10\x16\x11 1 \x15\x06\x0e\x11\x10\x13\x02\x13\x1a \b\x0f\x16\x14-\x02\x13\x15
\x04\r\x06-\x03\x16\a\a\x06\x13 \b\x0f\x16\x14-\f
\r\r-\x14\x16\x0e\x0e\x02\x13\x1a-\x10\x0f-\x06\x19
\x15 \b\x0f\x16\x14-\x05\x06\x02\x05\x06\x0f-\x14\x16\x0e\x0e\x02\x13\x1a \b\x0f\x16\x14-\x14\x16\x0e\x0e\x02\x13\x1a-\x04\r\x06\x02\x13-\r\x10\x04\x02\r-\x17\x02\x13
\x02\x03\r\x06\x14 \x03\x16\x13\x1a-\x03\x16\a\a\x06\x13 \b\x0f\x16\x14-\x14\x16\x0e\x0e\x02\x13\x1a-\x0e\x10\x05\x06 \b\x0f\x16\x14-\x14\x06\r\x06\x04\x15-\x0e\x06\x15 \x10\x05 \b\x0f\x16\x14-\x04\x16\x13\x13\x06\x0f\x15-\x14\x06\r\x06\x04\x15-\x0e\x06\x15 \x10\x05 \x11\x10\x11-\x15\x10-\x03\x16\a\a\x06\x13 \b\x0f\x16\x14-\x04\x10\x0f\a
\b\x16\x13\x06-\x18
\x0f\x05\x10\x18\x14 \a\x10\x13\x04\x06 \b\x0f\x16\x14- \x02\x0f\x05\r\x06-\x06\x11 \x06\x0e\x06\x13\x02\r-\x06\x19
\x15] 4 ("/\x16\x14\x13/X11R6/
\x03/\x19\x06\x0e\x02\x04\x14-20.4/
\x14\x11/\b\x0f\x16\x14/\b\x0f\x16\x14-\x14\x16\x0e.\x06\r\x04" . 124091) \x0f
\r>()
\x04\x02\r\r-
\x0f\x15\x06\x13\x02\x04\x15
\x17\x06\r\x1a(\b\x0f\x16\x14-\x14\x16\x0e\x0e\x02\x13\x1a-\x06\x19
\x15)
# (\x04\x10\x0f\x05
\x15
\x10\x0f-\x04\x02\x14\x06 ... . \x06\x13\x13\x10\x13)
# (\x04\x02\x15\x04 \x15\x10\x11-\r\x06\x17\x06\r ...)
E\x13\x13\x06\x16\x13 \x05\x06 \x14\x06\b\x0e\x06\x0f\x15\x02\x15
\x10\x0f.
Y\x10\x16 \x02\x17\x06 \x0f\x06\x18 \x0e\x02
\r
\x0f /\x17\x02\x13/\x14\x11\x10\x10\r/\x0e\x02
\r/\x11.\x18\x06\x0f
\x11.\x18\x06\x0f\f@\x14\x13\x06-4-139:\x1f >
Now what's all this ?
How can I correct it
Many thanks
Regards
--
/ / (_)____ __ ____ __
Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland
/____/_/_//_/\_,_/ /_/\_\
^ permalink raw reply [flat|nested] 22+ messages in thread* Re: ERROR AGAIN !! 1999-11-12 13:36 ERROR AGAIN !! Pieter Wenk @ 1999-11-15 19:15 ` Lars Magne Ingebrigtsen 1999-11-15 19:22 ` Laura Conrad 1999-11-15 23:06 ` ERROR AGAIN !! Jan Vroonhof 1 sibling, 1 reply; 22+ messages in thread From: Lars Magne Ingebrigtsen @ 1999-11-15 19:15 UTC (permalink / raw) Pieter Wenk <pwenk@urbanet.ch> writes: > Fatal error (11). > Your files have been auto-saved. > Use `M-x recover-session' to recover them. [...] > Now what's all this ? Well, it looks like an XEmacs bug, so you should report it to the XEmacs maintainers. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-15 19:15 ` Lars Magne Ingebrigtsen @ 1999-11-15 19:22 ` Laura Conrad 1999-11-15 20:06 ` Lars Magne Ingebrigtsen ` (2 more replies) 0 siblings, 3 replies; 22+ messages in thread From: Laura Conrad @ 1999-11-15 19:22 UTC (permalink / raw) >>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes: Lars> Well, it looks like an XEmacs bug, so you should report it Lars> to the XEmacs maintainers. Lars, My experience of reporting bugs to the XEmacs maintainers is that if I or the traceback mentions gnus, they assign it to you. Is this experience out of date? Or is getting a bug report through them rather than from here in some way easier for you to deal with? Or do you just want to make sure they have a record that they're crashing our systems? -- Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ ) (617) 661-8097 fax: (801) 365-6574 233 Broadway, Cambridge, MA 02139 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-15 19:22 ` Laura Conrad @ 1999-11-15 20:06 ` Lars Magne Ingebrigtsen 1999-11-15 22:59 ` Jan Vroonhof 1999-11-17 15:20 ` Pieter Wenk 2 siblings, 0 replies; 22+ messages in thread From: Lars Magne Ingebrigtsen @ 1999-11-15 20:06 UTC (permalink / raw) Laura Conrad <lconrad@gamesville.com> writes: > Lars, My experience of reporting bugs to the XEmacs maintainers is > that if I or the traceback mentions gnus, they assign it to you. Is > this experience out of date? Or is getting a bug report through them > rather than from here in some way easier for you to deal with? Or do > you just want to make sure they have a record that they're crashing > our systems? Well -- I consider anything that actually crashes any of the Emacsen to be entirely outside my domain of expertise. I don't know much C and I know little of the Emacsen internals, so I just don't deal with that. I refer all such messages to the Emacs/XEmacs maintainers, and if they assign them back to me again, then we have a problem. :-) But they don't seem to do that, I think. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-15 19:22 ` Laura Conrad 1999-11-15 20:06 ` Lars Magne Ingebrigtsen @ 1999-11-15 22:59 ` Jan Vroonhof 1999-11-16 7:44 ` Pieter Wenk 1999-11-17 15:20 ` Pieter Wenk 2 siblings, 1 reply; 22+ messages in thread From: Jan Vroonhof @ 1999-11-15 22:59 UTC (permalink / raw) Laura Conrad <lconrad@gamesville.com> writes: > Lars, My experience of reporting bugs to the XEmacs maintainers is > that if I or the traceback mentions gnus, they assign it to you. We do? I think (or hope) that you are confusing 2 things here. If XEmacs crashes while running any lisp program it is an XEmacs bug. In that case we need a C backtrace from gdb to do something from something about it. If you get a _lisp_ error and there is a gnus function in the _lisp backtrace_ then it is most likely a Gnus bug and we refer you here. Jan ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Re: ERROR AGAIN !! 1999-11-15 22:59 ` Jan Vroonhof @ 1999-11-16 7:44 ` Pieter Wenk 1999-11-16 8:35 ` Hrvoje Niksic 1999-11-16 12:27 ` Laura Conrad 0 siblings, 2 replies; 22+ messages in thread From: Pieter Wenk @ 1999-11-16 7:44 UTC (permalink / raw) On lun, 15 nov 1999, Jan Vroonhof wrote: >Laura Conrad <lconrad@gamesville.com> writes: > >> Lars, My experience of reporting bugs to the XEmacs maintainers is >> that if I or the traceback mentions gnus, they assign it to you. > >We do? I think (or hope) that you are confusing 2 things here. If >XEmacs crashes while running any lisp program it is an XEmacs bug. In >that case we need a C backtrace from gdb to do something from >something about it. > >If you get a _lisp_ error and there is a gnus function in the _lisp >backtrace_ then it is most likely a Gnus bug and we refer you here. Thanks a lot for all the explanations. I assume lars will also read this message. I am gladly prepared to submit a bug report to xemacs. Now I have never done this as yet. How to proceed ? Secondly, assuming, that I have a buggy xemacs what is to do that this nifty app stops crashing ? Third, I just started to use gnus. My .gnus is a sort of patchwork of different .gnus samples I gathered on the net (Thanks Robin). This might have a few errors, in particular with regards to the ))) or (( endings I do not as yet understand. Should somebody be prepared to have a look on my .gnus hel- ping me to eliminate some errors or improve certain settings I would be very pleased. Many thanks for your assistance. Regards -- / / (_)____ __ ____ __ Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland /____/_/_//_/\_,_/ /_/\_\ ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-16 7:44 ` Pieter Wenk @ 1999-11-16 8:35 ` Hrvoje Niksic 1999-11-17 8:36 ` Pieter Wenk 1999-11-16 12:27 ` Laura Conrad 1 sibling, 1 reply; 22+ messages in thread From: Hrvoje Niksic @ 1999-11-16 8:35 UTC (permalink / raw) Pieter Wenk <pwenk@urbanet.ch> writes: > I am gladly prepared to submit a bug report to xemacs. Now I have > never done this as yet. How to proceed ? Try to determine why and where your XEmacs crashed. What you were doing at the time, etc. As the crash page says, enter the debugger (gdb /usr/local/bin/xemacs core), type `where' and include that information. For maximum joy, compile XEmacs with debugging symbols enabled, and include debugging stack trace. For pure enlightenment, find the bug and fix it. :-) > Secondly, assuming, that I have a buggy xemacs what is to do that > this nifty app stops crashing ? It depends on why it crashes. Some crashes can be worked around, some can't. > Third, I just started to use gnus. My .gnus is a sort of patchwork > of different .gnus samples I gathered on the net Don't do that. It's a *very* bad idea to include something in your .gnus if you don't understand what it does. > Should somebody be prepared to have a look on my .gnus hel- ping me > to eliminate some errors or improve certain settings I would be very > pleased. Post it here and some of us will try. ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Re: ERROR AGAIN !! 1999-11-16 8:35 ` Hrvoje Niksic @ 1999-11-17 8:36 ` Pieter Wenk 1999-11-20 12:38 ` Pieter Wenk 0 siblings, 1 reply; 22+ messages in thread From: Pieter Wenk @ 1999-11-17 8:36 UTC (permalink / raw) [-- Attachment #1: Type: text/plain, Size: 1838 bytes --] On mar, 16 nov 1999, Hrvoje Niksic wrote: >Try to determine why and where your XEmacs crashed. What you were >doing at the time, etc. As the crash page says, enter the debugger >(gdb /usr/local/bin/xemacs core), type `where' and include that >information. I guess this I found out. It's affetcting 3-4 subscribed groups. Hitting either "c" of "q" did trigger it. I am just kicked out of gnus...and xemacs crashed. Now I tried on one group I tried the following: I just unsubscribed this group....and subscribed it again...now this seems to work again normally..for the time being. >> Third, I just started to use gnus. My .gnus is a sort of patchwork >> of different .gnus samples I gathered on the net > >Don't do that. It's a *very* bad idea to include something in your >.gnus if you don't understand what it does. Ohh. I did of course not pick-up things, I did now the purpose of it. I did include them knowing what I am doing. But I do not know as lisp.... >> Should somebody be prepared to have a look on my .gnus hel- ping me >> to eliminate some errors or improve certain settings I would be very >> pleased. > >Post it here and some of us will try. Thanks a lot. Below, included you will find my .gnus. Some additional info: I run a 586 machine, 64 RAM. I have a wired (cable)connection to my ISP. Since this is very fast, I have not installed leafnode. The settings concerning my connection, are working quite well. (Thanks Robin). I likely may have errors with (( or ))settings, since I do not as yet correctly understand them...But I will go to find it out how to set properly. Many thanks for your assistance Regards -- / / (_)____ __ ____ __ Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland /____/_/_//_/\_,_/ /_/\_\ [-- Attachment #2: .gnus --] [-- Type: text/plain, Size: 17654 bytes --] ;;Muster gnus von Tadamek ;;* Den Start beschleunigen ! ;;============================================================================= (setq gnus-read-active-file nil) (setq gnus-verbose 10) ;(setq gnus-read-active-file t) (setq gnus-check-new-newsgroups nil) (setq gnus-check-bogus-newsgroups 'ask-server) (setq gnus-newsgroup-adaptive-score-file nil ;;* Mails automatisch aus dem Spool holen ;;============================================================================= (setq nnml-get-new-mail t) ;;* News-Holen-Methode setzen. Hier 'nntp' ;;============================================================================= ;;(setq gnus-select-method '(nntp "localhost")) ;; default method for selecting a newsgroup (setq gnus-select-method '(nntp "") ;; preferred method for fetching an article by Message-ID gnus-refer-article-method '(nntp "news,urbanet.ch") ;; program to post news nnspool-inews-program '"/usr/lib/news/inews" ;; list of secondary methods that will be used for reading news gnus-secondary-select-methods '((nnml "Pieter" ;; spool directory for the nnml mail backend (nnml-directory "~/Mail/") ;; mail active file (nnml-active-file "~/Mail/active") ;; mail newsgroups description file (nnml-newsgroups-file "~/Mail/newsgroups"))) ;; name of the directory articles will be saved in gnus-article-save-directory "~/news/" ;; directory variable from which all other Gnus file variables are derived gnus-directory "~/news/" ;; variable to control where interactive score entries are to go gnus-home-score-file ;; return the score file of the top-level hierarchy of GROUP 'gnus-hierarchial-home-score-file ;; directory where kill files will be stored gnus-kill-files-directory (concat gnus-directory "score/") ) ;;* ;;* Diese Verzeichnisse möchten wir immer angezeigt bekommen, auch leer ;;* oder wenn der Inhalt gelesen wurde ;;============================================================================= ;;(setq gnus-permanently-visible-groups "^\\|^nnml\\|^nnfolder") (setq gnus-permanently-visible-groups "") ;;Larger printing-fonts ;:*====================== ;:* describe-face-at-point, a function to find out which face is which (defun describe-face-at-point () "Return face used at point." (interactive) (hyper-describe-face (get-char-property (point) 'face))) ;;* Alle verfassten News-Artikel automatisch speichern und Mails einmal ;;* im Monat in eine Datei mit Datum verfassen ;;============================================================================= (setq gnus-message-archive-group '((if (message-news-p) "archive-news" (concat "mail." (format-time-string "%Y-%m" (current-time)))))) ;;* Kein quoted-printable mehr als transfer-encoding ;;============================================================================= ;;(add-hook 'message-setup-hook ;; '(lambda () ;; (mime-editor/toggle-transfer-level ;; (if (message-news-p) 8 7)))) ;;* 3 Frames werden hiermit angezeigt, oben die summary, ;;* unten den gewählten Artikel und rechts oben eine permanente ;;* grafische und praktische Threadanzeige ;;============================================================================= (progn (setq gnus-build-sparse-threads 'some gnus-use-trees t gnus-generate-tree-function 'gnus-generate-horizontal-tree gnus-tree-minimize-window nil) (gnus-add-configuration '(article (vertical 1.0 (horizontal 0.25 (summary 0.75 point) (tree 1.0)) (article 1.0))))) ;;* Diverse mögliche Anzeigevariablen ARTICLES ;;============================================================================= ;;* highlighting quotes ;; Quotes (citations) sollen farblich hervorgehoben werden (add-hook 'gnus-article-display-hook 'gnus-article-highlight-citation t) (add-hook 'message-mode-hook 'gnus-article-highlight-citation t) (add-hook 'mail-mode-hook 'gnus-article-highlight-citation t) )) (setq gnus-article-display-hook ;; Header-Teile verstecken, wenn `gnus-have-all-headers' is nil '(gnus-article-hide-headers-if-wanted ;; Alle leeren Zeilen vom Artikel-Anfang an werden gelöscht gnus-article-strip-leading-blank-lines ;; Und restliche leere Zeilen ebenso gnus-article-remove-trailing-blank-lines ;; Hebt den gerade gewählten Artikel hervor gnus-article-highlight ;; Sucht im Header nach einem xface gnus-article-display-x-face ;; Zeigt smileys :-) ;-) als kleine icons an gnus-smiley-display ;; Fügt Buttons in den Header ein gnus-article-add-buttons-to-head ;; Blendet den PGP-Kram im Header und Artikel aus gnus-article-hide-pgp) (setq ;; Highlight cited text gnus-treat-highlight-citation 'last ;; Highlight the signature gnus-treat-highlight-signature 'last) ;;* mark threads ;; Threads sollen markiert werden (setq gnus-summary-same-subject "->") ;; resize summary window to 30% of the screen (gnus-add-configuration '(article (vertical 1.0 (summary .30 point) (article 1.0) ) ) ) ;; Summary-Anzeige angenehmer.;;;; ;* nicer summary-line format ;; So gefällt mir das Summary besser (setq gnus-summary-line-format "%U%R%z%(%I%-55,55s %[%n%]%)\n") ;;Smileys: (cond ((and (string-match "XEmacs\\|Lucid" emacs-version) (or (and (= emacs-major-version 19) (>= emacs-minor-version 15)) (and (= emacs-major-version 20) (>= emacs-minor-version 3)))) (load-library "smiley") (add-hook 'gnus-article-display-hook 'smiley-buffer))) ;;* Den Topic-Mode einschalten ;;============================================================================= (add-hook 'gnus-group-mode-hook 'gnus-topic-mode) ;;* Den Mail- und News-Header konfigurieren ;;============================================================================= (setq message-from-style 'angles user-mail-address "pwenk@urbanet.ch" mail-host-address "mail.urbanet.ch" user-full-name "Pieter Wenk" message-default-headers (concat "Organization: P.Wenk \n") message-syntax-checks '((sender . disabled)) ) ;;* Den Header schon bei der Erstellung erzeugen ;;============================================================================= (setq message-generate-headers-first t) >;;*=========================================================== >;;* Super-Cite Settings: >;;*=========================================================== >;;* >;;* >;;* Start of Super-Cite Settings: >;;*================================ >;;* >;; Set some functions >;;*================================ >;;; citing function which performs the initial citation. (autoload 'sc-cite-original "supercite" "Supercite 3.1" t) ;;; submit a bug report on Supercite via mail (autoload 'sc-submit-bug-report "supercite" "Supercite 3.1" t) ;;; modifying a citation just inserted in the mail buffer (add-hook 'mail-citation-hook 'sc-cite-original) ;;; hook which gets run once after Supercite loads. (add-hook 'sc-load-hook 'sc-setup-filladapt) ;;; function for citing an original message (setq message-cite-function 'sc-cite-original) ;; variable not documented (setq sc-message-cite-original-without-signature t) ;; variable not documented (setq news-reply-header-hook nil) (require 'sc-alist) ;; custom function for German citations (defun sc-header-attributed-schrieb-am () "\"<sc-attribution>\" == <sc-author> schrieb am <date>: ;; Treats these fields in a similar manner to `sc-header-on-said'." (let ((sc-mumble "") (whofrom (sc-whofrom))) (if whofrom (insert sc-reference-tag-string (sc-hdr "\"" (sc-mail-field "sc-attribution") "\" == ") (sc-hdr "" (sc-mail-field "sc-author") " ") "schrieb am " (sc-mail-field "date") ":\n")))) ;;* ;;* List of reference header rewrite functions ;;*================================ (defvar sc-rewrite-header-list '((sc-no-header) (sc-no-blank-line-or-header) ;; (sc-header-inarticle-wrote) (sc-header-inarticle-writes (sc-header-verbose) (sc-header-on-said) (sc-header-regarding-adds) (sc-header-attributed-wrote) (sc-header-schrieb-am) (sc-header-author-wrote) (sc-header-attributed-schrieb-am) ) ;; "*List of reference header rewrite functions. The variable ;; `sc-preferred-header-style' controls which function in this list is ;; chosen for automatic reference header insertions. Electric reference ;; mode will cycle through this list of functions.") ;;; (setq sc-preferred-attribution-list (list '"sc-header-schrieb-am" "sc-header-author-wrote" "sc-header-regarding-adds" "sc-header-on-said" "firstname" "emailname" "sc-header-attributed-schrieb-am" "lastname")) ;; ;; ;; Number of blank lines to leave after mail headers have been nuked. (setq sc-blank-lines-after-headers 0 ) ;; always confirm attribution string before citing text body (setq sc-confirm-always-p nil ) ;; index into `sc-rewrite-header-list' specifying preferred header style (setq sc-preferred-header-style 8 ) ;; if non-nil, automatically fill each paragraph after it has been cited (setq sc-auto-fill-region-p t ) ;; if non-nil, delete all leading white space before citing (setq sc-fixup-whitespace-p t ) ;; use electric references if non-nil (setq sc-electric-references-p t ) ;; if non-nil, put a citation on blank lines (setq sc-cite-blank-lines-p nil ) ;; whether to use nested or non-nested citation style (setq sc-nested-citation-p t ) ;; The "citation leader". The citation leader is contained in the ;; variable `sc-citation-leader', and has the default value of a ;; string containing four spaces. (setq sc-citation-leader "" ) ;; The "citation separator". The citation separator is contained in ;; the variable `sc-citation-separator', and has the default value of ;; a string containing a single space. (setq sc-citation-separator " " ) ;; string used at the beginning of built-in reference headers (setq sc-reference-tag-string "* " ) ;; The "citation delimiter". This string, contained in the variable ;; `sc-citation-delimiter' visually separates the citation from the ;; text of the line. This variable has a default value of `">"' and ;; for best results, the string should consist of only a single ;; character. (setq sc-citation-delimiter "> " ) ;;* Das Gnus-Mail-System konfigurieren ;;============================================================================= (setq gnus-secondary-select-methods '((nnml "private"))) (setq user-mail-address "pwenk@urbanet.ch") ;;* ;;* Eingehende Mails aufteilen ;;============================================================================ ;;(setq nnmail-split-methods ;; '( ;; ("xemacs-beta" ;;"^\\(To:\\|Cc:\\|CC:\\|Resent\\|Sender:\\).*xemacs-beta") ("robin" ;;"^\\(To:\\|Cc:\\).*robin") ("Intern" "^\\(To:\\).thomas@*") ;; ("Unsort" "") ;; ) ;; ) ;;* ;;* Delete duplicate Mails ;;*============================================================================ (setq nnmail-treat-duplicates 'delete) ;;* No crossposting in Mails ;;*============================================================================ ;;(setq nnmail-crosspost nil) ;;* automatischer Zeilenumbruch ;;*============================================================================ (add-hook 'message-mode-hook 'turn-on-auto-fill) (setq-default fill-column 70) ;;* MIME-Support einschalten ;;*============================================================================ (load "mime-setup") (setq mime-editor/transfer-level 8) (setq mime-editor/split-message nil) ;;NETSCAPE launching *======================= ;:* make netscape use a new window when clicking a URL ; by Karl Kleinpaste (setq browse-url-new-window-p t) (defun karl-browse (a) "Wrapper, for new window use." (browse-url-netscape a t)) (setq browse-url-browser-function (function karl-browse)) ;;* Signature-Datei ;;*============================================================================ (setq gnus-signature-file "~/.signature") ;;* Domaineintrag setzen (keine Ahnung ob's funktioniert) ;;*============================================================================ ;;(concat "<"(message-unique-id)"-pwenk@urbanet.ch>)) ;; And here something in order to get rid of borrowing messages. ;; A nice SCORE DEfinition. ;;* SCORE ;;*================================ ;;* Scoring away stuff I find boring (setq gnus-use-adaptive-scoring t) (defvar gnus-default-adaptive-score-alist '((gnus-unread-mark) (gnus-ticked-mark (from 4)) (gnus-dormant-mark (from 5)) (gnus-del-mark (from -4) (subject -1)) (gnus-read-mark (from 1) (subject 1)) (gnus-expirable-mark (from -1) (subject -1)) (gnus-killed-mark (from -1) (subject -3)) (gnus-kill-file-mark) (gnus-ancient-mark) (gnus-low-score-mark) (gnus-catchup-mark (subject -4) (from -1)) ) ) ;; You may find that your scores have a tendency to grow without bounds, ;; especially if you're using adaptive scoring. If scores get too big, ;; they lose all meaning--they simply max out and it's difficult to use ;; them in any sensible way. (setq gnus-decay-scores t) (defun gnus-decay-score (score) "Decay SCORE. This is done according to `gnus-score-decay-constant' and `gnus-score-decay-scale'." (floor (- score (* (if (< score 0) 1 -1) (min (abs score) (max gnus-score-decay-constant (* (abs score) gnus-score-decay-scale))))))) ;; If not enough, a nice nuke possibility: ;;*================================ ;;* quick nuke people :-) (global-set-key "\C-cx" 'gnus-scum-expunge) ;;* This function should be called from the summary buffer with point ;;* on the article to nuke. It puts a rule in ~/News/SPAMMERS to lower ;;* scores of author ;;* It needs an entry in all.SCORE of (files "~/News/SPAMMERS"). ;; I changed it to only add the from line. (defun gnus-scum-expunge () ;; "Remove this spammer from existance as much as possible." (interactive) (let* ((hdr (gnus-summary-article-header)) (subj (aref hdr 1)) (auth (aref hdr 2)) (artid (aref hdr 4)) (atsign (string-match "@" artid)) (host (substring artid (+ atsign 1) (- (length artid) 1))) (oldscfile gnus-current-score-file)) ;; Change to our spammer score file (gnus-score-change-score-file "SPAMMERS") ;; Add our horrible spammer scores (gnus-summary-score-entry "Subject" subj 'S' -1000 nil) (gnus-summary-score-entry "From" auth 'S' -9999 nil) (gnus-summary-score-entry "Message-ID" host 'S' -5 nil) ; mild ;; Change back to old current score file (gnus-score-change-score-file oldscfile) (gnus-score-save))) ;; Signature limite ;; This one takes care of fucked-up signatures ;; much enhanced version from the example in the docs by Torsten ;; Hilbrich <Torsten.Hilbrich@gmx.net> (setq gnus-signature-separator "^\\(-- \\|^-- *\\|________\\========*\\)$") ;; BBDB, das Adressbuch laden ;;============================================================================= ;;etq load-path (cons "/usr2/opt/bbdb-2.00.06/lisp" load-path)) ;;equire 'bbdb) ;;bdb-initialize 'gnus 'message 'sc 'w3) ;;dd-hook 'gnus-startup-hook 'bbdb-insinuate-gnus) ;;dd-hook 'mail-setup-hook 'bbdb-insinuate-sendmail) ;; Wo EMACS sonst noch nach Info-Files suchen soll ;;================================================ ;;etq Info-directory-list '("/usr2/opt/bbdb-2.00.06/texinfo/" ;;home/thomas/pgnus-0.97/texi/")) ;;* BBDB konfigurieren ;;============================================================================= ;;etq bbdb/news-auto-create-p 'bbdb-ignore-most-messages-hook ;;bbdb-ignore-most-messages-alist '(("To" . "wenk*\\|pieter*\\|*@urbanet.ch"))) ;;etq bbdb-notice-hook 'bbdb-auto-notes-hook) ;;etq bbdb-auto-notes-alist '(("Organization" (".*" company 0)) ;; ("X-Newsreader" (".*" mailer 0)) ;; ("X-Mailer" (".*" mailer 0)) ;; ("X-URL" (".*" url 0)) ;; ("Subject" (".*" last-subj 0 t)) ;; )) ;;("Newsgroup ("[^,]+" newsgroups 0)))) ;; ("Subject" (".*" last-subj 0 t)) ;; ("User-Agent" (".*" mailer 0)) ;; ("X-Newsreader" (".*" mailer 0)) ;; ("X-Mailer" (".*" mailer 0)) ;; ("X-URL" (".*" url 0)) ;; )) ;;*So geben wir der BBDB einen Datumsstempel mit auf den Weg ;;dd-hook 'bbdb-change-hook 'bbdb-creation-date-hook) ;;dd-hook 'bbdb-change-hook 'bbdb-timestamp-hook) ;;* und die BBDB-Erweiterung BBDB-Frame laden ;;(load "/usr2/opt/bbdb-frame/bbdb-frame") ;;(define-key bbdb-mode-map "T" 'bbdb-toggle-separate-frame) ;;(define-key bbdb-mode-map "i" 'bbdb-iconify) ;;(define-key bbdb-mode-map "q" 'bbdb-quit-frame) ;;* noch einige Einstellungen für BBDB ;;============================================================================= ;;dd-hook 'gnus-save-newsrc-hook 'bbdb-offer-save) ;;dd-hook 'gnus-exit-group-hook 'bbdb-offer-save) ;;etq bbdb-offer-save 'auto) ;just save, don't ask ;;* noch einige Tasten für BBDB ;;============================================================================= ;;lobal-set-key '(control f10) 'bbdb-create) ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Re: Re: ERROR AGAIN !! 1999-11-17 8:36 ` Pieter Wenk @ 1999-11-20 12:38 ` Pieter Wenk 1999-11-20 15:01 ` Michael Klingbeil 1999-11-20 22:25 ` Kai Großjohann 0 siblings, 2 replies; 22+ messages in thread From: Pieter Wenk @ 1999-11-20 12:38 UTC (permalink / raw) Hello to all: I have posted here a few days ago, my .gnus. Since I believe to have in this .gnus some errors which I should like to correct, I would be very pleased in getting your advises. FYI: I am loading xemacs with -q extention. Ommiting -q let's .gnus hang on (setq 11 What this number means, I have no idea. I edited of course my .gnus with vim and asked line 11...but this can't be correct. I would be very pleased if some of few could have a look on my .gnus I herewith include once again. Many thanks for your assistance. > >>> Should somebody be prepared to have a look on my .gnus hel- ping me >>> to eliminate some errors or improve certain settings I would be very >>> pleased. >> >>Post it here and some of us will try. > >Thanks a lot. Below, included you will find my .gnus. > >Some additional info: > >I run a 586 machine, 64 RAM. I have a wired (cable)connection >to my ISP. Since this is very fast, I have not installed leafnode. >The settings concerning my connection, are working quite well. >(Thanks Robin). > >I likely may have errors with (( or ))settings, since I do not as >yet correctly understand them...But I will go to find it out >how to set properly. > > >;;GNUS CONFIGURATION 12.11.99 > >;;* Den Start beschleunigen ! >;;============================================================================= >(setq gnus-read-active-file nil) >(setq gnus-verbose 10) >;(setq gnus-read-active-file t) >(setq gnus-check-new-newsgroups nil) >(setq gnus-check-bogus-newsgroups 'ask-server) >(setq gnus-newsgroup-adaptive-score-file nil > >;;* Mails automatisch aus dem Spool holen >;;============================================================================= >(setq nnml-get-new-mail t) > > > >;;* News-Holen-Methode setzen. Hier 'nntp' >;;============================================================================= >;;(setq gnus-select-method '(nntp "localhost")) > > ;; default method for selecting a newsgroup > (setq gnus-select-method '(nntp "") > ;; preferred method for fetching an article by Message-ID > gnus-refer-article-method '(nntp "news,urbanet.ch") > ;; program to post news > nnspool-inews-program '"/usr/lib/news/inews" > > ;; list of secondary methods that will be used for reading news > gnus-secondary-select-methods > '((nnml "Pieter" > ;; spool directory for the nnml mail backend > (nnml-directory "~/Mail/") > ;; mail active file > (nnml-active-file "~/Mail/active") > ;; mail newsgroups description file > (nnml-newsgroups-file "~/Mail/newsgroups"))) > ;; name of the directory articles will be saved in > gnus-article-save-directory "~/news/" > ;; directory variable from which all other Gnus file variables are derived > gnus-directory "~/news/" > ;; variable to control where interactive score entries are to go > gnus-home-score-file > ;; return the score file of the top-level hierarchy of GROUP > 'gnus-hierarchial-home-score-file > ;; directory where kill files will be stored > gnus-kill-files-directory (concat gnus-directory "score/") > ) > ;;* >;;* Diese Verzeichnisse möchten wir immer angezeigt bekommen, auch leer >;;* oder wenn der Inhalt gelesen wurde >;;============================================================================= >;;(setq gnus-permanently-visible-groups "^\\|^nnml\\|^nnfolder") >(setq gnus-permanently-visible-groups "") > >;;Larger printing-fonts > > >;:*====================== >;:* describe-face-at-point, a function to find out which face is which >(defun describe-face-at-point () > "Return face used at point." > (interactive) > (hyper-describe-face (get-char-property (point) 'face))) > > >;;* Alle verfassten News-Artikel automatisch speichern und Mails einmal >;;* im Monat in eine Datei mit Datum verfassen >;;============================================================================= >(setq gnus-message-archive-group > '((if (message-news-p) > "archive-news" > (concat "mail." (format-time-string > "%Y-%m" (current-time)))))) > >;;* Kein quoted-printable mehr als transfer-encoding >;;============================================================================= >;;(add-hook 'message-setup-hook >;; '(lambda () >;; (mime-editor/toggle-transfer-level >;; (if (message-news-p) 8 7)))) > > >;;* 3 Frames werden hiermit angezeigt, oben die summary, >;;* unten den gewählten Artikel und rechts oben eine permanente >;;* grafische und praktische Threadanzeige >;;============================================================================= >(progn > (setq gnus-build-sparse-threads 'some > gnus-use-trees t > gnus-generate-tree-function 'gnus-generate-horizontal-tree > gnus-tree-minimize-window nil) > (gnus-add-configuration > '(article > (vertical 1.0 > (horizontal 0.25 > (summary 0.75 point) > (tree 1.0)) > (article 1.0))))) > >;;* Diverse mögliche Anzeigevariablen ARTICLES >;;============================================================================= > >;;* highlighting quotes >;; Quotes (citations) sollen farblich hervorgehoben werden >(add-hook 'gnus-article-display-hook 'gnus-article-highlight-citation t) >(add-hook 'message-mode-hook 'gnus-article-highlight-citation t) >(add-hook 'mail-mode-hook 'gnus-article-highlight-citation t) > > )) > > >(setq gnus-article-display-hook > > ;; Header-Teile verstecken, wenn `gnus-have-all-headers' is nil > '(gnus-article-hide-headers-if-wanted > ;; Alle leeren Zeilen vom Artikel-Anfang an werden gelöscht > gnus-article-strip-leading-blank-lines > ;; Und restliche leere Zeilen ebenso > gnus-article-remove-trailing-blank-lines > ;; Hebt den gerade gewählten Artikel hervor > gnus-article-highlight > ;; Sucht im Header nach einem xface > gnus-article-display-x-face > ;; Zeigt smileys :-) ;-) als kleine icons an > gnus-smiley-display > ;; Fügt Buttons in den Header ein > gnus-article-add-buttons-to-head > ;; Blendet den PGP-Kram im Header und Artikel aus > gnus-article-hide-pgp) > > > >(setq > ;; Highlight cited text > gnus-treat-highlight-citation 'last > ;; Highlight the signature > gnus-treat-highlight-signature 'last) > > >;;* mark threads >;; Threads sollen markiert werden >(setq gnus-summary-same-subject "->") > >;; resize summary window to 30% of the screen >(gnus-add-configuration > '(article (vertical 1.0 > (summary .30 point) > (article 1.0) > ) > ) > ) > >;; Summary-Anzeige angenehmer.;;;; > >;* nicer summary-line format >;; So gefällt mir das Summary besser >(setq gnus-summary-line-format "%U%R%z%(%I%-55,55s %[%n%]%)\n") > > >;;Smileys: > >(cond ((and (string-match "XEmacs\\|Lucid" emacs-version) > (or (and (= emacs-major-version 19) > (>= emacs-minor-version 15)) > (and (= emacs-major-version 20) > (>= emacs-minor-version 3)))) > (load-library "smiley") > (add-hook 'gnus-article-display-hook 'smiley-buffer))) > > > > >;;* Den Topic-Mode einschalten >;;============================================================================= >(add-hook 'gnus-group-mode-hook 'gnus-topic-mode) > >;;* Den Mail- und News-Header konfigurieren >;;============================================================================= >(setq message-from-style 'angles > user-mail-address "pwenk@urbanet.ch" > mail-host-address "mail.urbanet.ch" > user-full-name "Pieter Wenk" > message-default-headers > (concat "Organization: P.Wenk \n") > message-syntax-checks '((sender . disabled)) > ) > >;;* Den Header schon bei der Erstellung erzeugen >;;============================================================================= >(setq message-generate-headers-first t) > > >>;;*=========================================================== >>;;* Super-Cite Settings: >>;;*=========================================================== >>;;* >>;;* >>;;* Start of Super-Cite Settings: >>;;*================================ >>;;* >>;; Set some functions >>;;*================================ >>;;; citing function which performs the initial citation. > (autoload 'sc-cite-original "supercite" "Supercite 3.1" t) > ;;; submit a bug report on Supercite via mail > (autoload 'sc-submit-bug-report "supercite" "Supercite 3.1" t) > ;;; modifying a citation just inserted in the mail buffer > (add-hook 'mail-citation-hook 'sc-cite-original) > ;;; hook which gets run once after Supercite loads. > (add-hook 'sc-load-hook 'sc-setup-filladapt) >;;; function for citing an original message > (setq message-cite-function 'sc-cite-original) > ;; variable not documented > (setq sc-message-cite-original-without-signature t) > ;; variable not documented > (setq news-reply-header-hook nil) > (require 'sc-alist) > ;; custom function for German citations > (defun sc-header-attributed-schrieb-am () > "\"<sc-attribution>\" == <sc-author> schrieb am <date>: > >;; Treats these fields in a similar manner to `sc-header-on-said'." > (let ((sc-mumble "") > (whofrom (sc-whofrom))) > (if whofrom > (insert sc-reference-tag-string > (sc-hdr "\"" (sc-mail-field "sc-attribution") "\" == ") > (sc-hdr "" (sc-mail-field "sc-author") " ") > "schrieb am " (sc-mail-field "date") ":\n")))) >;;* >;;* List of reference header rewrite functions >;;*================================ > (defvar sc-rewrite-header-list > '((sc-no-header) > (sc-no-blank-line-or-header) > ;; (sc-header-inarticle-wrote) > (sc-header-inarticle-writes > (sc-header-verbose) > (sc-header-on-said) > (sc-header-regarding-adds) > (sc-header-attributed-wrote) > (sc-header-schrieb-am) > (sc-header-author-wrote) > (sc-header-attributed-schrieb-am) > ) > >;; "*List of reference header rewrite functions. The variable >;; `sc-preferred-header-style' controls which function in this list is >;; chosen for automatic reference header insertions. Electric reference >;; mode will cycle through this list of functions.") >;;; > > (setq sc-preferred-attribution-list > (list > '"sc-header-schrieb-am" > "sc-header-author-wrote" > "sc-header-regarding-adds" > "sc-header-on-said" > "firstname" > "emailname" > "sc-header-attributed-schrieb-am" > "lastname")) >;; >;; > ;; Number of blank lines to leave after mail headers have been nuked. > (setq > sc-blank-lines-after-headers 0 > ) > ;; always confirm attribution string before citing text body > (setq > sc-confirm-always-p nil > ) > ;; index into `sc-rewrite-header-list' specifying preferred header style > (setq > sc-preferred-header-style 8 > ) > ;; if non-nil, automatically fill each paragraph after it has been cited > (setq > sc-auto-fill-region-p t > ) > ;; if non-nil, delete all leading white space before citing > (setq > sc-fixup-whitespace-p t > ) > ;; use electric references if non-nil > (setq > sc-electric-references-p t > ) > ;; if non-nil, put a citation on blank lines > (setq > sc-cite-blank-lines-p nil > ) > ;; whether to use nested or non-nested citation style > (setq > sc-nested-citation-p t > ) > ;; The "citation leader". The citation leader is contained in the > ;; variable `sc-citation-leader', and has the default value of a > ;; string containing four spaces. > (setq > sc-citation-leader "" > ) > ;; The "citation separator". The citation separator is contained in > ;; the variable `sc-citation-separator', and has the default value of > ;; a string containing a single space. > (setq > sc-citation-separator " " > ) >;; string used at the beginning of built-in reference headers > (setq > sc-reference-tag-string "* " > ) > ;; The "citation delimiter". This string, contained in the variable > ;; `sc-citation-delimiter' visually separates the citation from the > ;; text of the line. This variable has a default value of `">"' and > ;; for best results, the string should consist of only a single > ;; character. > (setq > sc-citation-delimiter "> " > ) > > > > >;;* Das Gnus-Mail-System konfigurieren >;;============================================================================= >(setq gnus-secondary-select-methods '((nnml "private"))) >(setq user-mail-address "pwenk@urbanet.ch") > >;;* >;;* Eingehende Mails aufteilen >;;============================================================================ >;;(setq nnmail-split-methods >;; '( >;; ("xemacs-beta" >;;"^\\(To:\\|Cc:\\|CC:\\|Resent\\|Sender:\\).*xemacs-beta") ("robin" >;;"^\\(To:\\|Cc:\\).*robin") ("Intern" "^\\(To:\\).thomas@*") >;; ("Unsort" "") >;; ) >;; ) > >;;* >;;* Delete duplicate Mails >;;*============================================================================ >(setq nnmail-treat-duplicates 'delete) > >;;* No crossposting in Mails >;;*============================================================================ >;;(setq nnmail-crosspost nil) > >;;* automatischer Zeilenumbruch >;;*============================================================================ > > >(add-hook 'message-mode-hook 'turn-on-auto-fill) >(setq-default fill-column 70) > > >;;* MIME-Support einschalten >;;*============================================================================ >(load "mime-setup") >(setq mime-editor/transfer-level 8) >(setq mime-editor/split-message nil) > >;;NETSCAPE launching > > >*======================= >;:* make netscape use a new window when clicking a URL >; by Karl Kleinpaste >(setq browse-url-new-window-p t) >(defun karl-browse (a) >;; "Wrapper, for new window use." > (browse-url-netscape a t)) >(setq browse-url-browser-function (function karl-browse)) > > >;;* Signature-Datei >;;*============================================================================ >(setq gnus-signature-file "~/.signature") > >;;* Domaineintrag setzen (keine Ahnung ob's funktioniert) >;;*============================================================================ >;;(concat "<"(message-unique-id)"-pwenk@urbanet.ch>)) > > >;; And here something in order to get rid of borrowing messages. >;; A nice SCORE DEfinition. > >;;* SCORE >;;*================================ >;;* Scoring away stuff I find boring > > >(setq gnus-use-adaptive-scoring t) >(defvar gnus-default-adaptive-score-alist > '((gnus-unread-mark) > (gnus-ticked-mark (from 4)) > (gnus-dormant-mark (from 5)) > (gnus-del-mark (from -4) (subject -1)) > (gnus-read-mark (from 1) (subject 1)) > (gnus-expirable-mark (from -1) (subject -1)) > (gnus-killed-mark (from -1) (subject -3)) > (gnus-kill-file-mark) > (gnus-ancient-mark) > (gnus-low-score-mark) > (gnus-catchup-mark (subject -4) (from -1)) > ) > ) >;; You may find that your scores have a tendency to grow without bounds, >;; especially if you're using adaptive scoring. If scores get too big, >;; they lose all meaning--they simply max out and it's difficult to use >;; them in any sensible way. >(setq gnus-decay-scores t) >(defun gnus-decay-score (score) > "Decay SCORE. >;; This is done according to `gnus-score-decay-constant' >;; and `gnus-score-decay-scale'." > (floor > (- score > (* (if (< score 0) 1 -1) > (min (abs score) > (max gnus-score-decay-constant > (* (abs score) > gnus-score-decay-scale))))))) > > >;; If not enough, a nice nuke possibility: > >;;*================================ >;;* quick nuke people :-) > (global-set-key "\C-cx" 'gnus-scum-expunge) >;;* This function should be called from the summary buffer with point >;;* on the article to nuke. It puts a rule in ~/News/SPAMMERS to lower >;;* scores of author >;;* It needs an entry in all.SCORE of (files "~/News/SPAMMERS"). >;; I changed it to only add the from line. > (defun gnus-scum-expunge () >;; "Remove this spammer from existance as much as possible." > (interactive) > (let* ((hdr (gnus-summary-article-header)) > (subj (aref hdr 1)) > (auth (aref hdr 2)) > (artid (aref hdr 4)) > (atsign (string-match "@" artid)) > (host (substring artid (+ atsign 1) (- (length artid) 1))) > (oldscfile gnus-current-score-file)) > ;; Change to our spammer score file > (gnus-score-change-score-file "SPAMMERS") > ;; Add our horrible spammer scores > (gnus-summary-score-entry "Subject" subj 'S' -1000 nil) > (gnus-summary-score-entry "From" auth 'S' -9999 nil) > (gnus-summary-score-entry "Message-ID" host 'S' -5 nil) ; mild > ;; Change back to old current score file > (gnus-score-change-score-file oldscfile) > (gnus-score-save))) > > >;; Signature limite >;; This one takes care of fucked-up signatures >;; much enhanced version from the example in the docs by Torsten >;; Hilbrich <Torsten.Hilbrich@gmx.net> >(setq gnus-signature-separator > "^\\(-- \\|^-- *\\|________\\========*\\)$") > > > >;; BBDB, das Adressbuch laden >;;============================================================================= >;;etq load-path (cons "/usr2/opt/bbdb-2.00.06/lisp" load-path)) >;;equire 'bbdb) >;;bdb-initialize 'gnus 'message 'sc 'w3) >;;dd-hook 'gnus-startup-hook 'bbdb-insinuate-gnus) >;;dd-hook 'mail-setup-hook 'bbdb-insinuate-sendmail) > >;; Wo EMACS sonst noch nach Info-Files suchen soll >;;================================================ >;;etq Info-directory-list '("/usr2/opt/bbdb-2.00.06/texinfo/" >;;home/thomas/pgnus-0.97/texi/")) > >;;* BBDB konfigurieren >;;============================================================================= >;;etq bbdb/news-auto-create-p 'bbdb-ignore-most-messages-hook >;;bbdb-ignore-most-messages-alist '(("To" . "wenk*\\|pieter*\\|*@urbanet.ch"))) > >;;etq bbdb-notice-hook 'bbdb-auto-notes-hook) >;;etq bbdb-auto-notes-alist '(("Organization" (".*" company 0)) >;; ("X-Newsreader" (".*" mailer 0)) >;; ("X-Mailer" (".*" mailer 0)) >;; ("X-URL" (".*" url 0)) >;; ("Subject" (".*" last-subj 0 t)) >;; )) >;;("Newsgroup ("[^,]+" newsgroups 0)))) >;; ("Subject" (".*" last-subj 0 t)) >;; ("User-Agent" (".*" mailer 0)) >;; ("X-Newsreader" (".*" mailer 0)) >;; ("X-Mailer" (".*" mailer 0)) >;; ("X-URL" (".*" url 0)) >;; )) > >;;*So geben wir der BBDB einen Datumsstempel mit auf den Weg >;;dd-hook 'bbdb-change-hook 'bbdb-creation-date-hook) >;;dd-hook 'bbdb-change-hook 'bbdb-timestamp-hook) > >;;* und die BBDB-Erweiterung BBDB-Frame laden >;;(load "/usr2/opt/bbdb-frame/bbdb-frame") > >;;(define-key bbdb-mode-map "T" 'bbdb-toggle-separate-frame) >;;(define-key bbdb-mode-map "i" 'bbdb-iconify) >;;(define-key bbdb-mode-map "q" 'bbdb-quit-frame) > >;;* noch einige Einstellungen für BBDB >;;============================================================================= >;;dd-hook 'gnus-save-newsrc-hook 'bbdb-offer-save) >;;dd-hook 'gnus-exit-group-hook 'bbdb-offer-save) >;;etq bbdb-offer-save 'auto) ;just save, don't ask > >;;* noch einige Tasten für BBDB >;;============================================================================= >;;global-set-key '(control f10) 'bbdb-create) > -- / / (_)____ __ ____ __ Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland /____/_/_//_/\_,_/ /_/\_\ ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-20 12:38 ` Pieter Wenk @ 1999-11-20 15:01 ` Michael Klingbeil 1999-11-20 22:25 ` Kai Großjohann 1 sibling, 0 replies; 22+ messages in thread From: Michael Klingbeil @ 1999-11-20 15:01 UTC (permalink / raw) Pieter Wenk <pwenk@urbanet.ch> writes: > >(setq gnus-newsgroup-adaptive-score-file nil ^^) [...] > >;;* highlighting quotes > >;; Quotes (citations) sollen farblich hervorgehoben werden > >(add-hook 'gnus-article-display-hook 'gnus-article-highlight-citation t) > >(add-hook 'message-mode-hook 'gnus-article-highlight-citation t) > >(add-hook 'mail-mode-hook 'gnus-article-highlight-citation t) > > > > )) ^^? [...] > > ;; Zeigt smileys :-) ;-) als kleine icons an ^^ ^^ ;; Zeigt smileys als kleine icons an > > gnus-smiley-display > > ;; Fügt Buttons in den Header ein > > gnus-article-add-buttons-to-head > > ;; Blendet den PGP-Kram im Header und Artikel aus > > gnus-article-hide-pgp) ^^) -- micha ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-20 12:38 ` Pieter Wenk 1999-11-20 15:01 ` Michael Klingbeil @ 1999-11-20 22:25 ` Kai Großjohann 1999-11-20 22:38 ` Pieter Wenk 1999-11-22 21:40 ` Aaron M. Ucko 1 sibling, 2 replies; 22+ messages in thread From: Kai Großjohann @ 1999-11-20 22:25 UTC (permalink / raw) Pieter Wenk <pwenk@urbanet.ch> writes: > FYI: I am loading xemacs with -q extention. > Ommiting -q let's .gnus hang on (setq 11 `-q' means do not load the .emacs file. Hence, this error is most probably in the .emacs file, not in .gnus. kai -- This gubblick contains many nonsklarkish English flutzpahs, but the overall pluggandisp can be glorked from context. -- David Moser ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-20 22:25 ` Kai Großjohann @ 1999-11-20 22:38 ` Pieter Wenk 1999-11-20 23:13 ` Kai Großjohann 1999-11-22 21:40 ` Aaron M. Ucko 1 sibling, 1 reply; 22+ messages in thread From: Pieter Wenk @ 1999-11-20 22:38 UTC (permalink / raw) On 20-Nov-99 Kai Großjohann wrote: > Pieter Wenk <pwenk@urbanet.ch> writes: Hallo Kai >> FYI: I am loading xemacs with -q extention. >> Ommiting -q let's .gnus hang on (setq 11 > > `-q' means do not load the .emacs file. Hence, this error is most > probably in the .emacs file, not in .gnus. I guess you right. Is there a ML concerning xemacs/emacs similar to ding@gnus ? BTW: I just installed leafnode. This will likely change somewhat my .gnus settings. I have the following actual settings conerning NNTP: ;;============================================================================= (setq gnus-read-active-file nil) (setq gnus-verbose 10) ;(setq gnus-read-active-file t) (setq gnus-check-new-newsgroups nil) (setq gnus-check-bogus-newsgroups 'ask-server) (setq gnus-newsgroup-adaptive-score-file nil) ;;* Mails automatisch aus dem Spool holen ;;============================================================================= (setq nnml-get-new-mail t) ;;* News-Holen-Methode setzen. Hier 'nntp' ;;============================================================================= ;;(setq gnus-select-method '(nntp "localhost")) ;; default method for selecting a newsgroup (setq gnus-select-method '(nntp "") ;; preferred method for fetching an article by Message-ID gnus-refer-article-method '(nntp "news.urbanet.ch") ;; program to post news nnspool-inews-program '"/usr/lib/news/inews" ;; list of secondary methods that will be used for reading news gnus-secondary-select-methods '((nnml "Pieter" ;; spool directory for the nnml mail backend (nnml-directory "~/Mail/") ;; mail active file (nnml-active-file "~/Mail/active") ;; mail newsgroups description file (nnml-newsgroups-file "~/Mail/newsgroups"))) ;; name of the directory articles will be saved in gnus-article-save-directory "~/news/" ;; directory variable from which all other Gnus file variables are derived gnus-directory "~/news/" ;; variable to control where interactive score entries are to go gnus-home-score-file ;; return the score file of the top-level hierarchy of GROUP 'gnus-hierarchial-home-score-file ;; directory where kill files will be stored gnus-kill-files-directory (concat gnus-directory "score/") ) What would you suggest as entry, with leafnode ?? I thought it to be an excellent idea to put leafnode on work. Many thanks for your assistance. Regards --- / / (_)____ __ ____ __ Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland /____/_/_//_/\_,_/ /_/\_\ ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-20 22:38 ` Pieter Wenk @ 1999-11-20 23:13 ` Kai Großjohann 0 siblings, 0 replies; 22+ messages in thread From: Kai Großjohann @ 1999-11-20 23:13 UTC (permalink / raw) Pieter Wenk <p.wenk@urbanet.ch> writes: > >> FYI: I am loading xemacs with -q extention. > >> Ommiting -q let's .gnus hang on (setq 11 > > > > `-q' means do not load the .emacs file. Hence, this error is most > > probably in the .emacs file, not in .gnus. > > I guess you right. Is there a ML concerning xemacs/emacs > similar to ding@gnus ? There is the help-gnu-emacs@gnu.org mailing list for Emacs, which is gatewayed (both directions) to the gnu.emacs.help newsgroup. There are also comp.emacs and comp.emacs.xemacs newsgroups, but I don't know about a mailing list gateway for them. But since you're talking about leafnode below, I presume that you will be able to read the newsgroups :-) > BTW: I just installed leafnode. This will likely change > somewhat my .gnus settings. I have the following actual > settings conerning NNTP: [...] Well, I used to use leafnode a long time ago, and I think I didn't have to change anything (except for the name of the news server, obviously). But my memory is rather vague since it's been so long ago. Sorry that I can't be of useful help. Your .gnus file is so long that it'd take a long time to go through it all... I glanced over it and didn't see anything. But then, I don't really grok the variables gnus-read-active-file, gnus-check-new-newsgroups, gnus-check-bogus-newsgroups and gnus-newsgroup-adaptive-score-file. Those are the only potentially `suspicous' ones I could see. kai -- This gubblick contains many nonsklarkish English flutzpahs, but the overall pluggandisp can be glorked from context. -- David Moser ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-20 22:25 ` Kai Großjohann 1999-11-20 22:38 ` Pieter Wenk @ 1999-11-22 21:40 ` Aaron M. Ucko 1 sibling, 0 replies; 22+ messages in thread From: Aaron M. Ucko @ 1999-11-22 21:40 UTC (permalink / raw) Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Gro_johann) writes: > Pieter Wenk <pwenk@urbanet.ch> writes: > > > FYI: I am loading xemacs with -q extention. > > Ommiting -q let's .gnus hang on (setq 11 > > `-q' means do not load the .emacs file. Hence, this error is most > probably in the .emacs file, not in .gnus. Not necessarily; Gnus looks at the value of init-file-user to decide whether to load .gnus. -- Aaron M. Ucko, KB1CJC <amu@mit.edu> (finger amu@monk.mit.edu) ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-16 7:44 ` Pieter Wenk 1999-11-16 8:35 ` Hrvoje Niksic @ 1999-11-16 12:27 ` Laura Conrad 1999-11-16 13:54 ` Gunnar Evermann 1999-11-16 20:12 ` Pieter Wenk 1 sibling, 2 replies; 22+ messages in thread From: Laura Conrad @ 1999-11-16 12:27 UTC (permalink / raw) >>>>> "Pieter" == Pieter Wenk <pwenk@urbanet.ch> writes: Pieter> I am gladly prepared to submit a bug report to xemacs. Now Pieter> I have never done this as yet. How to proceed ? There are pretty clear instructions in the message that comes out when it crashes. You can either use the "submit bug report" item on the misc menu, or paste the stuff from the crash window into a regular email message. Pieter> Secondly, assuming, that I have a buggy xemacs what is to Pieter> do that this nifty app stops crashing ? Another thing they used to do (I'm sure present company has nothing to do with this particular bug report handling) is tell you your crashes are because your machine doesn't have enough memory. Probably some of the crashes I see that the developers don't are because my machine has only 32M. -- Laura (mailto:lconrad@world.std.com , http://www.world.std.com/~lconrad/ ) (617) 661-8097 fax: (801) 365-6574 233 Broadway, Cambridge, MA 02139 ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-16 12:27 ` Laura Conrad @ 1999-11-16 13:54 ` Gunnar Evermann 1999-11-16 20:12 ` Pieter Wenk 1 sibling, 0 replies; 22+ messages in thread From: Gunnar Evermann @ 1999-11-16 13:54 UTC (permalink / raw) Cc: ding Hi Laura, I must say that I find your criticism of the handling of XEmacs bug reports a bit harsh. Laura Conrad <lconrad@world.std.com> writes: > >>>>> "Pieter" == Pieter Wenk <pwenk@urbanet.ch> writes: > > Pieter> Secondly, assuming, that I have a buggy xemacs what is to > Pieter> do that this nifty app stops crashing ? > > Another thing they used to do (I'm sure present company has nothing to > do with this particular bug report handling) is tell you your crashes > are because your machine doesn't have enough memory. Hm, I guess this 'they' refers to me as I answered your two bug reports concerning the crashes when running out of memory. I am sorry if I sounded rude. I'd like you to consider that we do get quite a lot of bug reports (about 1000 since I started sorting them) and many are not really very helpful (my favourites are the mails only containing 'it crashed.' and 'Yeah men , great BUG in' respectively). Many of our users are also neither willing nor able to provide useful further information when asked. You have no idea how many unanswered requests for information concerning bug reports I have written. Then there is also the issue of people being too stupid to configure their MUA/MTAs to produce emails that contain an address that actually leads back to their mailbox (i.e. often my replies bounce which is very frustrating indeed). Oh, did I mention those helpful folks that only send us a copy of the crash message we print to their console but NOTHING else, or the uuencoded 30MB coredumps... The user community of XEmacs is significantly larger than the Gnus community and many of our users are not nearly as clued as Larsi's users are. All this leads to the fact that I tend to not spend hours replying to one particular report and explaining the problem in detail if the situation is more or less clear (to me) or clearly hopeless. Errm, sorry, rant over. :-) > Probably some of the crashes I see that the developers don't are > because my machine has only 32M. I seriously doubt that. The amount of physical memory shouldn't be relevant for the stability of xemacs (only for its performance). FWIW my private machine has only 40MB RAM (and used to have 24MB for quite some time). OTOH if you run out of virtual memory you will get serious problems and when this happens inside some critical part of xemacs (e.g. redisplay as in your two cases) we currently crash. I consider that a problem and therefore sorted your report into the 'enhancements' category, which contains stuff I plan to look at again. To be honest I also considered the possibility that you had misconfigured your system and had not actually activated your swap space (128MB according to your mail) as I doubt that xemacs can exhaust 160MB of memory in normal usage. Concerning the the other report you sent ('^' in NNTP passwords) I tagged that as a Gnus bugs and as it was also mailed to ding@gnus.org didn't take any further action. Your mail also contained evidence of a real XEmacs crash (the Lisp backtrace and our crash message) but as you couldn't find the core dump there wasn't much we could do much to diagnose that problem. I'm sorry if you were frustrated by our handling of your bug reports and hope you will nevertheless continue to submit reports if you encounter crashes. I do admit that the current system is far from optimal but I do think it is an improvement over the old state of affairs (where mail to crashes@xemacs.org was mostly piped to /dev/null AFAICT). Gunnar. -- Gunnar Evermann Speech, Vision & Robotics Group Cambridge University Engineering Department ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Re: ERROR AGAIN !! 1999-11-16 12:27 ` Laura Conrad 1999-11-16 13:54 ` Gunnar Evermann @ 1999-11-16 20:12 ` Pieter Wenk 1 sibling, 0 replies; 22+ messages in thread From: Pieter Wenk @ 1999-11-16 20:12 UTC (permalink / raw) On mar, 16 nov 1999, Laura Conrad wrote: Hello Laura >Another thing they used to do (I'm sure present company has nothing to >do with this particular bug report handling) is tell you your crashes >are because your machine doesn't have enough memory. Probably some >of the crashes I see that the developers don't are because my machine >has only 32M. Ok. Shall establish the bug report. I found the file. With regards to any fancy ideas of lack in memory. I run a 586 machine with 64 RAM. Will move next week to 128 RAM. I guess this should be enough fulfilling Xemacs/gnus rather heavy requirements in resources. Regards -- / / (_)____ __ ____ __ Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland /____/_/_//_/\_,_/ /_/\_\ ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: Re: ERROR AGAIN !! 1999-11-15 19:22 ` Laura Conrad 1999-11-15 20:06 ` Lars Magne Ingebrigtsen 1999-11-15 22:59 ` Jan Vroonhof @ 1999-11-17 15:20 ` Pieter Wenk 1999-11-17 15:52 ` Hrvoje Niksic 1999-11-17 17:08 ` ERROR AGAIN !! (PR#1023) Jan Vroonhof 2 siblings, 2 replies; 22+ messages in thread From: Pieter Wenk @ 1999-11-17 15:20 UTC (permalink / raw) On lun, 15 nov 1999, Laura Conrad wrote: >>>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@gnus.org> writes: > > Lars> Well, it looks like an XEmacs bug, so you should report it > Lars> to the XEmacs maintainers. OK I have sent this bug report. Was however unable to do it the right way. No idea what was ment with "category"...Coco nuts, beans ??? I finaly copied just the whole thing and sent it through mutt to the indicated address. Why are these folks at xemacs not making thinks easier ? Since aparantly this file is saves somewere...why not just a button...the the whole thing is just copied correctly.... Fine, and now what's going to happen... FYI: I just experienced an hour ago again the same Error..on a group I thought is not triggering anymore this error. I did just hit "c".... Regards -- / / (_)____ __ ____ __ Pieter Wenk / /__/ / _ \/ // /\ \/ / Vevey/Switzerland /____/_/_//_/\_,_/ /_/\_\ ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-17 15:20 ` Pieter Wenk @ 1999-11-17 15:52 ` Hrvoje Niksic 1999-11-17 17:08 ` ERROR AGAIN !! (PR#1023) Jan Vroonhof 1 sibling, 0 replies; 22+ messages in thread From: Hrvoje Niksic @ 1999-11-17 15:52 UTC (permalink / raw) Pieter Wenk <pwenk@urbanet.ch> writes: > No idea what was ment with "category"...Coco nuts, beans ??? [...] > Why are these folks at xemacs not making thinks easier ? Like anyone else, we are volunteers. The send-pr thing sounded like a good idea at the time. If you find it cumbersome, just go ahead and post to comp.emacs.xemacs, or send mail to <xemacs-beta@xemacs.org>. ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! (PR#1023) 1999-11-17 15:20 ` Pieter Wenk 1999-11-17 15:52 ` Hrvoje Niksic @ 1999-11-17 17:08 ` Jan Vroonhof 1 sibling, 0 replies; 22+ messages in thread From: Jan Vroonhof @ 1999-11-17 17:08 UTC (permalink / raw) Cc: xemacsbugs Pieter Wenk <pwenk@urbanet.ch> writes: > OK I have sent this bug report. Was however unable to do it the right > way. In particular you didn't include a C backtrace. Without it we cannot help you very much. You must try include as must information into your bug report as possible. > > No idea what was ment with "category"...Coco nuts, beans ??? That send-pr script is really stupid. I agree it should be ditched. > Since aparantly this file is saves somewere...why not > just a button... What file do you mean? The closest thing to a button that we have is Help->Send Bug Report. > Fine, and now what's going to happen... You'll be requested for more info. Because we really cannot see anything from just the lisp crash. So far you haven't mentioned the XEmacs version you are using, how it was compiled and etc. If you are not using 21.1.8, then could you please try with that version? So please obtain a C backtrace. There are two methods 1. Run XEmacs under gdb, i.e. gdb `which xemacs` run <when XEmacs crashes, type> where 2. You need to make sure you get coredumps. Type unlimit coredumpsize in csh,tcsh, or ulimit -c unlimited in bash,ksh,zsh,... then you'll see a 'core' file after a crag? Then send that also and include the output of M-x describe-installation. Jan ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-12 13:36 ERROR AGAIN !! Pieter Wenk 1999-11-15 19:15 ` Lars Magne Ingebrigtsen @ 1999-11-15 23:06 ` Jan Vroonhof 1999-11-16 9:17 ` Lars Magne Ingebrigtsen 1 sibling, 1 reply; 22+ messages in thread From: Jan Vroonhof @ 1999-11-15 23:06 UTC (permalink / raw) Pieter Wenk <pwenk@urbanet.ch> writes: > insert-file-contents-internal("/home/p.wenk/News/" nil nil nil nil undecided used-codesys) > byte-code("ÀÁ\n Lars Magne Ingebrigtsen <larsi@gnus.org> writes: > Well, it looks like an XEmacs bug, so you should report it to the > XEmacs maintainers. I think it is both. Why is Gnus calling insert-file-contents on a directory? Jan ^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: ERROR AGAIN !! 1999-11-15 23:06 ` ERROR AGAIN !! Jan Vroonhof @ 1999-11-16 9:17 ` Lars Magne Ingebrigtsen 0 siblings, 0 replies; 22+ messages in thread From: Lars Magne Ingebrigtsen @ 1999-11-16 9:17 UTC (permalink / raw) Jan Vroonhof <vroonhof@math.ethz.ch> writes: > Pieter Wenk <pwenk@urbanet.ch> writes: > > > insert-file-contents-internal("/home/p.wenk/News/" nil nil nil nil undecided used-codesys) > > byte-code("ÀÁ\n > > Lars Magne Ingebrigtsen <larsi@gnus.org> writes: > > > Well, it looks like an XEmacs bug, so you should report it to the > > XEmacs maintainers. > > I think it is both. Why is Gnus calling insert-file-contents on a directory? Well, if XEmacs hadn't crashed, then we could have gotten a proper Lisp backtrace, so we could find out why. :-) -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen ^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~1999-11-22 21:40 UTC | newest] Thread overview: 22+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 1999-11-12 13:36 ERROR AGAIN !! Pieter Wenk 1999-11-15 19:15 ` Lars Magne Ingebrigtsen 1999-11-15 19:22 ` Laura Conrad 1999-11-15 20:06 ` Lars Magne Ingebrigtsen 1999-11-15 22:59 ` Jan Vroonhof 1999-11-16 7:44 ` Pieter Wenk 1999-11-16 8:35 ` Hrvoje Niksic 1999-11-17 8:36 ` Pieter Wenk 1999-11-20 12:38 ` Pieter Wenk 1999-11-20 15:01 ` Michael Klingbeil 1999-11-20 22:25 ` Kai Großjohann 1999-11-20 22:38 ` Pieter Wenk 1999-11-20 23:13 ` Kai Großjohann 1999-11-22 21:40 ` Aaron M. Ucko 1999-11-16 12:27 ` Laura Conrad 1999-11-16 13:54 ` Gunnar Evermann 1999-11-16 20:12 ` Pieter Wenk 1999-11-17 15:20 ` Pieter Wenk 1999-11-17 15:52 ` Hrvoje Niksic 1999-11-17 17:08 ` ERROR AGAIN !! (PR#1023) Jan Vroonhof 1999-11-15 23:06 ` ERROR AGAIN !! Jan Vroonhof 1999-11-16 9:17 ` Lars Magne Ingebrigtsen
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).