Gnus development mailing list
 help / color / mirror / Atom feed
From: alfred@GlobeSet.com (Alfred J Correira)
Subject: using multiple Summary buffer formats
Date: 14 Jan 1999 18:53:35 -0600	[thread overview]
Message-ID: <usoddz78w.fsf@GlobeSet.Com> (raw)
In-Reply-To: Richard Coleman's message of "Mon, 11 Jan 1999 18:51:57 -0500"

I've been poking around in the documentation on the Summary buffer for a way to
do the following, but I just don't see how to do it simply.  Namely, I would
like to have one Summary buffer format for all my groups, except my outgoing
group (the GCC: group); I would like that one to use a format that displayed,
say, the first To: address rather than the usual From: (they're all from me,
after all :-).  It looks like perhaps I could make up my own function to bind
to the gnus-extract-address-components variable, one that checks for my GCC
group and does something different than the usual predefined functions when I'm
in that group, but that feels wrong to me somehow.  Am I missing some obvious
existing mechanism that supports what I want to do?

(This would for pgnus v0.69 ...)

-- 
Work: Alfred.Correira@GlobeSet.Com  PH: 512.427.7715
Home: Correira@Flash.Net           FAX: 512.427.5101
PGP: 55 42 BB 2E 17 E9 0D 9C 0B 51 66 58 58 96 1E 45



  parent reply	other threads:[~1999-01-15  0:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <feoh@cosmic.com>
1999-01-11 22:08 ` Pre-Processed maiil splitting under Gnus? Asymptotically Approaching Relaxation
1999-01-11 23:51   ` Richard Coleman
1999-01-12  7:00     ` Asymptotically Approaching Relaxation
1999-01-15  0:53     ` Alfred J Correira [this message]
1999-01-15 10:23       ` using multiple Summary buffer formats Kai.Grossjohann
1999-01-15 10:35         ` Lee Willis
1999-01-15 11:13           ` Kai.Grossjohann
     [not found]             ` <lzww2o21ez.fsf@landlord.gbdirect.co.uk>
     [not found]               ` <vaf7luon2dv.fsf@ramses.cs.uni-dortmund.de>
1999-01-15 12:34                 ` Kai.Grossjohann
1999-01-15 13:04                   ` Lee Willis
1999-01-15 14:27                     ` Karl Kleinpaste
1999-01-19 14:54                       ` Jack Vinson
1999-01-19 15:15                         ` Lee Willis
     [not found]   ` <m3iuedcuua.fsf@peorth.gweep.net>
1999-01-12  7:57     ` Pre-Processed maiil splitting under Gnus? Asymptotically Approaching Relaxation
1999-01-12 16:02       ` Kai.Grossjohann
1999-01-12 16:38         ` Hrvoje Niksic
1999-01-12 17:00           ` M-x gnus-filter-mail-at-warp-10 (was: Re: Pre-Processed maiil splitting under Gnus?) Asymptotically Approaching Relaxation
1999-01-12 17:35             ` Kai.Grossjohann
1999-01-12 18:42               ` Asymptotically Approaching Relaxation
1999-01-13 22:35                 ` Kai.Grossjohann
1999-01-12 20:49             ` M-x gnus-filter-mail-at-warp-10 (was: " Jari Aalto+mail.procmail
1999-01-13 22:32               ` Kai.Grossjohann
1999-01-13 23:21                 ` Hrvoje Niksic
1999-01-12 17:21           ` Pre-Processed maiil splitting under Gnus? Lars Magne Ingebrigtsen

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=usoddz78w.fsf@GlobeSet.Com \
    --to=alfred@globeset.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).