--> ap/xxxxx

* __

annotation code fix: (2008.01.17:1 annotation#4 annotation_software#20)



Credits for sources to all at:




Annotation code for all wikis (2007.12.13:1 annotation#3 annotation_software#19)


New annotation GR code: (2007.12.06:1)


Parses Gravitys Rainbow Wiki and supports line numbers - cleaner formatting also in org-mode:

Annotation [Gravity's Rainbow] (2007.11.05:2)

To re-work code base with following ideas/questions:

1] Difference between phrase commentary and category/idea annotation

2] Problem with category headings thus for each page.

3] Locations and mapping out eg. Peenemuende map, Usedom coast, Slothrop's route, Berlin route, time route

4] How to handle embedded page numbers

5] Cleaning up electronic GR copy so that we can crosslink in the text itself (and code for this also)

6] How to enter and retrieve categories [as properties] (now using latest org-mode 5.13h):

Problems with adding a single value to a property [we can make property/value pair with C-c C-c s or C-c C-x p but we can't add values]

C-c / p - to retrieve as sparse tree doesn't seem to work so well as we have all headlines at top level - is fine is we have all pages as second level headings

Perhaps working better by adding tags to the page/headline [still with sparse tree problem solved by extra heading level]

7] How thus to work across page/category divide?

Annotation updated (2007.10.19:1 emacs#50 annotation#1)


So that new page annotations are placed under same major heading.

Still need some way of organising multiple annotations (how to possibly parse line number).

[from wrong page]

Inlined Emacs images using iimage.el: (2007.09.11:3 emacs#36 annotation_software#15)


C-l to re-display them

As minor mode with org-mode we use ‹foo.png› syntax for images which can be embedded under headings and so on.

First annotation.el cleaned up release for Gravity's Rainbow annotations: (2007.09.11:1 annotation_software#14 software#8)


1] Interactive commands (no bindings as yet):

palm-ann: enter all annotations in proper format from Memo pad:GR category on the Palm Pilot (uses altered:


annotate_region/annotate_buffer: annotate formatted regions/buffers

annotate_template: write formatted template for annotation entry

inter_annotate: prompt for annotation additions for a text region

annotate_wiki/annotate_hyperarts: input annotations from resepctive wikis (in a cleaned up wiki buffer)

2] Features:

3] Format:

P: page number [note capitals]

b: beginning words

e: ending words

c: categories

t: text block of annotation

4] TODO:

5] Links:

Org-mode documentation: http://orgmode.org/org.html

Emacs-Pilot synchronization suite: http://turing.ubishops.ca/home/bruda/emacs-pilot/

annotation bug fix and entry of all text now from Gravity's Rainbow (2007.09.01:1)



1] New annotations input from: http://www.hyperarts.com/pynchon/gravity/ DONE - bit rough but working

2] Tidying - line breaks, wierd mark up, unnecessary spacing DONE

3] link/markup structure - to some degree DONE - need to figure out inheritance

4] parsing and query code

newer annotation2.el fixes trailing text space problem. (2007.08.31:1)

for event platform/annotation software/ and emacs-driven-wiki: (2007.08.23:1 annotation_software#11 xxxxx_at_piksel2007_technotes#13)

Code base AS platform. code and comments reparsed by further comments to provide differing views or re-processings generating actively new content. Such differing views on an active code base represent the particular application

For example: emacs wiki with active lisp functions to generate text (say, for example from the knowledge representation annotations and relations, from remembrance agent, from processes running on a local or remote machine, from collaborative endeavour). To extend this dynamism into a running Common Lisp web server.

Comments morph into code as a development methodology. Rendering active potentials.


;; - further integration with version control/RCS check in and check                                                                                                      
;; - out / auto-save annotation file                    
as suggestions for further work on annotation platform. Version control also for event (and version control of the script-text courier's tragedy itself within Crying of Lot 49 // all these differing editions of the Wharfinger text). See also:


At the other end of this - filesystem and resources.

expand annotation/platform (2007.08.22:2 xxxxx_at_piksel2007_technotes#12 annotation_software#10 emacs#33)

using GNU Emacs 22/image-dired/linkd/org-mode usw.


To enter Image-Dired, mark the image files you want to look at in the Dired buffer, using m as usual. Then type C-t d (image-dired-display-thumbs). This creates and switches to a buffer containing image-dired, corresponding to the marked files.

code also from goby and/or eev (see emacs - where this should also go!)

annotation code Palm and buffer support: (2007.08.22:1 xxxxx_at_piksel2007_technotes#11 annotation_software#9)

again: http://1010.co.uk/annotation2.el

1] palm-ann. enters memos into annotation system format as for:

annotate-region: which annotates selected region marked up as follows:

p: page number

b: beginning words

e: ending words

c: categories

t: text block of annotation

2] or use prompted entry with annotation text as region by way of:


3] Makes links to original Gravity's Rainbow text in org-mode fashion

4] TODO:

