Alexander Burger <a...@software-lab.de> writes: Hi Alex, Hi List,
thanks for the cool tractatus and the as always very interesting views about wiki markup. I don't know if I should mention it, because it's in a raw state and I don't have much time to polish it now, but as you know there does exist already an alternative wiki syntax: (Emacs) Org-mode. Note that Org-mode is not just dumb wiki syntax like Markdown or so, under the syntax surface is another very powerful and featurerich Lisp application that can do amazing things, see ,---- | orgmode.org `---- The gitrepo of my iOrg project can be found here: ,---- | https://github.com/tj64/iorg `---- Its the PicoLisp Wiki, but calls the Org-mode exporter to render the (Org-mode) markup, instead of using the PicoLisp render function from Alex. This works! There is even support for emacs-w3m mode for editing the wiki pages, i.e. instead of opening a small text buffer for editing an textarea (the usual behaviour), emacs-w3m opens an Org-mode buffer for editing iOrg wiki pages. The changes from the Org-mode buffer are then committed to the web application (the wiki) just like any other html form that is edited with emacs-w3m. I haven't touched it for a long time, but this part of the project worked very well IIRC. Thank to Alex for all his help back then! The project was more ambitious, there is a pretty far developed web interface for org-mode trees/nodes, that almost worked, but then I had to move to other shores and could not finish it. But I'm still interested in this project, because Emacs Org-mode is the most powerful static website/document generator anyone can think of, and using Emacs Org-mode as syntax for the PicoLisp wiki would combine my two favorite pieces of software. Under the hood, an Org-mode document is a nested (Emacs Lisp) list, which is of course very convenient from a PicoLisp point of view. Unfortunately, the Org-mode parser (org-element.el) makes use of some unique Emacs Lisp features (circular lists, text properties ...) that complicated my life tremendously when trying to make the two apps talk to each other. So if extending the PicoLisp markup is on the agenda right now - why not try a revival of the iOrg project? I would be happy about feedback and contributions. > True, but again it holds what I said about too much abstraction. I've > shot myself into the food this way many times. That made me really curios - was it vegetables, meat, or rather seafood? ;-) -- cheers, Thorsten -- UNSUBSCRIBE: mailto:picolisp@software-lab.de?subject=Unsubscribe
