Re: Xiki framework (wiki and tree emacs features)

[Craig Muth <craig.muth@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 2108 bytes --]

Here's an example of a xiki tree you might build up when working in some
elisp files.  Could be useful for communicating about code on mailing lists
like this one.  Forgive me if org mode (or something else) already does
this.  If so please enlighten me - I'd be interested in checking it out.

- /usr/share/emacs22/
  - lisp/
    - isearch.el
      | (defun isearch-forward (&optional regexp-p no-recursive-edit)
        | Type \\[isearch-yank-char] to yank char from buffer onto end of
search\
        | (defun isearch-mode (forward &optional regexp op-fun
recursive-edit word-p)
          | (defvar isearch-mode-map
            |     (define-key map "\M-\C-y" 'isearch-yank-char)
              - Not recognizing var:
              | (defun isearch-yank-char (&optional arg)

      + all lines using the map: ##isearch-mode-map/

    - You can see it compiles:
    ! ls -l
      ! -rw-r--r--    1 craig  admin    97058 Feb  2 11:58 isearch.el
      ! -rw-r--r--    1 craig  admin    66540 Feb  2 11:58 isearch.elc

  - site-lisp/
    - session.el
      | (defcustom session-registers '((?0 . ?9) ?- ?= ?\\ ?` region (?a .
?z))
        - Todo: want to include this:
        |   CHAR or (FROM . TO) or `file' or `region' or t.

Such trees are navigable in any buffer/file (you can just paste in the
tree), though in note-mode they will be colorized.

Normally you build up these trees (using keyboard shortcuts) for your self,
for navigation while you're working and for reference later.  You can also
send them to other people, and they can use them to navigate (possibly
changing the /usr/share/emacs22/ line first if appropriate).

Note you can C-. (or C-enter, or double-click) on dirs to expand and show
their files, on files to open them or expand their contents, on lines within
files to jump to them, on the "!" line to run the command, and on the "##"
line to expand the search (searches expand out into a sub-tree).  The "-
foo:" lines are ignored, and are just there for notes.  The whitespace
before the "| ..." lines is insignificant, so you can indent to represent
the call hierarchy.

--Craig

[-- Attachment #2: Type: text/html, Size: 2619 bytes --]