From: issdr <p_u_n_k_i_n_d@yahoo.it>
Subject: Re: Changing signing key
Date: 3 Jul 2006 05:19:04 GMT [thread overview]
Message-ID: <ulkrbs1x7.fsf@ID-219024.news.uni-berlin.de> (raw)
In-Reply-To: <87psgnae1a.fsf@janni.cybervalley.org>
leandro noferini wrote:
>> ((add-to-list 'gnus-newsgroup-variables 'pgg-default-user-id))
>
> It seems to work good!
>
> Only one little thing: the line above is only with one parenthesis
>
> (add-to-list 'gnus-newsgroup-variables 'pgg-default-user-id)
yes, that's correct. sometimes i use dabbrev blindly...
>> in my `.gnus.el' file. (see (info "(gnus)group parameters") to understand
>> why)
>
> I could not understand.
,----
| `(VARIABLE FORM)'
| You can use the group parameters to set variables local to the
| group you are entering. If you want to turn threading off in
| `news.answers', you could put `(gnus-show-threads nil)' in the
| group parameters of that group. `gnus-show-threads' will be made
| into a local variable in the summary buffer you enter, and the
| form `nil' will be `eval'ed there.
|
| Note that this feature sets the variable locally to the summary
| buffer. But some variables are evaluated in the article buffer,
| or in the message buffer (of a reply or followup or otherwise
| newly created message). As a workaround, it might help to add the
| variable in question to `gnus-newsgroup-variables'. *Note Various
| Summary Stuff::. So if you want to set `message-from-style' via
| the group parameters, then you may need the following statement
| elsewhere in your `~/.gnus' file:
|
| (add-to-list 'gnus-newsgroup-variables 'message-from-style)
`----
--
np: no song
prev parent reply other threads:[~2006-07-03 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-12 11:17 leandro noferini
2006-06-20 17:16 ` Reiner Steib
2006-07-02 4:17 ` leandro noferini
2006-07-02 8:13 ` issdr
2006-07-02 22:16 ` leandro noferini
2006-07-03 5:19 ` issdr [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=ulkrbs1x7.fsf@ID-219024.news.uni-berlin.de \
--to=p_u_n_k_i_n_d@yahoo.it \
/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).