emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Graph not hierarchical?
Date: Fri, 14 Feb 2014 20:58:05 -0600	[thread overview]
Message-ID: <CAFAhFSXd0J++U=iwPXuoQtu0wNkHoqgXLF3+fTf7_sPH1vmJ_A@mail.gmail.com> (raw)

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

Is there any way to have org mode simulate a graph structure rather than
always a (folding) hierarchy? You could say a hierarchy is a tree graph,
and you could "link" or give a "jump" from one entry to another -- even in
another org file. It seems plausible to call an entry a "node," and a node
could have listed in its properties "edges" leading to other nodes. Has
anyone else thought of this?

Without knowing anything about how org mode is really coded under the hood,
I'm guessing (from reading the documentation) it is simply built on the
emacs folding code, i.e., there is no real underlying hierarchy
algorithm(s) that you could hack into in order to make org mode more
database-like (tree, graph, or otherwise).

Some of these thoughts came from the simple examples given in "Land of
Lisp" where a simple nodes and edges representation was given with a-lists:

(defparameter *nodes* '(living-room garden attic))

(defparameter *edges* '((living-room (garden west door)
                                     (attic upstairs ladder))
                        (garden (living-room east door))
                        (attic (living-room downstairs ladder))))

The nodes are living-room, attic, and garden. And the edges are an a-list
keyed on the nodes, e.g., living-room has two edges, one connected to the
attic (upstairs by way of a ladder), the other to the garden (to the west
by way of a door).

I guess this is beginning to sound like a weak graph database hack, but as
I envisioned it, each node -- an org mode entry -- could be leveraging org
mode's big strengths: literate programming and loose, do-it-yourself text
data storage.

LB
North Shore MN

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

next             reply	other threads:[~2014-02-15  2:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-15  2:58 Lawrence Bottorff [this message]
2014-02-15 10:44 ` Graph not hierarchical? Eric S Fraga
2014-02-15 15:34   ` Lawrence Bottorff
2014-02-15 21:05     ` Eric S Fraga
2014-02-18 17:18     ` Brett Viren
2014-02-18 18:00       ` Nick Dokos
2014-02-18 18:33     ` Samuel Wales
2014-02-18 18:36       ` Samuel Wales
2014-02-18 18:46         ` Samuel Wales
2014-02-20  3:11           ` Lawrence Bottorff
2014-03-01  7:26             ` Bastien

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAFAhFSXd0J++U=iwPXuoQtu0wNkHoqgXLF3+fTf7_sPH1vmJ_A@mail.gmail.com' \
    --to=borgauf@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).