WIP: Adds env var for max posts #105
No reviewers
Labels
No Label
bug
compatibility
documentation
duplicate
enhancement
future release
help wanted
invalid
non-code
question
refactor
testing
this release
wontfix
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cmccabe/linkulator2#105
Loading…
Reference in New Issue
No description provided.
Delete Branch "line-limit"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Not sure if this is wanted or if a better route to the end result would be preferable. So treat this pull as a proof of concept rather than as something needing to get pulled in.
I often use dvtm on rtc and scrolling back in the terminal, while doable, is a pain. I dont need the ancient posts generally. As such I modded linkulator to take an env var
$LINK_LIMIT
. If I set it to3
I will only see the top three posts in any category.A better approach, now that I am writing this might be to have a flag within linkulator that can be triggered by a menu input to only show "recent" posts (with recent being defined as something like "within the last 30 days"). That way it could be toggled on and off easily.
Anyway, let me know what you think. Is something like this needed at all? Is the link limit var way good? Would a "recent" flag within the running program that can be toggled on and off be better (this is how telem works over in circumlunar space)? Let me know. I'm happy to build out whatever would be good. I have to imagine I am not the only one with scrollback being a pain to deal with and ever expanding posts being unwanted...
Adds env var for max poststo WIP: Adds env var for max postsHi Sloum
I did try to address scrollback by making a curses client, which is available in the pager branch. It has most functionality available, and I've been using it for a while. I wasn't sure if it was too big to be considered an upgrade instead of a new client, also I didn't know if it was something people were interested in.
Your idea is quite good, a simple way to limit screen usage in the current version. Having a recent flag might also work well, as it would ensure you wouldn't miss an update if the new items exceeded the line limit. Of the two, the recent flag seems like something I might use more.
Step 1:
From your project repository, check out a new branch and test the changes.Step 2:
Merge the changes and update on Gitea.