From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: gnus+qmail: set envelope sender?
Date: Sun, 15 Sep 2002 16:54:38 +0200 [thread overview]
Message-ID: <vafy9a3s3pt.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <y9a4cv0c.fsf@ID-23066.news.dfncis.de> (Clemens Fischer's message of "Sat, 14 Sep 2002 19:59:31 +0200")
Clemens Fischer <ino@despammed.com> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Grojohann) writes:
>
>>> (address
>>> (cadr (setq message-qmail-inject-args `("-f" ,user-mail-address))))
>>> )
>>
>> I think that's not a good idea. I think you can set local variables
>> from posting styles. Why not use that feature?
>
> but that's what i'm doing!
No, you're executing Lisp code by side-effect from a place where this
is not intended to happen.
> also, the info page states that attributes in list-form get eval'ed.
Yes. I'm not saying it doesn't work, I'm saying it's bad style.
It's like avoiding "goto" in imperative programming languages.
>> You might have to add message-qmail-inject-args to
>> gnus-newsgroup-variables, though.
>
> well, to be honest, i don't know which of these features i can trust
> more, and i have this strong feeling towards keeping related stuff in
> one place.
Well, you can put the two Lisp statements together in your .gnus...
kai
--
~/.signature is: umop 3p!sdn (Frank Nobis)
prev parent reply other threads:[~2002-09-15 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-12 2:45 clemens fischer
2002-09-12 8:41 ` Kai Großjohann
2002-09-12 9:59 ` Frank Tegtmeyer
2002-09-12 15:23 ` Paul Jarc
2002-09-12 23:21 ` Clemens Fischer
2002-09-13 19:58 ` signature separator (was: " Paul Jarc
2002-09-16 11:36 ` signature separator Reiner Steib
2002-09-13 20:25 ` gnus+qmail: set envelope sender? Kai Großjohann
2002-09-14 17:59 ` Clemens Fischer
2002-09-15 14:54 ` Kai Großjohann [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=vafy9a3s3pt.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).