Rename functions hackernews-read-contents and hackernews-render-item with double hyphens to enable easier future API changes.
Add form feeds near ;;; sections (e.g. as per lisp/simple.el) to allow page navigation with C-x[ and C-x].
Discussion
As I mention in the first commit message, hackernews-read-contents and hackernews-render-item do not comprise a meaningful/consistent API, despite their current centrality to hackernews. IMO, the sooner we indicate their potential instability, the better.
I am particularly thinking of #39 and #40 in relation to hackernews-read-contents and the possibility of moving to a different UI, e.g. tabulated-list-mode, in relation to hackernews-render-item.
If there are no comments/objections, I will merge in around a week's time.
Changelog
hackernews-read-contents
andhackernews-render-item
with double hyphens to enable easier future API changes.;;;
sections (e.g. as perlisp/simple.el
) to allow page navigation with C-x[ and C-x].Discussion
As I mention in the first commit message,
hackernews-read-contents
andhackernews-render-item
do not comprise a meaningful/consistent API, despite their current centrality tohackernews
. IMO, the sooner we indicate their potential instability, the better.I am particularly thinking of #39 and #40 in relation to
hackernews-read-contents
and the possibility of moving to a different UI, e.g.tabulated-list-mode
, in relation tohackernews-render-item
.If there are no comments/objections, I will merge in around a week's time.