emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Samuel Wales <samologist@gmail.com>
To: sindikat <sindikat@mail36.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Orgmode] Feature request: IDs on anything
Date: Tue, 29 Nov 2011 14:13:05 -0700	[thread overview]
Message-ID: <CAJcAo8vVFxYDbeAzpuaegnxqsU0CTpdaEiJAmD2DOwvfhkYzuA@mail.gmail.com> (raw)
In-Reply-To: <20111127230951.35547.qmail@rage.so36.net>

Hi sindikat,

On 2011-11-27, sindikat <sindikat@mail36.net> wrote:
> I really love this idea of ID markers. It would open so
> many opportunities for semantic extensions of org-mode and
> not only. Using ID markers we can
> management could be made out of that. Every ID marker will
> effectively become a graph vertice.

Yes, you got it.  Wherever an ID marker is, that place is a
graph vertex.

Because it uses Org IDs, it is pretty unbreakable and can be
linked to across files.  If you move it, you don't have to
change anything that points to it.

You can change how an ID marker looks by adding a keyword
argument (like :label or :face) to the marker.


As you suggest, the arguments can let you point to other
markers to create arbitrary graph structures.

Among other things, this allows =unbreakable bidirectional
links=.  IMO these potentially solve a few unaddressed
aspects of the =tree problem= (my term for the fact that
ideas and tasks naturally form a graph but outlines form a
tree).  Especially with the right label code.  RET bounces
between the ends.

Of course, this is vaporware as.  It's been discussed in a
bunch of threads.  Perhaps you would be willing to try
implementing it.


The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Bigotry against people with serious diseases is still bigotry.

  reply	other threads:[~2011-11-29 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-27 23:09 [Orgmode] Feature request: IDs on anything sindikat
2011-11-29 21:13 ` Samuel Wales [this message]
2011-12-01 13:48 sindikat

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:

  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=CAJcAo8vVFxYDbeAzpuaegnxqsU0CTpdaEiJAmD2DOwvfhkYzuA@mail.gmail.com \
    --to=samologist@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sindikat@mail36.net \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


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).