Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: gnus-article-browse-html-article: boundary, gnus-visible-headers
Date: Fri, 21 Mar 2008 13:46:48 +0100	[thread overview]
Message-ID: <v9iqzgtfbb.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mskykc3h7.fsf@jpl.org>

On Fri, Mar 21 2008, Katsumi Yamaoka wrote:

> I considered the main purpose to customize `gnus-visible-headers'
> on most people is to add some headers to view in the article buffer.
> Those will be for keeping watch on some headers or just for fun.

I agree.  Thanks for your explanations.

> I also considered that while it is meaningful in the article buffer,
> headers that `gnus-visible-headers' specifies by default are
> necessary and sufficient for general use.

Maybe it would make sense to add a new variable specifying the headers
used for commands like `gnus-article-browse-html-article' and
`gnus-summary-print-article' (do we have other, comparable commands)?
We should also bind `gnus-treat-date-lapsed' to nil for those, I
think.

The new variable (say `gnus-brief-headers'?) could have the following
values:

- (list of) regexp(s):

  Show specified headers.  The variable should be initialized from
  `gnus-saved-headers'.  The purpose seems similar.  Its default value
  is gnus-visible-headers.

  Maybe some headers present (and useful) in `gnus-visible-headers'
  should be removed from the default of `gnus-saved-headers' or only
  from the new variable, e.g. Gnus-Warning, X-Sent,
  (Mail-)?Followup-To, ...

- The symbol `current':

  Use the currently visible headers (like `gnus-summary-print-article'
  does it now)

- nil:

  Use `gnus-saved-headers'.

- t (or ...?):

  Use your implementation (but with `gnus-saved-headers'?).  (Does
  providing this still make sense if we have a dedicated variable?)

Opinions? 

> Sorry for the late response.

Late?  Less than one day?  :-)

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  reply	other threads:[~2008-03-21 12:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-20  9:59 Reiner Steib
2008-03-21  0:42 ` Katsumi Yamaoka
2008-03-21 12:46   ` Reiner Steib [this message]
2008-03-24  9:40     ` Katsumi Yamaoka
2008-03-28 12:21       ` Katsumi Yamaoka

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=v9iqzgtfbb.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).