Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: registry and the gnus-summary-line-format
Date: Sun, 19 Feb 2017 17:06:14 -0800	[thread overview]
Message-ID: <87fuj96589.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87wpcl3lee.fsf@mat.ucm.es>

Uwe Brauer <oub@mat.ucm.es> writes:

> Hi according to the documentation of gnus-registry.el
> I should add ;; Finally, you can put %uM in your summary line format to
> show the registry.
>
> now in the relevant custom buffer using  gnus-group-customize
> I have 
>
> Set variables local to the group you are entering. More
> INS DEL Variable: gnus-summary-line-format
>             Value: 
> "%uM%U%R%z%I%N %(%[ %-10,10uB%]%) %-10,10~(form (rfc2047-decode-string (gnus-extra-header 'To)))@  [%-25,25s%] %D %k %L   \n"
> INS
>
> but gnus-summary-line-format is a variable defined in ‘gnus.el’.
> Its value is "%U%R%z%I%(%[%4L: %-23,23f%]%) %s
> "
>
> I don't understand that, can somebody please explain?

I'm not entirely sure what you're asking, but you have two options here:
set a global gnus-summary-line-format variable, that applies to all
groups, and also set a per-group (ie "group local") summary line that
only applies to that one group, and overrides the global value.

In the customization "screenshots" above, the top entry is specific to
one group. The second is the value that applies to all groups.

If that doesn't clear things up, you might need to rephrase your
question!

Yours,
Eric




  reply	other threads:[~2017-02-20  1:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-19 21:45 Uwe Brauer
2017-02-20  1:06 ` Eric Abrahamsen [this message]
2017-02-21 12:01   ` Uwe Brauer
2017-02-21 16:28     ` Eric Abrahamsen
2017-02-21 18:18       ` Uwe Brauer
2017-02-21 18:23       ` Uwe Brauer
2017-02-21 18:32         ` Eric Abrahamsen
2017-02-21 20:08           ` Uwe Brauer
2017-02-22  0:34             ` Eric Abrahamsen
2017-02-22  9:25               ` Uwe Brauer
2017-02-22 16:59                 ` Eric Abrahamsen
2017-02-22 17:38                   ` Uwe Brauer
2017-02-21 21:49           ` Uwe Brauer

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=87fuj96589.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).