From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Re: Organize Your Life In Plain Text! Date: Thu, 14 May 2009 13:36:50 +0200 Message-ID: <677A32B5-8CBD-4863-B06C-B4E3D0A46F29@gmail.com> References: <87zldovowk.fsf@gollum.intra.norang.ca> <87bppxojos.fsf@gollum.intra.norang.ca> <4D5BC81A-63F1-49E3-87BB-21000C1C115B@gmail.com> <87y6t1mz0e.fsf@gollum.intra.norang.ca> <87y6t1coa5.fsf@kassiopeya.MSHEIMNETZ> Mime-Version: 1.0 (Apple Message framework v930.3) Content-Type: multipart/mixed; boundary="===============0984688723==" Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M4ZFH-00065x-Rz for emacs-orgmode@gnu.org; Thu, 14 May 2009 07:37:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M4ZFD-00064j-Os for emacs-orgmode@gnu.org; Thu, 14 May 2009 07:37:03 -0400 Received: from [199.232.76.173] (port=48967 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M4ZFD-00064d-GA for emacs-orgmode@gnu.org; Thu, 14 May 2009 07:36:59 -0400 Received: from ey-out-1920.google.com ([74.125.78.144]:63301) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M4ZFC-0006jO-BQ for emacs-orgmode@gnu.org; Thu, 14 May 2009 07:36:59 -0400 Received: by ey-out-1920.google.com with SMTP id 13so288256eye.24 for ; Thu, 14 May 2009 04:36:57 -0700 (PDT) In-Reply-To: <87y6t1coa5.fsf@kassiopeya.MSHEIMNETZ> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastian Rose Cc: Bernt Hansen , emacs-orgmode@gnu.org --===============0984688723== Content-Type: multipart/alternative; boundary=Apple-Mail-4--146678248 --Apple-Mail-4--146678248 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit On May 13, 2009, at 12:04 PM, Sebastian Rose wrote: > > I like the idea of publishing the sources. I have just pushed a change which implements org-publish-org-to-org, so you should be able to use this in a publishing setup. It is also possible to get an htmlized version of the file. The way to use this would be to specify two publishing functions, and to specify the kinds of source file representations with parameters in org-publish-alist, like this: :publishing-function (org-publish-org-to-html org-publish-org-to-org) :plain-source t :htmlized-source t for a file file.org, this would give you both file.org and file.org.html in the publishing directory. In both files, archived trees, commented trees and trees excluded by tags from export would have been removed. The html version will look just like your org buffer in Emacs. If you want to use this in batch processing, you need a CSS file that defines the font colors and set it's location in `org-export-htmlized- org-css-url'. The CSS file can be generated in an interactive Emacs session with M-x org- export-htmlize-generate-css. - Carsten > > Shouldn't we do something like this on worg too? > > It's amazing to see the too files side by side - both perfectly > readable - visible simplicity and a great source of examples for > (potentially new) users. > > BTW: it would be real fun to tranform links for this purpose, so that > visitors could browse the published org sources just like in emacs. > > > > We could as well this here > > [[http://repo.or.cz/w/Worg.git?a=blob;f=org-tutorials/org-publish-html-tutorial.org > ][Source > of this file]] > > > Maybe in the tutorial index (e.g.)? > > > ... > > * Publishing org to html > #+ATTR_HTML: title="See sources of that file (git repo on repo.or.cz)" > [[http://repo.or.cz/w/Worg.git?a=blob;f=org-tutorials/org-publish-html-tutorial.org > ][(src)]] > > .... > > > Sebastian > > > Bernt Hansen writes: >> Carsten Dominik writes: >> >>> On May 13, 2009, at 3:50 AM, Bernt Hansen wrote: >>> >>>> Rick Moynihan writes: >>>> >>>>> Another comment (and this goes for many documents published in >>>>> org-mode) is that it would be nice if the HTML file could link >>>>> to an >>>>> online copy of the raw org file. >>>> >>>> More thoughts along this line... >>>> >>>> The only downside of doing this automatically is if you >>>> include :noexport: tags or COMMENT on headlines to prevent export >>>> (say >>>> you have information you don't want out on the net. >>>> >>>> I wouldn't want the source file automatically published always. >>>> I'm >>>> like to be able to control that from some org-publish >>>> configuration. >>> >>> I guess it would be relatively easy to write a function >>> `org-publish-org-to-org' which would remove these sensitive >>> parts and could be used as as :publishing-function in a setup >> >> That works for me :) I prefer to post my source with the published >> files for most things -- my old publishing method (before switching >> to >> org-mode) used to do that (without the noexport options -- since it >> had >> no concept of not publishing everything). >> >> -Bernt --Apple-Mail-4--146678248 Content-Type: text/html; charset=US-ASCII Content-Transfer-Encoding: quoted-printable
On May 13, 2009, = at 12:04 PM, Sebastian Rose wrote:


I like the idea of publishing the = sources.

I have just pushed a = change which implements org-publish-org-to-org,
so you should = be able to use this in a publishing setup.  It is = also
possible to get an htmlized version of the file. =  The way to use
this would be to specify = two publishing functions, and to specify
the kinds of = source file representations with parameters
in = org-publish-alist, like = this: 

  :publishing-function = (org-publish-org-to-html = org-publish-org-to-org)
  :plain-source = t
  :htmlized-source t

for = a file file.org, this would give you both file.org and = file.org.html
in the publishing directory.  In both = files, archived trees, commented
trees and trees excluded by = tags from export would have been removed.
The html version = will look just like your org buffer in = Emacs.

If you want to use this in batch = processing, you need a CSS file that defines the font colors and set = it's location in `org-export-htmlized-org-css-url'. =  The
CSS file can be generated in an interactive Emacs = session with = M-x org-export-htmlize-generate-css.

- = Carsten


Shouldn't we do = something like this on worg too?

It's amazing to see the too = files side by side - both perfectly
readable - visible simplicity and = a great source of examples for
(potentially new) users.

BTW: = it would be real fun to tranform links for this purpose, so = that
visitors could browse the published org sources just like in = emacs.



We could as well this here

[[http://repo.or.cz/w/Worg.git?a=3Dblob;f=3Dorg-tutoria= ls/org-publish-html-tutorial.org][Source
of this = file]]


Maybe in the tutorial index = (e.g.)?


...

* Publishing org to html
#+ATTR_HTML: = title=3D"See sources of that file (git repo on repo.or.cz)"
[[http://repo.or.cz/w/Worg.git?a=3Dblob;f=3Dorg-tutoria= ls/org-publish-html-tutorial.org][(src)]]

....


=   Sebastian


Bernt Hansen <bernt@norang.ca> = writes:
Carsten Dominik <carsten.dominik@gmail.com>= ; writes:

On May 13, 2009, at 3:50 AM, Bernt Hansen = wrote:

Rick = Moynihan <rick.moynihan@gmail.com> = writes:

Another comment (and this goes = for many documents published = in
org-mode) is that it would be = nice if the HTML file could link to = an
online copy of the raw org = file.

More = thoughts along this = line...

The = only downside of doing this automatically is if = you
include = :noexport: tags or COMMENT on headlines to prevent export = (say
you = have information you don't want out on the = net.

I = wouldn't want the source file automatically published always. =  I'm
like = to be able to control that from some org-publish = configuration.

I guess it would be relatively = easy to write a function
`org-publish-org-to-org' which = would remove these sensitive
parts and could be used as as = :publishing-function in a setup

That works for = me :)  I prefer to post my source with the = published
files for most = things -- my old publishing method (before switching = to
org-mode) used to do that = (without the noexport options -- since it = had
no concept of not = publishing everything).

-Bernt

<= /html>= --Apple-Mail-4--146678248-- --===============0984688723== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode --===============0984688723==--