From: Sebastian Rose <sebastian_rose@gmx.de>
To: Bernt Hansen <bernt@norang.ca>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: Organize Your Life In Plain Text!
Date: Wed, 13 May 2009 12:04:02 +0200 [thread overview]
Message-ID: <87y6t1coa5.fsf@kassiopeya.MSHEIMNETZ> (raw)
In-Reply-To: <87y6t1mz0e.fsf@gollum.intra.norang.ca> (Bernt Hansen's message of "Wed, 13 May 2009 00:02:09 -0400")
I like the idea of publishing the sources.
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 <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
next prev parent reply other threads:[~2009-05-13 10:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 16:49 Organize Your Life In Plain Text! Bernt Hansen
2009-05-07 18:22 ` Rick Moynihan
2009-05-07 18:44 ` Bernt Hansen
[not found] ` <4a035da6.0407560a.7391.ffffc270@mx.google.com>
2009-05-07 22:32 ` Bernt Hansen
2009-05-08 2:10 ` Memnon Anon
2009-05-08 3:04 ` Bernt Hansen
2009-05-07 22:50 ` Jonathan Arkell
2009-05-08 1:35 ` Rick Moynihan
2009-05-08 1:46 ` Eric Schulte
2009-05-08 14:08 ` Carsten Dominik
2009-05-08 15:32 ` Eric Schulte
2009-05-08 16:19 ` Carsten Dominik
2009-05-13 0:22 ` Rick Moynihan
2009-05-13 1:39 ` Bernt Hansen
2009-05-13 1:50 ` Bernt Hansen
2009-05-13 3:58 ` Carsten Dominik
2009-05-13 4:02 ` Bernt Hansen
2009-05-13 10:04 ` Sebastian Rose [this message]
2009-05-13 10:15 ` Rick Moynihan
2009-05-14 13:33 ` Eric Schulte
2009-05-14 19:30 ` Sebastian Rose
2009-05-14 19:55 ` Keith Lancaster
2009-05-14 22:16 ` Eric Schulte
2009-05-15 6:54 ` Ian Barton
2009-05-15 22:18 ` Eric Schulte
2009-05-16 6:56 ` Ian Barton
2009-05-17 21:49 ` Eric Schulte
2009-05-18 6:06 ` Ian Barton
2009-05-18 13:17 ` Eric Schulte
2009-05-19 9:19 ` Ian Barton
2009-05-14 11:36 ` Carsten Dominik
2009-05-14 19:11 ` Bernt Hansen
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=87y6t1coa5.fsf@kassiopeya.MSHEIMNETZ \
--to=sebastian_rose@gmx.de \
--cc=bernt@norang.ca \
--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).