(note: uses org-mode linking syntax)


annotation update (2007.08.21:1 xxxxx_at_piksel2007_technotes#9 annotation_software#7)

For GR annotations we need:

Annotation is not from original text (region), but we could have this function. From above data we retrieve and format quote, markup and link, and enter into correct place with active link to original text.

Markup needs also to refer to online links, inline images and to read and respond to Gneve-based video markup (alterations to gneve for video markup and tests for keyframes TODO). This could come from base in linkd and/or org-mode:

Org-mode (vs. planner?):

Features of interest:

[problem is conflicts with use of remember for planner as in now]


Org-mode documents can contain dynamic blocks. These are specially marked regions that are updated by some user-written function.

In combination with Org-mode, you can use templates to generate different types of remember notes. (2007.08.20:3 xxxxx_at_piksel2007_technotes#8 annotation_software#6)



would be fast annotation mode using this.

During expansion of the template, special %-escapes allow dynamic insertion of content:

     %^{prompt}  prompt the user for a string and replace this sequence with it.
     %t          time stamp, date only
     %T          time stamp with date and time
     %u, %U      like the above, but inactive time stamps
     %^t         like %t, but prompt for date.  Similarly %^T, %^u, %^U
                 You may define a prompt like %^{Birthday}t
     %n          user name (taken from user-full-name)
     %a          annotation, normally the link created with org-store-link
     %i          initial content, the region when remember is called with C-u.
                 The entire text will be indented like %i itself.
     %^g         prompt for tags, with completion on tags in target file.
     %^G         prompt for tags, with completion all tags in all agenda files.
     %:keyword   specific information for certain link types, see below

display and marking(management, annotation, linking) (2007.08.20:2 xxxxx_at_piksel2007_technotes#7 annotation_software#5)

of images, text-> speech or display, sound, film (see gneve)

working both ways - how we are annotating (the system), and the display of such annotations. For example to be able to annotate sequences and frames in Pasolini's Salo and then to view film and timed annotations. Also here the relation to the original. Also links to images and text within a filesystem - but what of, say, GR annotations with annotation file and ext file which must also be matched. Thus annotation format/code needs to automatically add file reference.

For linking refer to: linkd (which marks up buffer blocks and enables linking between blocks)

Also of note: org-mode: http://staff.science.uva.nl/~dominik/Tools/org/

which is implemented on top of outline-mode...

and planner again (markup).

Throw in link to underlying process code, scheduling and is complete platform mode.

division of annotation/presentation platform: (2007.08.20:1 xxxxx_at_piksel2007_technotes#6 annotation_software#4)

1] annotation system + Palm Pilot entry system (TODO. see also: )

2] presentation functions - images/mplayer/speech usw. (we have)

3] KR system (see KODIAK)

4] link to underlying Common Lisp (ILISP, SLIME)

5] markup and syntax highlighting (see planner/eev)

6] active and shell process (see eev)


1] annotation:

is fine scrying_tech_notes but other way.

eg. using terminal on Palm Pilot as entry system for annotations

1] tried using (insert-file-contents "/dev/ttyS0") which works but only after Ctrl-G this command do the characters appear.

2] modified pilot.el and memo-pilot-el from emacs-pilot-1.4 to work with importing memos to file - change to import into annotations buffer and also to avoid repetition - test export of memos

3] Kermit script:


(but is not directly into buffer)

4] C - read one character wrapped in: (insert (shell-command-to-string COMMAND))


for i in *; do cp $i $(echo $i | cut -d "-" -f2); done
to cut off header and leave last number and:

ls .sort -n

to list in correct (numerical) order

but how to fix so that we can work in this order?

prefix s command in dired buffer with a zero and then pass ls -lv command to dired

and then use macro to strip text and concat into another buffer

[completed - now to be marked up and reformatted]

parsing Gravity's Rainbow wiki (2007.08.15:1 xxxxx_at_piksel2007_technotes#5 annotation_software#1)

for entry into annotation system.


1] wget -mirror

2] shell script to convert to plain text:

for file in `ls *Pages*`
new=`basename $file`
cp $file ${new}.html
lynx -dump ${new}.html > ${new}.txt 

3] TODO - automatically go through directory in Emacs Lisp and enter page-numbered entries [also mark with GR-wiki tag!]