Gnus development mailing list
 help / color / mirror / Atom feed
From: Wes Hardaker <Wesley.Hardaker@sphys.unil.ch>
Subject: Re: Disabling scoring for a group
Date: 07 Mar 1997 08:48:16 +0100	[thread overview]
Message-ID: <qk2209sb0sf.fsf@iptsun2.unil.ch> (raw)
In-Reply-To: Per Abrahamsen's message of 06 Mar 1997 14:41:57 +0100

>>>>> In article <rj3eu9yw62.fsf@zuse.dina.kvl.dk>, Per Abrahamsen <abraham@dina.kvl.dk> writes:

Per> COMMERCIAL BREAK -- COMMERCIAL BREAK -- COMMERCIAL BREAK -- COMMERCIAL BREAK

A> Oh no, now I have again wasted an evening trying to set group
A> parameters in Gnus!

B> I know!  I used to have the same problem, but then I found `G c'!

B> Did you know that using `G c' in the group buffer to set group
B> parameters, will avoid most of these silly syntactical errors?

A> No, really?  I must try that!

Per> <next day>

A> Hi B!  Thank you!  After I started using `G c' my laundry is whiter
A> than the whitest...

Per> COMMERCIAL BREAK -- COMMERCIAL BREAK -- COMMERCIAL BREAK -- COMMERCIAL BREAK

DEVILS ADVOCATE BREAK -- DEVILS ADVOCATE BREAK -- DEVILS ADVOCATE BREAK

But:

Unknown entries:
[INS] [DEL] Lisp expression:  (total-expire)
[INS]

This entry should have been a specifically turned off total-expire
(say, if you have the total-expire variable turned on or the
total-expire param in a topic the group is in.  This should turn it
off).

Also, for that matter, how do you edit the topic parameters???  You're
customize thing only works on groups.

DEVILS ADVOCATE BREAK -- DEVILS ADVOCATE BREAK -- DEVILS ADVOCATE BREAK


;-)
Wes


  reply	other threads:[~1997-03-07  7:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-28 10:35 Preformatting features of Emacs Hrvoje Niksic
1997-02-28 11:32 ` Per Abrahamsen
1997-02-28 14:12   ` Steinar Bang
1997-03-03  9:31     ` Robert Bihlmeyer
1997-02-28 16:31   ` Hrvoje Niksic
1997-02-28 15:37 ` David Blacka
1997-03-03 11:51   ` Lars Balker Rasmussen
1997-02-28 20:37 ` Paul Franklin
1997-02-28 22:17   ` Hrvoje Niksic
1997-02-28 23:26     ` Stainless Steel Rat
1997-02-28 23:58       ` Jason L Tibbitts III
1997-03-01  0:57         ` Sudish Joseph
1997-03-01  2:05           ` Alan Shutko
1997-03-01  2:53             ` Paul Franklin
1997-03-01 21:45               ` Jason L Tibbitts III
1997-03-01 23:15                 ` C. R. Oldham
1997-03-02 23:24                   ` Alan Shutko
1997-03-01  3:02         ` filladapt.el Stainless Steel Rat
1997-03-05 15:58           ` Disabling scoring for a group C. R. Oldham
1997-03-05 17:15             ` Hrvoje Niksic
1997-03-05 19:08               ` C. R. Oldham
1997-03-06 13:41                 ` Per Abrahamsen
1997-03-07  7:48                   ` Wes Hardaker [this message]
1997-03-07 12:41                     ` Per Abrahamsen
1997-03-01  5:52       ` Preformatting features of Emacs Hrvoje Niksic
1997-03-01  0:29     ` Sudish Joseph
1997-02-28 22:22   ` Sudish Joseph
1997-02-28 22:47     ` Per Abrahamsen
1997-02-28 23:56       ` Sudish Joseph
1997-03-01  0:21         ` Stephen Peters
1997-02-28 23:59       ` Sudish Joseph
1997-03-01  1:04         ` Lars Magne Ingebrigtsen
1997-03-01  1:53           ` Sudish Joseph
1997-03-01  2:13           ` Sudish Joseph
1997-03-01  2:17           ` Steven L Baur
1997-03-01  3:06             ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=qk2209sb0sf.fsf@iptsun2.unil.ch \
    --to=wesley.hardaker@sphys.unil.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).