| |||||||||||||
EPOLL_CTL_DISABLE, epoll, and API designEPOLL_CTL_DISABLE, epoll, and API designPosted Oct 26, 2012 0:21 UTC (Fri) by Jandar (subscriber, #85683)In reply to: EPOLL_CTL_DISABLE, epoll, and API design by dlang Parent article: EPOLL_CTL_DISABLE, epoll, and API design
Nearly all content of https://lwn.net/Comments/unread I have already seen.
I read LWN in the "One big page" mode and go to the comments (in a new tab) with the "Comments (xxx posted)" button. After I have read the comments for one article I close the tab. Is there something I can do to make Comments/unread more useful?
What I would really like would be some means to hop from one unread comment to the next within the complete comment-section to see the surrounding context. It could be a link at each unread comment pointing to an anchor at the next. E.g. http://lwn.net/Articles/520198/#Comments-UnRead42.
(Log in to post comments)
EPOLL_CTL_DISABLE, epoll, and API design Posted Oct 26, 2012 0:46 UTC (Fri) by dlang (✭ supporter ✭, #313) [Link]
If you were logged in when you saw those other comments, and still see them on the /unread page, there is a bug that you should send to lwn@lwn.net
However, I suspect that if you go to the unread page again, you will not see all those comment any more and you will find it much more useful.
you should also look at the greasemonkey script for lwn, I think it does more of what you are looking for.
EPOLL_CTL_DISABLE, epoll, and API design Posted Oct 26, 2012 1:22 UTC (Fri) by Jandar (subscriber, #85683) [Link]
I was logged in while reading this weekly edition. Next week I make a few tests and see if a bug is reproducible.
I use konqueror not firefox but greasemonkey with fancyLWNComments seems to be a reason to switch for reading LWN. Thanks for pointing me to it.
|
|||||||||||||