Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: jason haslup <jason@haslup.com>
Subject: Re: displaying initial words in a summary line (like gmail)
Date: Wed, 30 Mar 2005 11:23:37 -0700	[thread overview]
Message-ID: <1112207025.1602f81d408e5e16c9390e047a8f10ba@teranews> (raw)
In-Reply-To: <r77psxnhady.fsf@muscadet.inria.fr>

James Leifer <James.Leifer@inria.fr> writes:

> Hello,
>
> I was reading the doc for gnus-summary-line-format, but couldn't find
> an answer to my question.
>
> When visually scanning the summary buffer I would find it useful to
> see the first couple of words of each message.  Those who use Google
> gmail might have noticed that this makes it far faster to identify to
> the missed spams in the inbox and the missed hams in the spambox.
>
> Any ideas?
>

I think you need to somehow get that info into the .overview file (if
you're using nnml).

I do this with procmail and a perl script which adds an 'X-Blurb'
header to all my incoming mail.  Then add X-Blurb to gnus' interesting
headers variables so that it's included in the .overview file (i'm
using nnml).

I'm sure there's a hook that I could have used, now that I think about
it more.  It might be nicer if gnus actually added the header or entry
in the .overview file.  My perl script ignores mime messages since it
doesn't decode it, gnus might actually be able to extract the first
line from inside those messages.

jason


           reply	other threads:[~2005-03-30 18:23 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <r77psxnhady.fsf@muscadet.inria.fr>]

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=1112207025.1602f81d408e5e16c9390e047a8f10ba@teranews \
    --to=jason@haslup.com \
    /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).