Gnus development mailing list
 help / color / mirror / Atom feed
From: Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich <Peter.Weiss@germany.sun.com>
Cc: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann), ding@gnus.org
Subject: Re: group specific headers headers
Date: 19 Jun 2000 15:55:36 +0200	[thread overview]
Message-ID: <xpxyhfapbwrr.fsf@Germany.Sun.com> (raw)
In-Reply-To: Jorge Godoy's message of "19 Jun 2000 10:19:32 -0300"

>>>>> On 19 Jun 2000 10:19:32 -0300, Jorge Godoy <godoy@conectiva.com> said:

Jorge> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>> Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich <Peter.Weiss@germany.sun.com> writes:
>> 
>> >     a task that I'd like to do is to set a special header field in a group
>> >     related way (e.g. when sending from some groups I need a Reply-To-Field
>> >     set up, on others not).
>> 
>> Posting styles are your friend.

Jorge> Ok... I've looked after them and couldn't find it. 

Jorge> Could you give me some pointer to the info page?

Using Gnus v5.8.7 the info page is the following;

File: gnus,  Node: Posting Styles,  Next: Drafts,  Prev: Archived Messages,  Up: Composing Messages

Posting Styles
==============

   All them variables, they make my head swim.

   So what if you want a different `Organization' and signature based
on what groups you post to?  And you post both from your home machine
and your work machine, and you want different `From' lines, and so on?

   One way to do stuff like that is to write clever hooks that change
the variables you need to have changed.  That's a bit boring, so
somebody came up with the bright idea of letting the user specify these
things in a handy alist.  Here's an example of a `gnus-posting-styles'
variable:

     ((".*"
       (signature "Peace and happiness")
       (organization "What me?"))
      ("^comp"
       (signature "Death to everybody"))
      ("comp.emacs.i-love-it"
       (organization "Emacs is it")))

   As you might surmise from this example, this alist consists of
several "styles".  Each style will be applicable if the first element
"matches", in some form or other.  The entire alist will be iterated
over, from the beginning towards the end, and each match will be
applied, which means that attributes in later styles that match override
the same attributes in earlier matching styles.  So
`comp.programming.literate' will have the `Death to everybody'
signature and the `What me?' `Organization' header.

   The first element in each style is called the `match'.  If it's a
string, then Gnus will try to regexp match it against the group name.
If it is the symbol `header', then Gnus will look for header that match
the next element in the match, and compare that to the last header in
the match.  If it's a function symbol, that function will be called
with no arguments.  If it's a variable symbol, then the variable will be
referenced.  If it's a list, then that list will be `eval'ed.  In any
case, if this returns a non-`nil' value, then the style is said to
"match".

   Each style may contain a arbitrary amount of "attributes".  Each
attribute consists of a `(NAME . VALUE)' pair.  The attribute name can
be one of `signature', `signature-file', `organization', `address',
`name' or `body'.  The attribute name can also be a string.  In that
case, this will be used as a header name, and the value will be
inserted in the headers of the article; if the value is `nil', the
header name will be removed.  If the attribute name is `eval', the form
is evaluated, and the result is thrown away.

   The attribute value can be a string (used verbatim), a function with
zero arguments (the return value will be used), a variable (its value
will be used) or a list (it will be `eval'ed and the return value will
be used).  The functions and sexps are called/`eval'ed in the message
buffer that is being set up.  The headers of the current article are
available through the `message-reply-headers' variable.

   If you wish to check whether the message you are about to compose is
meant to be a news article or a mail message, you can check the values
of the `message-news-p' and `message-mail-p' functions.

   So here's a new example:

     (setq gnus-posting-styles
           '((".*"
              (signature-file "~/.signature")
              (name "User Name")
              ("X-Home-Page" (getenv "WWW_HOME"))
              (organization "People's Front Against MWM"))
             ("^rec.humor"
              (signature my-funny-signature-randomizer))
             ((equal (system-name) "gnarly")
              (signature my-quote-randomizer))
             ((message-news-p)
              (signature my-news-signature))
             (header "From.*To" "larsi.*org"
              (Organization "Somewhere, Inc."))
             ((posting-from-work-p)
              (signature-file "~/.work-signature")
              (address "user@bar.foo")
              (body "You are fired.\n\nSincerely, your boss.")
              (organization "Important Work, Inc"))
             ("^nn.+:"
              (signature-file "~/.mail-signature"))))

    Hth -- Peter

-- 
Peter Weiss 

CLASS Firmengruppe           phone  +49 (0)8151 / 991 - 512
Moosstrasse 7                fax    +49 (0)8151 / 991 - 229
D-82319 Starnberg            mobil  0172/ 83 79 125
http://www.class.de          mailto:Peter.Weiss@Class.de



      reply	other threads:[~2000-06-19 13:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-15 13:42 Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich
2000-06-15 14:32 ` Kai Großjohann
2000-06-19 13:19   ` Jorge Godoy
2000-06-19 13:55     ` Peter Weiss - Sun Germany ENS Engineer Mission Critical - Munich [this message]

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=xpxyhfapbwrr.fsf@Germany.Sun.com \
    --to=peter.weiss@germany.sun.com \
    --cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
    --cc=Peter.Weiss@Class.De \
    --cc=ding@gnus.org \
    /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).