Re: [tin] Setting it up - Headers
- From: Whiskers <catwheezel@xxxxxxxxxxxxx>
- Date: Sun, 18 Dec 2005 19:55:09 +0000
On 2005-12-18, eerok <eerok@xxxxxxxxxxxx> wrote:
> On Sun, 18 Dec 2005 12:23:32 +0000, Whiskers wrote:
>> On 2005-12-18, eerok <eerok@xxxxxxxxxxxx> wrote:
>>> On Sun, 18 Dec 2005 01:19:47 GMT, SINNER wrote:
>>>> In fact, in my little foray into the world of tin, it seems that a merge
>>>> of these to apps (feature wise) would be an incredible NNTP client.
>>> I thought the same thing. Quite a few features of tin hit
>>> just the right note for me; it's already made my short list
>>> of favorite newsreaders ...
>> Do the slrn macros 'tin-group.sl' and 'tin-art.sl' not go far enough? I
>> have never given Tin more than a cursory look so I can't really make a
>> comparison - but I'm willing to learn more.
> To be honest, I don't know what those macros do, but I think
> slrn is flexible enough to do most anything. At this point I
> think it would help if I stated more specifically what I like
> about tin:
> * I like the "article view" which fills my term with just
> what I'm reading. I don't need any other windows, since
> typically the "threaded view" in a split window ends up
> too small to be very useful to me anyway.
Slrn can do that too (the z toggle)
> * I like the context information I'm given in article
> view: articles in the thread; current article number;
> threads in the group. I can use this info to jump
> around within a thread (by entering article numbers).
slrn offers an 'analogue' (ie visual) indication of that sort of
information, in the 'thread' view and split thread+article view; but if
you like numbers better, then fair enough.
> * I like getting the whole thread (even the posts I've
> seen) when there are new posts in the thread. This
> gives me the option of reading the whole context if I
> want ("Enter") or skipping to what's new ("N").
That is not something slrn does at present; however, 'get parent' works
well enough for me, mostly. 'Reconstruct thread' would be useful, but
that requires a function not curently supported by my local NNTP cache
> * I like staying in article view and browsing through a
> group with liberal use of thread-killing ("K") which
> just pops me smoothly to the next thread. For example,
> in a group like comp.lang.learn.c-c++ I'm not interested
> in the posts about c++ ... so I just blast around those
> threads once I see the first post. (In a perfect world,
> I'd be able to see by the subject line what language the
> topic referred to, but this is seldom the case ;-))
I can 'skim and dip' easily in slrn, too; I suppose a macro could be
written for slrn to 'mark as read' the whole of a thread while viewing any
article in that thread - but I work the othr way around; I mark articles
or threads I want to 'keep' so that they survive the 'catchup' which
'marks all [up to here] as read'. Slrn can also kill on Subject, of
course, but 'out of the box' that isn't a one-key operation.
> That's enough detail for now. I'm sure that my preferences
> aren't universal; I'm just mentioning them so you know what
> I'm talking about.
> Offhand I'd say that some of these things would be easier to
> implement in slrn than others.
Often there is an accomodation of the user to the features of their
particular newsreader - leading to subsequent preference for 'doing it
that way' in any other newsreader they try ;))
- Prev by Date: Re: [tin] Setting it up - Headers
- Next by Date: Re: Xnews - urls not opening in 98lite
- Previous by thread: Re: [tin] Setting it up - Headers
- Next by thread: Re: [tin] Setting it up - Headers