From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: [RFC] Gnus generalized search, part II
Date: Sat, 29 Apr 2017 17:20:19 -0400 [thread overview]
Message-ID: <8637cqnc6k.fsf@local.lan> (raw)
In-Reply-To: <87r30dz618.fsf@hanan>
Andrew Cohen <cohen@bu.edu> writes:
>> Ohh, uhm, forgot to mention:) You have to put the spec in the
>> gnus-summary-line-format variable instead of the old nnir specific one
>> (which has gone away). This spec will be happily ignored in normal
>> groups (%g for short group name and %G for the full name).
Eric A
> Aha! I was led astray by the presence of the
> nnselect-summary-line-format variable. :)
Sorry to bog things down to something probably trivial. But could one
of you spell out a bit more what this `spec' is?
My summary line format is a long string of char that I pieced together
about a hundred yrs ago, haven't thought much about since, and are now
mainly mystifying.
Is it upper or lower case `g' as would seem to be what Andrew C
suggests or something more?
(setq gnus-summary-line-format "%O%2t%U%R%7d%z%I%(%[%4L: %-20,20f%]%) %s\n")
next prev parent reply other threads:[~2017-04-29 21:20 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 21:35 Eric Abrahamsen
2017-04-22 0:16 ` Andrew Cohen
2017-04-22 7:50 ` Eli Zaretskii
2017-04-22 8:00 ` Andrew Cohen
2017-04-22 19:53 ` Lars Ingebrigtsen
2017-04-22 20:26 ` Eric Abrahamsen
2017-04-24 20:30 ` Eric Abrahamsen
2017-04-26 4:41 ` Andrew Cohen
2017-04-26 6:31 ` Adam Sjøgren
2017-04-26 7:39 ` Saša Janiška
2017-04-26 16:07 ` Eric Abrahamsen
2017-04-26 9:21 ` Joakim Jalap
2017-04-26 15:51 ` Eric Abrahamsen
[not found] ` <7e7ccca805864b5398551cc74123df11@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
[not found] ` <87k2653oum.fsf@delle7240>
2017-04-27 19:35 ` Eric Abrahamsen
2017-04-28 1:18 ` Andrew Cohen
[not found] ` <cb06d28e83ab4a6cab1b3cd02fc7e554@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
[not found] ` <87zif16j2t.fsf@delle7240>
2017-04-28 9:16 ` Andrew Cohen
2017-04-26 8:18 ` Andrew Cohen
2017-04-26 16:37 ` Eric Abrahamsen
2017-04-26 22:31 ` Eric Abrahamsen
2017-04-27 4:27 ` Andrew Cohen
2017-04-27 18:22 ` Eric Abrahamsen
2017-04-28 1:15 ` Andrew Cohen
2017-04-28 18:23 ` Eric Abrahamsen
2017-04-28 20:52 ` Eric Abrahamsen
2017-04-28 23:26 ` Andrew Cohen
2017-04-29 3:57 ` Eric Abrahamsen
2017-04-29 9:37 ` Andrew Cohen
2017-04-30 5:13 ` Eric Abrahamsen
2017-04-28 23:34 ` Andrew Cohen
2017-04-29 4:16 ` Eric Abrahamsen
2017-04-29 21:20 ` Harry Putnam [this message]
2017-04-30 0:15 ` Andrew Cohen
2017-04-26 17:50 ` Eric Abrahamsen
2017-04-26 8:22 ` Andrew Cohen
2017-04-23 13:48 ` Dan Christensen
2017-04-23 17:19 ` Eric Abrahamsen
2017-04-23 17:59 ` Dan Christensen
2017-04-23 23:22 ` Eric Abrahamsen
2017-04-24 1:37 ` Dan Christensen
2017-04-24 21:02 ` Eric Abrahamsen
2017-06-10 4:46 ` Eric Abrahamsen
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=8637cqnc6k.fsf@local.lan \
--to=reader@newsguy.com \
--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).