__

for current planner/emacs-wiki setup: 19:55 (2006.11.30:2 tech_notes#314 emacswiki_plannermode#9)

TODO::

• 1] greater number of categories/links (by hand) eg. lisp, lispcpu, endophysics, exteriority and in some way to group these

what is already in planner/emacs-wiki to make such grouping possible?

• 2] categories successfully placed in rss on publication

(add-to-list 'remember-planner-append-hook 'planner-rss-add-note t)

called in: remember-planner-append (&optional page) within remember/remember-planner.el

deosn't work. we need to know what exactly is a note.

• 3] front page news refs should be to named page rather than (planner) day

see ~/elisp/snuff.el:

(emacs-wiki-published-name (planner-note-page info))

need to know how pages are organised

• 4] version control integration with, say, rcsmerge page attached to all [(x)tla, GNU Arch, rcs]
• 5] remembrance agent integration
• first step being to back up current planner pages and work offline on such features

man rcsintro ... 14:15 (2006.11.30:1 tech_notes#313 emacswiki_plannermode#1)

simple version control

rcsintro - introduction to RCS commands

DESCRIPTION

The Revision Control System (RCS) manages multiple revisions of files. RCS automates the storing, retrieval, logging, identification, and merging of revisions. RCS is useful for text that is revised frequently, for example programs, documentation, graphics, papers, and form letters.

The basic user interface is extremely simple. The novice only needs to learn two commands: ci(1) and co(1). ci, short for `check in', deposits the contents of a file into an archival file called an RCS file. An RCS file contains all revisions of a particular file. co, short for `check out', retrieves revisions from an RCS file.

RCS as created directory under project sub-directory

rcsmerge is used in our xxxxx_publication version control text:

rcsmerge  -p  -A -r1.1  -r1.6  alice > version_control

how this could be integrated with emacs-wiki/planner for automatic generation of merge files

• co - checkout planner page(s)
• edit
• ci - checkin published page
• merge latest versions and plan-page as page_name_rcsmerge