emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <dominik@science.uva.nl>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-publish future ?
Date: Tue, 6 Jun 2006 12:03:52 +0200	[thread overview]
Message-ID: <8bc0ad0ebe18824fed0f19f550075611@science.uva.nl> (raw)
In-Reply-To: <1839ad060606051303v6d94b45buf7923eebc95159a4@mail.gmail.com>


What I like about org-publish is that it is general, and really 
focusses on the essentials of just the publishing process, without 
intermingling these issues with the formatting issues.  I believe you 
could publish muse files and bhdl files with org-publish, by just 
calling the appropriate functions or if necessary write a trivial 
wrapper around them.  Maybe you could also publish Org-mode files with 
Muse, I am not sure.

I myself don't see Org-mode primarily as a publishing tool at all.  The 
motivation for writing Org-mode was twofold:

- to get to a handle on the many things I need to do
- to collect all ideas that I had for writing plain text notes
   in Emacs into a single mode.  For me, Org-mode is vastly more
   convenient to use that any other text mode I know of.

David's org-publish gave me a one-key way to get these files on a 
webpage, something I use mostly internally to share notes with 
collaborators.  Importantly, I can let it take care of also updating 
any additional files like source code that might have changed and need 
updating.  That is exactly what I need.

About future development: I really like how basic and straight 
org-publish is.  No need to create another monster.  Maybe add a few 
more general publishing-functions (right now there are only two: 
org-to-html, and a plain copy for attachments) to save some users from 
writing their own.  But the basic setup looks fine and complete to me.

- Carsten


On Jun 5, 2006, at 22:03, Xavier Maillard wrote:

> Hi,
>
> I was looking on emacswiki searching for publish engines for Emacs. 
> Actually, I have found at least three of them:
>
> 1. muse
> 2. emacs-wiki
> 3. bhl
>
> Adding org-publish to this list, we got 4 engines that do merely the 
> same thing except for org-publish which offers less features. So what 
> is the current goal for org-publish exactly ? Is there any possiblity 
> that org-publish be incorporated into something bigger and more 
> insteresting for us as end users. are there any plans for orc-publish 
> if at all ?
>
> I know David is quite busy with all his projects but I would like to 
> know if it is worth I learn org-publish in depth or switch to 
> something else. So David, what are your plans ? :)
>
> Regards
> -- 

  reply	other threads:[~2006-06-06 10:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-05 20:03 org-publish future ? Xavier Maillard
2006-06-06 10:03 ` Carsten Dominik [this message]
2006-06-06 13:57   ` Michael Olson
2006-06-07 13:08     ` Carsten Dominik
2006-06-07 13:29       ` Michael Olson
2006-06-10 12:24 ` 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=8bc0ad0ebe18824fed0f19f550075611@science.uva.nl \
    --to=dominik@science.uva.nl \
    --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).