| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
Here's a list of variables relevant to both mailing and posting:
gnus-mailing-list-groups
If your news server offers groups that are really mailing lists
gatewayed to the NNTP server, you can read those groups without
problems, but you can't post/followup to them without some difficulty.
One solution is to add a to-address to the group parameters
(see section 2.10 Group Parameters). An easier thing to do is set the
gnus-mailing-list-groups to a regexp that matches the groups that
really are mailing lists. Then, at least, followups to the mailing
lists will work most of the time. Posting to these groups (a) is
still a pain, though.
gnus-user-agent
This variable controls which information should be exposed in the
User-Agent header. It can be one of the symbols gnus (show only
Gnus version), emacs-gnus (show only Emacs and Gnus versions),
emacs-gnus-config (same as emacs-gnus plus system
configuration), emacs-gnus-type (same as emacs-gnus plus
system type) or a custom string. If you set it to a string, be sure to
use a valid format, see RFC 2616.
You may want to do spell-checking on messages that you send out. Or, if
you don't want to spell-check by hand, you could add automatic
spell-checking via the ispell package:
(add-hook 'message-send-hook 'ispell-message) |
If you want to change the ispell dictionary based on what group
you're in, you could say something like the following:
(add-hook 'gnus-select-group-hook
(lambda ()
(cond
((string-match
"^de\\." (gnus-group-real-name gnus-newsgroup-name))
(ispell-change-dictionary "deutsch"))
(t
(ispell-change-dictionary "english")))))
|
Modify to suit your needs.