tt yesterday evening to mute things I'm not interested in. But I have to polish the code before releasing it to the wild.
That's better illustrated on some example. Consider the simple kill file rule
'sxivfua' in twt.conversation_hashes that will just hide the complete conversation tree with all its branches. Here's a screenshot of yesterday's version where I just replaced the text, but didn't hide the twts yet (current code does):
complete conversation killedNow, if that kill file rule is extended to
'sxivfua' in twt.conversation_hashes and twt.source.nick != 'david' some twts are not matched by the rule in the conversation. Again, from yesterday's experiment:
partial conversation tree killedIf I do this today, it just hides the killed entries without any shown leaves. However, it still keeps the intermediate nodes that would have to be killed according to the kill file rule. For sake of keeping the structure intact I decided to still show them in a modified manner:
partial conversation tree killed, now reallyI haven't made up my mind on where to configure the kill file rules. Maybe in the config file in a dedicated
[killfile] section. Then the keys could be some names or descriptions that describe the rules.And I also need to integrate this into the UI, so I can press something like
^K and then automatically insert a rule that hides that tree at the cursor.
> either need to follow fewer people or I need to somehow rework my client’s UX.
I _think_ you should focus on the later 😂 That particular Yarn you're tlaking about with over ~50 Twts I didn't even notice until last night sometime before bed 😂
The UX(s) of
tt and jenny (correct me if I'm wrong) don't collapse threads by default right? 🤔~
> either need to follow fewer people or I need to somehow rework my client’s UX.
I _think_ you should focus on the later 😂 That particular Yarn you're tlaking about with over ~50 Twts I didn't even notice until last night sometime before bed 😂
The UX(s) of
tt and jenny (correct me if I'm wrong) don't collapse threads by default right? 🤔~
yarnd some week or so ago as well -- But I don't use this very much, because the "Flat view" collapses long threads so it's not a problem.
yarnd some week or so ago as well -- But I don't use this very much, because the "Flat view" collapses long threads so it's not a problem.
tt cannot even collapse conversation trees, they're always fully expanded. Or not shown at all if all twts in that tree are marked as read and the appropriate setting is enabled to hide completely read conversations.
tt needs to grow similar support? 🤔
tt needs to grow similar support? 🤔
I think I’ll try playing with mutt’s
collapse_unread setting first. I don’t want this for *email*, but it could be useful for twtxt. It basically keeps all threads collapsed, unless you explicitly open them.
I think I’ll try playing with mutt’s
collapse_unread setting first. I don’t want this for *email*, but it could be useful for twtxt. It basically keeps all threads collapsed, unless you explicitly open them.
I think I’ll try playing with mutt’s
collapse_unread setting first. I don’t want this for *email*, but it could be useful for twtxt. It basically keeps all threads collapsed, unless you explicitly open them.
So for the beginning I would do it the other way. Expand everything unread and manually collapse and mark read the whole thread if it gets too boring. This way it's easier to jump over a few messages and quickly see if it gets more interesting or not. But maybe that's already the way you do it.