Re: Request: links to Elisp package homepages
"Ben Wing" <ben(a)666.com> writes:
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/
(in response to a message from Adrian about broken links)
> http://home.xnet.com/~blatura/linapps.shtml
An "updated" link is
http://powerusersbbs.com/linapps/
But this is still from 1998.
This looks better:
http://www.linux.org/apps/
Done.
Done.
> http://kaolin.unice.fr/~serrano/emacs/emacs.html
> timed out connecting to host
>
> http://optics.ph.unimelb.edu.au/help/source/texcd2.2/gnu/GNU%2
>0emacs/ispell_port.html
> not found (404)
> http://www.extundo.com/gnus-imap/
> not found (404)
> http://www.hpl.hp.co.uk/people/ange/
> timed out connecting to host
> http://www.ultranet.com/~zappo/fsf.shtml
> not found (404)
This whole section on Elisp packages is totally rotten.
Norbert or anyone else, is there an updated list of web pages for
independent packages that anyone is maintaining? If not, can people at
least send lists of pages that they know about so we can update this info?
BTW Adrian, this whole page does not belong under Architecting XEmacs. We
Ben, I put Architecting XEmacs under CVS.
The content, according to %author% added back then, originates with
you.
Who better than you to rework it to your pleasing?
I can get you started with the xemacsweb module, if you need help.
http://www.xemacs.org/About/Website.html#GfC
should be a good start.
need a separate page for links; if we already have one, we need to
merge the
two. (It looks like there is no such page. Adrian, could you put a "Links"
section under the main sidebar, with a pointer to www.xemacs.org/Links/ as
well as pointers to the various Links pages, and add a page for Packages and
maybe one to include the other stuff from Architecting XEmacs?)
I think Architecting XEmacs should be nuked as it is out-of-date and I've
incorporated most everything into the internals manual. Once I'm sure there
No objections.
is no remaining info here that isn't there I'll ask you to
nuke it, and in
its place we should link to the "Future" section of the copy of the
internals manual that we keep online.
Sounds good.
We probably should move to online docs with named rather than
enumerated anchors.
I think makeinfo --html would do that, but I'd have to test that well
before a possible transition.
Enumerated anchors will cause permanent breakage after new nodes are
added to our docs.
A commit trigger for texi files and moving to online docs with named
anchors is an area I can see myself working on fairly short-term.
Moving away from the orphaned genpage is another issue I wanted to
tackle for a long time but haven't for lack of it.
Best regards,
Adrian