Gnus development mailing list
 help / color / mirror / Atom feed
From: Neal H Walfield <neal@cs.uml.edu>
Cc: ding@gnus.org
Subject: Re: collapsed thread indicator change?
Date: Wed, 12 Sep 2001 18:01:53 +0200	[thread overview]
Message-ID: <87snds2ya6.fsf@bassanio.walfield.org> (raw)
In-Reply-To: <877kv41o1c.fsf@mogli.aximilation.org> (Martin Kretzschmar's message of "Wed, 12 Sep 2001 16:28:31 +0200")

Martin Kretzschmar <Martin.Kretzschmar@inf.tu-dresden.de> writes:

> Neal H Walfield <neal@cs.uml.edu> writes:
>
>>>> I didn't see this in the manual: can the collapsed thread indicator
>>>> [...] be changed?  It would be great if the left side trough (sorry if
>>>> this is not the right term for it) that Emacs 21 has could be used to
>>>> indicate a collapsed thread, for instance.
>>>
>>> If I understand that part of emacs (you speak of the ``fringe'' btw),
>>> there is little chance to do this
>>
>> [ snip ]
>> > please prove me wrong
>>
>> I do not think this is what he is talking about at all.  
>
> OK I focused completely on the not so important 2nd sentence but this
> was the third post with an emacs21-fringe idea which seems hard to
> implement, so I posted this. 
>
>>                                                           Rather, my
>> interpretation is that he is suggesting that a few variables be added
>> to indicate how a collapsed / uncollapsed topic should be indicated to
>> the user.  
>
> Now you've misunderstood something.

Er right, I misread thread as topic.

>  He is talking about threads which
> are a summary buffer thing. Hitting C-M-s on a parent of a thread
> hides its children and display an ellipsis [...] at the end of the
> line.
>
>>             Currently, in the default setup where
>> gnus-topic-line-format is "%i[ %(%{%n%}%) -- %A ]%v\n", we have the
>> following for an open topic:
>>
>>         [ misc -- 0 ]
>>
>> And:
>>
>>         [ misc -- 0 ]...
>>
>> for one which is collapsed (the `...' is create by the %v).
>>
>> Instead, %v should not be fixed and should be be replaced by, for
>> instance, gnus-topic-collapsed-string when collapsed and
>> gnus-topic-uncollapsed-string when open.
>
> Agreed. Search for gnus-topic-insert-topic-line in gnus-topic.el and
> find these two hardcoded. There would be a fast fix. But then, in
> gnus-sum.el, which controls what the OP wanted to customize, this
> doesn't work. The ellipsis is implemented completely differently
> there (without %v). I have almost found a way to change it there.
>
> 	Martin
>
> btw, why aren't we discussing this on the list?

Oops.  I hit the wrong keys.  





      parent reply	other threads:[~2001-09-12 16:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-10 14:51 Ted Zlatanov
2001-09-11 20:40 ` Martin Kretzschmar
2001-09-12 14:43   ` Martin Kretzschmar
2001-09-13 18:51     ` Ted Zlatanov
2001-09-18 12:29       ` Martin Kretzschmar
2001-09-18 13:55         ` Ted Zlatanov
2001-09-19  9:47           ` Martin Kretzschmar
     [not found]   ` <87g09t4dpt.fsf@bassanio.walfield.org>
     [not found]     ` <877kv41o1c.fsf@mogli.aximilation.org>
2001-09-12 16:01       ` Neal H Walfield [this message]

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=87snds2ya6.fsf@bassanio.walfield.org \
    --to=neal@cs.uml.edu \
    --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).