From: Emerick Rogul <emerick@cs.bu.edu>
Subject: Re: How do I get no signature in particular groups?
Date: 23 Nov 1999 01:49:22 -0500 [thread overview]
Message-ID: <vuoiu2taej1.fsf@csa.bu.edu> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of "12 Nov 1999 06:50:22 +0100"
Lars Magne Ingebrigtsen writes:
: Emerick Rogul <emerick@cs.bu.edu> writes:
:: In some newsgroups I'm subscribed to, I don't want any signature at
:: all to be appended to my messages. I tried adding (message-signature
:: nil) to my group parameters, but nothing happened. I also tried
:: adding (signature nil) and (signature "") to that group's
:: posting-style. Setting it to nil did nothing; setting it to "" was
:: closer, but I was still getting the signature separator at the end of
:: my message.
: I think I've located and fixed this bug. Could you check after
: Pterodactyl Gnus v0.99 has been released to see whether things start
: working?
I've now tested this with the latest pGnus 0.99 in CVS (as of
11/23/1999) and it still doesn't seem quite right (either that, or I'm
doing something completely wrong :).
I have the following in my .gnus file:
(setq gnus-posting-styles
'((".*"
(signature-file "~/.my-sig"))))
This will use my standard signature in all groups, and that works
fine. In one particular group where I don't want to use a signature,
I've added the following to the group parameters:
(posting-style
(signature nil))
This still appended my signature to new messages. I then tried the
following:
(posting-style
(signature-file nil))
but this caused an error (pgnus is expecting a string, I suppose).
Finally, I tried the following which did what I wanted (no signature
for that particular group) but seemed unintuitive:
(posting-style
(signature t))
If I'm doing something wrong, please let me know, but I think I've
correctly followed all of the instructions in the manual.
-Emerick
--
-------------------------------------------------------------------------
Emerick Rogul /\/ "...painted portraits of minions and slaves,
emerick@cs.bu.edu /\/ crotch mavens and one-night plays..."
-------------------------------------------------------- 'here', pavement
next prev parent reply other threads:[~1999-11-23 6:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-10 19:11 Emerick Rogul
1999-11-12 5:50 ` Lars Magne Ingebrigtsen
1999-11-14 14:23 ` Turbo Fredriksson
1999-11-15 0:01 ` Stephen Zander
1999-11-15 10:33 ` Turbo Fredriksson
1999-11-15 19:50 ` Lars Magne Ingebrigtsen
1999-11-16 11:19 ` Turbo Fredriksson
1999-11-16 17:03 ` Lars Magne Ingebrigtsen
1999-11-17 13:21 ` Turbo Fredriksson
1999-12-01 15:51 ` Lars Magne Ingebrigtsen
1999-12-02 11:14 ` Turbo Fredriksson
1999-12-06 4:05 ` Lars Magne Ingebrigtsen
1999-11-17 1:27 ` Rupa Schomaker (list)
1999-11-23 6:49 ` Emerick Rogul [this message]
1999-11-23 21:39 ` Kai Großjohann
1999-12-01 15:54 ` Lars Magne Ingebrigtsen
1999-12-01 17:18 ` Emerick Rogul
1999-12-01 22:54 ` Lars Magne Ingebrigtsen
1999-12-02 1:25 ` Emerick Rogul
1999-12-06 4:04 ` Lars Magne Ingebrigtsen
1999-12-06 5:36 ` Emerick Rogul
2000-04-21 20:28 ` Lars Magne Ingebrigtsen
2000-04-21 22:29 ` Emerick Rogul
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=vuoiu2taej1.fsf@csa.bu.edu \
--to=emerick@cs.bu.edu \
/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).