emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: mah@everybody.org (Mark A. Hershberger)
To: Craig Muth <craig.muth@gmail.com>
Cc: emacs-orgmode@gnu.org, emacs-devel@gnu.org
Subject: Re: Xiki framework (wiki and tree emacs features)
Date: Fri, 05 Feb 2010 20:26:50 -0500	[thread overview]
Message-ID: <87ljf7p31h.fsf@everybody.org> (raw)
In-Reply-To: <e0a9243f1002051248kd704f1axc9770e3db21aa8b@mail.gmail.com> (Craig Muth's message of "Fri, 5 Feb 2010 15:48:54 -0500")

Craig Muth <craig.muth@gmail.com> writes:

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

It's hard for me to see exactly what is going on, but it doesn't look
like anything that OrgMode isn't already doing or could be made to do
with a SMOP.

Look at Emacs Starter Kit
(http://eschulte.github.com/emacs-starter-kit/) for an example of how
you can mix OrgMode markup and Emacs Lisp, for example.

Mark.

-- 
http://hexmode.com/

The only alternative to Tradition is bad tradition.
                          — Jaraslov Pelikan

       reply	other threads:[~2010-02-06  1:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e0a9243f1002011908w1e64c032maf0ddde034c93f2f@mail.gmail.com>
     [not found] ` <878wb7r196.fsf@everybody.org>
     [not found]   ` <e0a9243f1002051248kd704f1axc9770e3db21aa8b@mail.gmail.com>
2010-02-06  1:26     ` Mark A. Hershberger [this message]
2010-02-06  1:45       ` Xiki framework (wiki and tree emacs features) Craig Muth
2010-02-06 22:55         ` Richard Stallman
2010-02-07 11:33           ` Glauber Alex Dias Prado
2010-02-07 15:55             ` joakim

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=87ljf7p31h.fsf@everybody.org \
    --to=mah@everybody.org \
    --cc=craig.muth@gmail.com \
    --cc=emacs-devel@gnu.org \
    --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
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

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