Gnus development mailing list
 help / color / mirror / Atom feed
From: Nuutti Kotivuori <nuutti.kotivuori@smarttrust.com>
Cc: ding list <ding@gnus.org>
Subject: Re: spurious subject change (was: problem with gnus-summary-line-format.)
Date: Mon, 30 Jul 2001 12:45:42 +0300	[thread overview]
Message-ID: <87lml63g3d.fsf@smarttrust.com> (raw)
In-Reply-To: <vafy9p7zbyr.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sun, 29 Jul 2001 23:01:32 +0200")

Kai Großjohann wrote:
> On Sun, 29 Jul 2001, Nuutti Kotivuori wrote:
>> Kai Großjohann wrote:
>>> On Sun, 29 Jul 2001, Nuutti Kotivuori wrote:
>>>> Atleast for me, threads do change subjects even when not at
>>>> root. I gather threads by references.
>>> 
>>> I have no idea what the current tree building code will do when
>>> that happens.  Hm.  Lessee...
>> 
>> It works perfectly for me atleast. I see the new subject whenever
>> it changes, but the thread trees are intact. And %B summary format
>> ofcourse works fine.
> 
> No, no.  That's not what I'm talking about.  You can set
> gnus-sum-thread-tree-root to nil, then it will insert the subject.
> This way, you can put %B _without_ %s into the summary line format,
> and you will see a tree with subject.

Ah yes, you already talking about the %B tree building code. I thought
you meant the normal tree building, which was silly of me.

> But when the subject changes, that feature won't do the right thing.
> To get the right effect there, one needs to look if the subject has
> changed, and optionally append the subject to every node if this has
> happened.

In my opinion, the decision between showing the subject or not showing
the subject is not limited to just changing subjects and root. I, for
example, am a bit annoyed by the fact that when I'm reading news
articles, if the thread is long, I don't see the current subject from
it - I have to look at modeline or article headers, and both are far
away. So I might want "%S" and not "%s", so to speak. Or maybe
something even more complex, like showing the subject every 5 headers.

-- Naked


  parent reply	other threads:[~2001-07-30  9:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-28  7:24 problem with gnus-summary-line-format Maciej Matysiak
2001-07-28 11:34 ` Kai Großjohann
2001-07-28 20:09   ` Maciej Matysiak
2001-07-28 22:39     ` Nuutti Kotivuori
2001-07-28 23:13       ` spurious subject change (was: problem with gnus-summary-line-format.) Kai Großjohann
2001-07-28 23:25         ` Kai Großjohann
2001-07-28 23:29         ` Nuutti Kotivuori
2001-07-29 21:01           ` Kai Großjohann
2001-07-29 21:08             ` Maciej Matysiak
2001-07-29 22:02               ` Kai Großjohann
2001-07-30  9:45             ` Nuutti Kotivuori [this message]
2001-07-30 11:16               ` Kai Großjohann
2001-07-28 22:30   ` problem with gnus-summary-line-format Kai Großjohann
2001-07-28 22:59     ` Maciej Matysiak
2001-07-29 21:05       ` Kai Großjohann
2001-07-29 21:38         ` Maciej Matysiak
2001-08-23 17:15           ` Lars Magne Ingebrigtsen
2001-07-28 23:10     ` Kai Großjohann

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=87lml63g3d.fsf@smarttrust.com \
    --to=nuutti.kotivuori@smarttrust.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).