From: Bastien <bzg@altern.org>
To: emacs-orgmode@gnu.org
Subject: Re: org mode vs basecamp
Date: Wed, 24 Oct 2007 10:43:03 +0100 [thread overview]
Message-ID: <878x5sonko.fsf@bzg.ath.cx> (raw)
In-Reply-To: <854pghdlbi.fsf@usenet.my.skamphausen.de> (Stefan Kamphausen's message of "Wed, 24 Oct 2007 09:27:13 +0200")
Stefan Kamphausen <skampi@gmx.net> writes:
>> 3. The third idea is to let a web interface directly operate changes on
>> underlying Org files. I think this is achievable: Org files are text,
>> but with a reasonable set of conventions to format them we could edit
>> them through another tool.
>
> in my mind lives another idea which is close to your #3: use a wiki as
> a backend (currently I'm thinking about oddmuse).
>
> - Write an extension to oddmuse which displays org-syntax as HTML.
> Has to be written in Perl, probably could reuse lots of regexps from
> org.el. A really fancy extension would render checkboxes and the
> like, but I don't know whether this is achievable.
> - Instead of find-file and save-buffer one could use oddmuse-edit and
> oddmuse-post from [1].
> - Setup auto-mode-alist to set org-mode when opening such a wikipage,
> or put a -*-modeline into the wikipages
I've not been using the OddMuse wiki engine for a long time now, and I
don't know how difficult such a backend would be to write, but I think
this is an *excellent* idea.
> I'll try to find some time during the next weeks to start with the
> oddmuse-extension, but I can't see when that will happen. It has to
> fill the time-slots when they come up ;-)
Good luck! :)
--
Bastien
next prev parent reply other threads:[~2007-10-24 8:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-23 9:17 org mode vs basecamp cezar
2007-10-23 17:09 ` Bastien
2007-10-23 18:43 ` cezar
2007-10-23 20:21 ` Bastien
2007-10-24 9:06 ` cezar
2007-10-24 10:26 ` Bastien
2007-10-24 10:52 ` cezar
2007-10-24 12:05 ` Bastien
2007-10-24 7:27 ` Stefan Kamphausen
2007-10-24 9:43 ` Bastien [this message]
2007-10-24 8:58 ` Stefan Kamphausen
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=878x5sonko.fsf@bzg.ath.cx \
--to=bzg@altern.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).