Re: newsticker-*.el files

[Ulf Jasper]

Thien-Thi Nguyen <address@hidden> writes:

> feedread
> readfeed
> rd-feed
> feeddisp ("display")
> feedshow
> showfeed
> feedtick
> tickfeed
> showxmlf (show XML (as opposed to some more elegant
>                     sexp equivlant)
>                feed)
> etc, etc.

feedread sounds good. "feedreader" sounds even better and would be a
better name than "newsticker" I think.

newsticker.el           -> feedreader.el  (feeadrea.el)
newsticker-backend.el   -> feedr-back.el  (feedr-ba.el)
newsticker-plainview.el -> feedr-plain.el (feedr-pl.el)
newsticker-reader.el    -> feedr-read.el  (feedr-re.el)
newsticker-ticker.el    -> feedr-tick.el  (feedr-ti.el)
newsticker-treeview.el  -> feedr-tree.el  (feedr-tr.el)

That would match the 8+3 rule, be readable, and even be reasonable.

> Personally, i prefer "showfeed", which can be shortened to "shfeed"
> and then suffixed: "shfeed-x" (XML), shfeed-s (sexp), shfeeddN
> (data acquisition -- think process monitoring -- format N), etc.
>
> If you stretch a bit, another (further) stopping point is "tree":
> "shtree".  I would be pleased to use such a facility for examining
> gnugo.el runtime structures, for example.

Extending newsticker, I mean feedreader, shouldn't be too difficult.
Retrieval is generic already as it can be done with an arbitrary elisp
command. Making newsticker=feedreader understand other feed formats is
easy, as long as the formats are well tempered. And of course one may
write another frontend/reader. But I don't see how you could play go
with it.

>                                                  Anyway,
> probably if you rename it like Knuth would, you'll be ok!

My copy of taocp has been collecting dust lately -- how would he do it?

Ulf

-- 
Klicken Sie HIER und Sie erhalten vier Dosen umsonst