emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
* Release 6.13
@ 2008-11-23  7:20 Carsten Dominik
  2008-11-23 18:24 ` Bernt Hansen
  0 siblings, 1 reply; 11+ messages in thread
From: Carsten Dominik @ 2008-11-23  7:20 UTC (permalink / raw)
  To: emacs-orgmode Org-Mode

Hi,

I have released Org-mode 6.13.

Enjoy!

- Carsten



Changes in Version 6.13
=======================

Overview
========

    - Keybindings in Remember buffers can be configured
    - Support for ido completion
    - New face for date lines in agenda column view
    - Invisible targets become now anchors in headlines.
    - New contributed file /org-exp-blocks.el/
    - New contributed file /org-eval-light.el/
    - Link translation
    - BBDB links may use regular expressions.
    - Link abbreviations can use %h to insert a url-encoded target value
    - Improved XHTML compliance

Details
=======

Keybindings in Remember buffers can be configured
-------------------------------------------------

     The remember buffers created with Org's extensions are in
     Org-mode, which is nice to prepare snippets that will
     actually be stored in Org-mode files.  However, this makes it
     hard to configure key bindings without modifying the Org-mode
     keymap.  There is now a minor mode active in these buffers,
     `org-remember-mode', and its keymap org-remember-mode-map can
     be used for key bindings.  By default, this map only contains
     the bindings for `C-c C-c' to store the note, and `C-c C-k'
     to abort it.  Use `org-remember-mode-hook' to define your own
     bindings like

   (add-hook
    'org-remember-mode-hook
    (lambda ()
      (define-key org-remember-mode-map
        "\C-x\C-s" 'org-remember-finalize)))


     If you wish, you can also use this to free the `C-c C-c'
     binding (by binding this key to nil in the minor mode map),
     so that you can use `C-c C-c' again to set tags.

     This modification is based on a request by Tim O'Callaghan.

Support for ido completion
--------------------------

     You can now get the completion interface from /ido.el/ for
     many of Org's internal completion commands by turning on the
     variable `org-completion-use-ido'. `ido=mode' must also be
     active before you can use this.

     This change is based upon a request by Samuel Wales.

New face for date lines in agenda column view
---------------------------------------------

     When column view is active in the agenda, and when you have
     summarizing properties, the date lines become normal column
     lines and the separation between different days becomes
     harder to see.  If this bothers you, you can now customize
     the face `org-agenda-column-dateline'.

     This is based on a request by George Pearson.

Invisible targets become now anchors in headlines.
--------------------------------------------------

     These anchors can be used to jump to a directly with an HTML
     link, just like the `sec-xxx' ids.  For example, the
     following will make a http link
     `//domain/path-to-my-file.html#dummy' work:

       # <<dummy>>
       *** a headline

     This is based on a request by Matt Lundin.

New contributed file /org-exp-blocks.el/
----------------------------------------

     This new file implements special export behavior of
     user-defined blocks.  The currently supported blocks are

     - comment :: Comment blocks with author-specific markup
     - ditaa ::  conversion of ASCII art into pretty png files
          using Stathis  Sideris' /ditaa.jar/ program
     - dot :: creation of graphs in the /dot/ language
     - R :: Sweave type exporting using the R program

     For more details and examples, see the file commentary in
     /org-exp-blocks.el/.

     Kudos to Eric Schulte for this new functionality, after
     /org-plot.el/ already his second major contribution.  Thanks
     to Stathis for this excellent program, and for allowing us to
     bundle it with Org-mode.

New contributed file /org-eval-light.el/
----------------------------------------

     This module gives contrib over execution Emacs Lisp code
     blocks included in a file.

     Thanks to Eric Schulte also for this file.

Link translation
----------------

     You can now configure Org to understand many links created
     with the Emacs Planner package, so you can cut text from
     planner pages and paste them into Org-mode files without
     having to re-write the links.  Among other things, this means
     that the command `org-open-at-point-global' which follows
     links not only in Org-mode, but in arbitrary files like
     source code files etc, will work also with links created by
     planner. The following customization es needed to make all of
     this work

   (setq org-link-translation-function
         'org-translate-link-from-planner)


    I guess an inverse translator could be written and integrated
    into Planner.

BBDB links may use regular expressions.
---------------------------------------

     This did work all along, but only now I have documented it.

`yank-pop' works again after yanking an outline tree
----------------------------------------------------

     Samuel Wales had noticed that org-yank did mess up this
     functionality.  Now you can use `yank-pop' again, the only
     restriction is that the so-yanked text will not be
     pro/demoted or folded.

Link abbreviations can use %h to insert a url-encoded target value
------------------------------------------------------------------

     Thanks to Steve Purcell for a patch to this effect.

Improved XHTML compliance
-------------------------

     Thanks to Sebastian Rose for pushing this.

Many bug fixes again.
---------------------

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Release 6.13
  2008-11-23  7:20 Release 6.13 Carsten Dominik
@ 2008-11-23 18:24 ` Bernt Hansen
  2008-11-24  2:12   ` Sebastian Rose
  2008-11-25  1:31   ` Sebastian Rose
  0 siblings, 2 replies; 11+ messages in thread
From: Bernt Hansen @ 2008-11-23 18:24 UTC (permalink / raw)
  To: Carsten Dominik; +Cc: emacs-orgmode Org-Mode

Carsten Dominik <dominik@science.uva.nl> writes:

> New contributed file /org-exp-blocks.el/
> ----------------------------------------
>
>     This new file implements special export behavior of
>     user-defined blocks.  The currently supported blocks are
>
>     - comment :: Comment blocks with author-specific markup
>     - ditaa ::  conversion of ASCII art into pretty png files
>          using Stathis  Sideris' /ditaa.jar/ program
>     - dot :: creation of graphs in the /dot/ language
>     - R :: Sweave type exporting using the R program
>
>     For more details and examples, see the file commentary in
>     /org-exp-blocks.el/.
>
>     Kudos to Eric Schulte for this new functionality, after
>     /org-plot.el/ already his second major contribution.  Thanks
>     to Stathis for this excellent program, and for allowing us to
>     bundle it with Org-mode.

Thanks for this!  I really like that C-c ' now makes editing the ditaa
images easy.

Now for my questions related to improving my work-flow for generating
documents with ditaa images.

Q1: Can org-publish-current-project somehow automatically pick up ditaa
    generated images?

    I have a play org file http://doc.norang.ca/org-mode.org which
    generates the page at http://doc.norang.ca/org-mode.html.

    I usually edit the source file and then
       M-x org-publish-current-project
    to publish my changes.

    This was working great... until ditaa came along :).

    Now exporting my .org files creates new ditaa generated images (.png
    files) which don't get exported with the document because they are
    part of a different project.  After org-publish-current-project I
    have to remember to also org-publish doc-png to get the ditaa
    generated images published.

    Publishing the parent project 'doc' instead

      doc
         doc-org (org -> HTML export -> publishing target)
         doc-png (copy .png          -> publishing target)

    works fine so maybe I just need fix my workflow so my publish code
    is smart enough to find the appropriate parent project and publish
    that instead.

Q2: Can org-publish handle a source file in more than one project?

    Sometimes I would like to publish the generated page (org-mode.html)
    as well as the source file that creates it (org-mode.org) as in Q1
    above.  I don't think I can have a doc-org project that generates
    HTML and a doc-src project that just copies the .org files verbatim
    to the target directory since after publishing one of the two
    projects the file is 'unchanged' and skipped for publishing the
    second one.  Is there a way to accomplish this?

    For now I'm manually touching the org file and manually publishing
    the doc-src project to make it work.


ditaa images look great on HTML exports.  I'm having some difficulty
including them in other formats (PDF for instance - they end up being
tiny.)  Someday I'll find a good solution for that.
http://doc.norang.ca/org-mode.pdf is an example.

Thanks for org-mode!

Regards,
Bernt

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Re: Release 6.13
  2008-11-23 18:24 ` Bernt Hansen
@ 2008-11-24  2:12   ` Sebastian Rose
  2008-11-24 21:23     ` Bernt Hansen
  2008-11-25  1:31   ` Sebastian Rose
  1 sibling, 1 reply; 11+ messages in thread
From: Sebastian Rose @ 2008-11-24  2:12 UTC (permalink / raw)
  To: emacs-orgmode Org-Mode

Hi Bernt,


this is how it works here:


(setq org-publish-project-alist
      '(("org-notes"
         :base-directory "~/emacs/org/notes/"
         :auto-index t
         :index-filename "sitemap.org"
         :index-title "Sitemap"
         :recursive t
         :base-extension "org"
         ;; this could be: "/ssh:user@host:~/html/notebook/"
         :publishing-directory "~/public_html/org-notes/"
         :publishing-function org-publish-org-to-html
         :headline-levels 4
                                        ;:section-numbers nil
                                        ;:table-of-contents nil
         :auto-preamble t
                                        ;:auto-postamble nil
         :style "<link rel=\"stylesheet\" href=\"stylesheet.css\" type=\"text/css\" />"

         )
        ("org-notes-static"
         :base-directory "~/emacs/org/notes/"
         :recursive t
         :base-extension "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf\\|txt\\|htm\\|html\\|dtd\\|php"
         :publishing-directory "~/public_html/org-notes/"
         :publishing-function org-publish-attachment)

        ("org" :components ("org-notes" "org-notes-static"))


This way first the *.org files are published (and thus ditaa images are
created in :base-directory) and then the new generated images.





Best,

   Sebastian


Bernt Hansen <bernt@norang.ca> writes:
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> New contributed file /org-exp-blocks.el/
>> ----------------------------------------
>>
>>     This new file implements special export behavior of
>>     user-defined blocks.  The currently supported blocks are
>>
>>     - comment :: Comment blocks with author-specific markup
>>     - ditaa ::  conversion of ASCII art into pretty png files
>>          using Stathis  Sideris' /ditaa.jar/ program
>>     - dot :: creation of graphs in the /dot/ language
>>     - R :: Sweave type exporting using the R program
>>
>>     For more details and examples, see the file commentary in
>>     /org-exp-blocks.el/.
>>
>>     Kudos to Eric Schulte for this new functionality, after
>>     /org-plot.el/ already his second major contribution.  Thanks
>>     to Stathis for this excellent program, and for allowing us to
>>     bundle it with Org-mode.
>
> Thanks for this!  I really like that C-c ' now makes editing the ditaa
> images easy.
>
> Now for my questions related to improving my work-flow for generating
> documents with ditaa images.
>
> Q1: Can org-publish-current-project somehow automatically pick up ditaa
>     generated images?
>
>     I have a play org file http://doc.norang.ca/org-mode.org which
>     generates the page at http://doc.norang.ca/org-mode.html.
>
>     I usually edit the source file and then
>        M-x org-publish-current-project
>     to publish my changes.
>
>     This was working great... until ditaa came along :).
>
>     Now exporting my .org files creates new ditaa generated images (.png
>     files) which don't get exported with the document because they are
>     part of a different project.  After org-publish-current-project I
>     have to remember to also org-publish doc-png to get the ditaa
>     generated images published.
>
>     Publishing the parent project 'doc' instead
>
>       doc
>          doc-org (org -> HTML export -> publishing target)
>          doc-png (copy .png          -> publishing target)
>
>     works fine so maybe I just need fix my workflow so my publish code
>     is smart enough to find the appropriate parent project and publish
>     that instead.
>
> Q2: Can org-publish handle a source file in more than one project?
>
>     Sometimes I would like to publish the generated page (org-mode.html)
>     as well as the source file that creates it (org-mode.org) as in Q1
>     above.  I don't think I can have a doc-org project that generates
>     HTML and a doc-src project that just copies the .org files verbatim
>     to the target directory since after publishing one of the two
>     projects the file is 'unchanged' and skipped for publishing the
>     second one.  Is there a way to accomplish this?
>
>     For now I'm manually touching the org file and manually publishing
>     the doc-src project to make it work.
>
>
> ditaa images look great on HTML exports.  I'm having some difficulty
> including them in other formats (PDF for instance - they end up being
> tiny.)  Someday I'll find a good solution for that.
> http://doc.norang.ca/org-mode.pdf is an example.
>
> Thanks for org-mode!
>
> Regards,
> Bernt
>
>
>
>
>
> _______________________________________________
> 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
>

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose emma-stil de, sebastian_rose gmx de
Http:  www.emma-stil.de

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Release 6.13
  2008-11-24  2:12   ` Sebastian Rose
@ 2008-11-24 21:23     ` Bernt Hansen
  0 siblings, 0 replies; 11+ messages in thread
From: Bernt Hansen @ 2008-11-24 21:23 UTC (permalink / raw)
  To: Sebastian Rose; +Cc: emacs-orgmode Org-Mode

Sebastian Rose <sebastian_rose@gmx.de> writes:

> This way first the *.org files are published (and thus ditaa images are
> created in :base-directory) and then the new generated images.

Thanks for the response Sebastian.

I already have my projects set up like this - it's just that I need to
break my (bad) habit of using org-publish-current-project when editing a
*.org file which has ditaa images since this does not publish the images
too.

I'll just fix my work flow so that I use the org-publish function
instead of org-publish-current-project.

-Bernt

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Re: Release 6.13
  2008-11-23 18:24 ` Bernt Hansen
  2008-11-24  2:12   ` Sebastian Rose
@ 2008-11-25  1:31   ` Sebastian Rose
  2008-11-25  1:48     ` Sebastian Rose
  1 sibling, 1 reply; 11+ messages in thread
From: Sebastian Rose @ 2008-11-25  1:31 UTC (permalink / raw)
  To: emacs-orgmode Org-Mode



OK, here is the patch. This ensures, that the whole project is published
for

C-c C-e P

Hence ditaa blocks can be exported together with a changed Org-file
again.



diff --git a/lisp/org-publish.el b/lisp/org-publish.el
index eafa8fa..3ec48c4 100644
--- a/lisp/org-publish.el
+++ b/lisp/org-publish.el
@@ -470,7 +470,11 @@ matching filenames."
 (defun org-publish-get-project-from-filename (filename)
   "Return the project FILENAME belongs."
   (let* ((project-name (cdr (assoc (expand-file-name filename)
-                                  org-publish-files-alist))))
+                                  org-publish-files-alist)))
+        (parent-project nil))
+    (dolist (prj org-publish-project-alist)
+      (if (member project-name (plist-get (cdr prj) :components))
+          (setq project-name (car prj))))
     (assoc project-name org-publish-project-alist)))
 
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;



Regards,


  Sebastian









Bernt Hansen <bernt@norang.ca> writes:
> Carsten Dominik <dominik@science.uva.nl> writes:
>
>> New contributed file /org-exp-blocks.el/
>> ----------------------------------------
>>
>>     This new file implements special export behavior of
>>     user-defined blocks.  The currently supported blocks are
>>
>>     - comment :: Comment blocks with author-specific markup
>>     - ditaa ::  conversion of ASCII art into pretty png files
>>          using Stathis  Sideris' /ditaa.jar/ program
>>     - dot :: creation of graphs in the /dot/ language
>>     - R :: Sweave type exporting using the R program
>>
>>     For more details and examples, see the file commentary in
>>     /org-exp-blocks.el/.
>>
>>     Kudos to Eric Schulte for this new functionality, after
>>     /org-plot.el/ already his second major contribution.  Thanks
>>     to Stathis for this excellent program, and for allowing us to
>>     bundle it with Org-mode.
>
> Thanks for this!  I really like that C-c ' now makes editing the ditaa
> images easy.
>
> Now for my questions related to improving my work-flow for generating
> documents with ditaa images.
>
> Q1: Can org-publish-current-project somehow automatically pick up ditaa
>     generated images?
>
>     I have a play org file http://doc.norang.ca/org-mode.org which
>     generates the page at http://doc.norang.ca/org-mode.html.
>
>     I usually edit the source file and then
>        M-x org-publish-current-project
>     to publish my changes.
>
>     This was working great... until ditaa came along :).
>
>     Now exporting my .org files creates new ditaa generated images (.png
>     files) which don't get exported with the document because they are
>     part of a different project.  After org-publish-current-project I
>     have to remember to also org-publish doc-png to get the ditaa
>     generated images published.
>
>     Publishing the parent project 'doc' instead
>
>       doc
>          doc-org (org -> HTML export -> publishing target)
>          doc-png (copy .png          -> publishing target)
>
>     works fine so maybe I just need fix my workflow so my publish code
>     is smart enough to find the appropriate parent project and publish
>     that instead.
>
> Q2: Can org-publish handle a source file in more than one project?
>
>     Sometimes I would like to publish the generated page (org-mode.html)
>     as well as the source file that creates it (org-mode.org) as in Q1
>     above.  I don't think I can have a doc-org project that generates
>     HTML and a doc-src project that just copies the .org files verbatim
>     to the target directory since after publishing one of the two
>     projects the file is 'unchanged' and skipped for publishing the
>     second one.  Is there a way to accomplish this?
>
>     For now I'm manually touching the org file and manually publishing
>     the doc-src project to make it work.
>
>
> ditaa images look great on HTML exports.  I'm having some difficulty
> including them in other formats (PDF for instance - they end up being
> tiny.)  Someday I'll find a good solution for that.
> http://doc.norang.ca/org-mode.pdf is an example.
>
> Thanks for org-mode!
>
> Regards,
> Bernt
>
>
>
>
>
> _______________________________________________
> 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
>

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose emma-stil de, sebastian_rose gmx de
Http:  www.emma-stil.de

^ permalink raw reply related	[flat|nested] 11+ messages in thread

* Re: Re: Release 6.13
  2008-11-25  1:31   ` Sebastian Rose
@ 2008-11-25  1:48     ` Sebastian Rose
  2008-11-25  4:36       ` Carsten Dominik
  2008-11-25  9:56       ` Carsten Dominik
  0 siblings, 2 replies; 11+ messages in thread
From: Sebastian Rose @ 2008-11-25  1:48 UTC (permalink / raw)
  To: emacs-orgmode Org-Mode

Arrgh....

Sorry - there was an unnecessary line.


diff --git a/lisp/org-publish.el b/lisp/org-publish.el
index eafa8fa..3ec48c4 100644
--- a/lisp/org-publish.el
+++ b/lisp/org-publish.el
@@ -470,7 +470,11 @@ matching filenames."
 (defun org-publish-get-project-from-filename (filename)
   "Return the project FILENAME belongs."
   (let* ((project-name (cdr (assoc (expand-file-name filename)
                                    org-publish-files-alist))))
+    (dolist (prj org-publish-project-alist)
+      (if (member project-name (plist-get (cdr prj) :components))
+          (setq project-name (car prj))))
     (assoc project-name org-publish-project-alist)))
 
 ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;



Regards,

  Sebastian


Sebastian Rose <sebastian_rose@gmx.de> writes:
> OK, here is the patch. This ensures, that the whole project is published
> for
>
> C-c C-e P
>
> Hence ditaa blocks can be exported together with a changed Org-file
> again.
>
>
>
> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
> index eafa8fa..3ec48c4 100644
> --- a/lisp/org-publish.el
> +++ b/lisp/org-publish.el
> @@ -470,7 +470,11 @@ matching filenames."
>  (defun org-publish-get-project-from-filename (filename)
>    "Return the project FILENAME belongs."
>    (let* ((project-name (cdr (assoc (expand-file-name filename)
> -                                  org-publish-files-alist))))
> +                                  org-publish-files-alist)))
> +        (parent-project nil))
> +    (dolist (prj org-publish-project-alist)
> +      (if (member project-name (plist-get (cdr prj) :components))
> +          (setq project-name (car prj))))
>      (assoc project-name org-publish-project-alist)))
>  
>  ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>
>
>
> Regards,
>
>
>   Sebastian
>
>
>
>
>
>
>
>
>
> Bernt Hansen <bernt@norang.ca> writes:
>> Carsten Dominik <dominik@science.uva.nl> writes:
>>
>>> New contributed file /org-exp-blocks.el/
>>> ----------------------------------------
>>>
>>>     This new file implements special export behavior of
>>>     user-defined blocks.  The currently supported blocks are
>>>
>>>     - comment :: Comment blocks with author-specific markup
>>>     - ditaa ::  conversion of ASCII art into pretty png files
>>>          using Stathis  Sideris' /ditaa.jar/ program
>>>     - dot :: creation of graphs in the /dot/ language
>>>     - R :: Sweave type exporting using the R program
>>>
>>>     For more details and examples, see the file commentary in
>>>     /org-exp-blocks.el/.
>>>
>>>     Kudos to Eric Schulte for this new functionality, after
>>>     /org-plot.el/ already his second major contribution.  Thanks
>>>     to Stathis for this excellent program, and for allowing us to
>>>     bundle it with Org-mode.
>>
>> Thanks for this!  I really like that C-c ' now makes editing the ditaa
>> images easy.
>>
>> Now for my questions related to improving my work-flow for generating
>> documents with ditaa images.
>>
>> Q1: Can org-publish-current-project somehow automatically pick up ditaa
>>     generated images?
>>
>>     I have a play org file http://doc.norang.ca/org-mode.org which
>>     generates the page at http://doc.norang.ca/org-mode.html.
>>
>>     I usually edit the source file and then
>>        M-x org-publish-current-project
>>     to publish my changes.
>>
>>     This was working great... until ditaa came along :).
>>
>>     Now exporting my .org files creates new ditaa generated images (.png
>>     files) which don't get exported with the document because they are
>>     part of a different project.  After org-publish-current-project I
>>     have to remember to also org-publish doc-png to get the ditaa
>>     generated images published.
>>
>>     Publishing the parent project 'doc' instead
>>
>>       doc
>>          doc-org (org -> HTML export -> publishing target)
>>          doc-png (copy .png          -> publishing target)
>>
>>     works fine so maybe I just need fix my workflow so my publish code
>>     is smart enough to find the appropriate parent project and publish
>>     that instead.
>>
>> Q2: Can org-publish handle a source file in more than one project?
>>
>>     Sometimes I would like to publish the generated page (org-mode.html)
>>     as well as the source file that creates it (org-mode.org) as in Q1
>>     above.  I don't think I can have a doc-org project that generates
>>     HTML and a doc-src project that just copies the .org files verbatim
>>     to the target directory since after publishing one of the two
>>     projects the file is 'unchanged' and skipped for publishing the
>>     second one.  Is there a way to accomplish this?
>>
>>     For now I'm manually touching the org file and manually publishing
>>     the doc-src project to make it work.
>>
>>
>> ditaa images look great on HTML exports.  I'm having some difficulty
>> including them in other formats (PDF for instance - they end up being
>> tiny.)  Someday I'll find a good solution for that.
>> http://doc.norang.ca/org-mode.pdf is an example.
>>
>> Thanks for org-mode!
>>
>> Regards,
>> Bernt
>>
>>
>>
>>
>>
>> _______________________________________________
>> 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
>>

-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose emma-stil de, sebastian_rose gmx de
Http:  www.emma-stil.de

^ permalink raw reply related	[flat|nested] 11+ messages in thread

* Re: Re: Release 6.13
  2008-11-25  1:48     ` Sebastian Rose
@ 2008-11-25  4:36       ` Carsten Dominik
  2008-11-25  8:32         ` Sebastian Rose
  2008-11-25  9:56       ` Carsten Dominik
  1 sibling, 1 reply; 11+ messages in thread
From: Carsten Dominik @ 2008-11-25  4:36 UTC (permalink / raw)
  To: Sebastian Rose; +Cc: emacs-orgmode Org-Mode

Hi Sebastian,

it seems to me thatt his patch depends on the projects in
org-publish-projects-alist to be defined in a certain order,
with the components first, and the big "parent" projects later.
So maybe you need to iterate the dolist loop until it stabilizes.

Also, I guess a "component" could be part of several "parents"?
Hmm, maybe not a likely setup.  OK, les not worry about this issue.

- Carsten

On Nov 25, 2008, at 2:48 AM, Sebastian Rose wrote:

> Arrgh....
>
> Sorry - there was an unnecessary line.
>
>
> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
> index eafa8fa..3ec48c4 100644
> --- a/lisp/org-publish.el
> +++ b/lisp/org-publish.el
> @@ -470,7 +470,11 @@ matching filenames."
> (defun org-publish-get-project-from-filename (filename)
>   "Return the project FILENAME belongs."
>   (let* ((project-name (cdr (assoc (expand-file-name filename)
>                                    org-publish-files-alist))))
> +    (dolist (prj org-publish-project-alist)
> +      (if (member project-name (plist-get (cdr prj) :components))
> +          (setq project-name (car prj))))
>     (assoc project-name org-publish-project-alist)))
>
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>
>
>
> Regards,
>
>  Sebastian
>
>
> Sebastian Rose <sebastian_rose@gmx.de> writes:
>> OK, here is the patch. This ensures, that the whole project is  
>> published
>> for
>>
>> C-c C-e P
>>
>> Hence ditaa blocks can be exported together with a changed Org-file
>> again.
>>
>>
>>
>> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
>> index eafa8fa..3ec48c4 100644
>> --- a/lisp/org-publish.el
>> +++ b/lisp/org-publish.el
>> @@ -470,7 +470,11 @@ matching filenames."
>> (defun org-publish-get-project-from-filename (filename)
>>   "Return the project FILENAME belongs."
>>   (let* ((project-name (cdr (assoc (expand-file-name filename)
>> -                                  org-publish-files-alist))))
>> +                                  org-publish-files-alist)))
>> +        (parent-project nil))
>> +    (dolist (prj org-publish-project-alist)
>> +      (if (member project-name (plist-get (cdr prj) :components))
>> +          (setq project-name (car prj))))
>>     (assoc project-name org-publish-project-alist)))
>>
>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>
>>
>>
>> Regards,
>>
>>
>>  Sebastian
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Bernt Hansen <bernt@norang.ca> writes:
>>> Carsten Dominik <dominik@science.uva.nl> writes:
>>>
>>>> New contributed file /org-exp-blocks.el/
>>>> ----------------------------------------
>>>>
>>>>    This new file implements special export behavior of
>>>>    user-defined blocks.  The currently supported blocks are
>>>>
>>>>    - comment :: Comment blocks with author-specific markup
>>>>    - ditaa ::  conversion of ASCII art into pretty png files
>>>>         using Stathis  Sideris' /ditaa.jar/ program
>>>>    - dot :: creation of graphs in the /dot/ language
>>>>    - R :: Sweave type exporting using the R program
>>>>
>>>>    For more details and examples, see the file commentary in
>>>>    /org-exp-blocks.el/.
>>>>
>>>>    Kudos to Eric Schulte for this new functionality, after
>>>>    /org-plot.el/ already his second major contribution.  Thanks
>>>>    to Stathis for this excellent program, and for allowing us to
>>>>    bundle it with Org-mode.
>>>
>>> Thanks for this!  I really like that C-c ' now makes editing the  
>>> ditaa
>>> images easy.
>>>
>>> Now for my questions related to improving my work-flow for  
>>> generating
>>> documents with ditaa images.
>>>
>>> Q1: Can org-publish-current-project somehow automatically pick up  
>>> ditaa
>>>    generated images?
>>>
>>>    I have a play org file http://doc.norang.ca/org-mode.org which
>>>    generates the page at http://doc.norang.ca/org-mode.html.
>>>
>>>    I usually edit the source file and then
>>>       M-x org-publish-current-project
>>>    to publish my changes.
>>>
>>>    This was working great... until ditaa came along :).
>>>
>>>    Now exporting my .org files creates new ditaa generated images  
>>> (.png
>>>    files) which don't get exported with the document because they  
>>> are
>>>    part of a different project.  After org-publish-current-project I
>>>    have to remember to also org-publish doc-png to get the ditaa
>>>    generated images published.
>>>
>>>    Publishing the parent project 'doc' instead
>>>
>>>      doc
>>>         doc-org (org -> HTML export -> publishing target)
>>>         doc-png (copy .png          -> publishing target)
>>>
>>>    works fine so maybe I just need fix my workflow so my publish  
>>> code
>>>    is smart enough to find the appropriate parent project and  
>>> publish
>>>    that instead.
>>>
>>> Q2: Can org-publish handle a source file in more than one project?
>>>
>>>    Sometimes I would like to publish the generated page (org- 
>>> mode.html)
>>>    as well as the source file that creates it (org-mode.org) as in  
>>> Q1
>>>    above.  I don't think I can have a doc-org project that generates
>>>    HTML and a doc-src project that just copies the .org files  
>>> verbatim
>>>    to the target directory since after publishing one of the two
>>>    projects the file is 'unchanged' and skipped for publishing the
>>>    second one.  Is there a way to accomplish this?
>>>
>>>    For now I'm manually touching the org file and manually  
>>> publishing
>>>    the doc-src project to make it work.
>>>
>>>
>>> ditaa images look great on HTML exports.  I'm having some difficulty
>>> including them in other formats (PDF for instance - they end up  
>>> being
>>> tiny.)  Someday I'll find a good solution for that.
>>> http://doc.norang.ca/org-mode.pdf is an example.
>>>
>>> Thanks for org-mode!
>>>
>>> Regards,
>>> Bernt
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>
> -- 
> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449  
> Hannover
>
> Tel.:  +49 (0)511 - 36 58 472
> Fax:   +49 (0)1805 - 233633 - 11044
> mobil: +49 (0)173 - 83 93 417
> Email: s.rose emma-stil de, sebastian_rose gmx de
> Http:  www.emma-stil.de
>
>
> _______________________________________________
> 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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Re: Release 6.13
  2008-11-25  4:36       ` Carsten Dominik
@ 2008-11-25  8:32         ` Sebastian Rose
  2008-11-25  9:55           ` Carsten Dominik
  0 siblings, 1 reply; 11+ messages in thread
From: Sebastian Rose @ 2008-11-25  8:32 UTC (permalink / raw)
  To: Carsten Dominik; +Cc: emacs-orgmode Org-Mode

Hi Carsten,


Carsten Dominik <dominik@uva.nl> writes:
> Hi Sebastian,
>
> it seems to me thatt his patch depends on the projects in
> org-publish-projects-alist to be defined in a certain order,
> with the components first, and the big "parent" projects later.
> So maybe you need to iterate the dolist loop until it stabilizes.

> Also, I guess a "component" could be part of several "parents"?
> Hmm, maybe not a likely setup.  OK, les not worry about this issue.

org-publish-get-project-from-filename always returned the first matching
project. It still does so, but if one or more composite projects are
found, of which the files project is a component, the last composite is
returned instead. In that, it still does what it always did.

Yes, this depends on a certain kind of setup. But it's the setup from
the example in the docs, so I feel people will most likely use
that. Since one has to provide the `:publishing-function', the only way to
publish static content (e.g. images) AND dynamic content is to provide a
composite project.


The issue came up with org-exp-blocks.el [1]. ditaa blocks contain text,
that is changed, just to update an image. I never ran into this, simply
because I never used `C-c C-e P' [2].


The publishing of a composite project depends on the sequence of it's
`:components' anyway [3].

Maybe this should be mentioned in the docs at the end of section 13.2.2?

=> --->8----------------------------->8----------------------------->8---
'The `:components' in "website" are guaranteed to be published in the
sequence provided.'
<= ---8<-----------------------------8<-----------------------------8<---




All the best,

  Sebastian


=--- Footnotes: ---------------

 [1]  There are more `up-to-date issues' in the publishing (e.g. an
      #+INCLUDE index.org). Yet, we shouldn't open each and every file
      in a project just to be shure to have everything up to date (the
      user could still use `touch' or write a publishing function that
      does so). This is OK. Org-mode cannot _think_ for people,
      publishing a complex WEB project.

 [2]  I never open my org-notes using the real path. I have link 'notes'
      in my home directory pointing to ~/emacs/org/notes/.

 [3]  Org-mode can't guess - there is no `right' sequence.


-- 
Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449 Hannover

Tel.:  +49 (0)511 - 36 58 472
Fax:   +49 (0)1805 - 233633 - 11044
mobil: +49 (0)173 - 83 93 417
Email: s.rose emma-stil de, sebastian_rose gmx de
Http:  www.emma-stil.de

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Re: Release 6.13
  2008-11-25  8:32         ` Sebastian Rose
@ 2008-11-25  9:55           ` Carsten Dominik
  0 siblings, 0 replies; 11+ messages in thread
From: Carsten Dominik @ 2008-11-25  9:55 UTC (permalink / raw)
  To: Sebastian Rose; +Cc: emacs-orgmode Org-Mode


On Nov 25, 2008, at 9:32 AM, Sebastian Rose wrote:

> Hi Carsten,
>
>
> Carsten Dominik <dominik@uva.nl> writes:
>> Hi Sebastian,
>>
>> it seems to me thatt his patch depends on the projects in
>> org-publish-projects-alist to be defined in a certain order,
>> with the components first, and the big "parent" projects later.
>> So maybe you need to iterate the dolist loop until it stabilizes.
>
>> Also, I guess a "component" could be part of several "parents"?
>> Hmm, maybe not a likely setup.  OK, les not worry about this issue.
>
> org-publish-get-project-from-filename always returned the first  
> matching
> project. It still does so, but if one or more composite projects are
> found, of which the files project is a component, the last composite  
> is
> returned instead. In that, it still does what it always did.
>
> Yes, this depends on a certain kind of setup. But it's the setup from
> the example in the docs, so I feel people will most likely use
> that. Since one has to provide the `:publishing-function', the only  
> way to
> publish static content (e.g. images) AND dynamic content is to  
> provide a
> composite project.
>
>
> The issue came up with org-exp-blocks.el [1]. ditaa blocks contain  
> text,
> that is changed, just to update an image. I never ran into this,  
> simply
> because I never used `C-c C-e P' [2].
>
>
> The publishing of a composite project depends on the sequence of it's
> `:components' anyway [3].
>
> Maybe this should be mentioned in the docs at the end of section  
> 13.2.2?
>
> => --->8----------------------------->8----------------------------- 
> >8---
> 'The `:components' in "website" are guaranteed to be published in the
> sequence provided.'
> <=  
> ---8<-----------------------------8<-----------------------------8<---


I think it fits better at the end of 13.1.1, where it is located now.

Thanks.

- Carsten

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Re: Release 6.13
  2008-11-25  1:48     ` Sebastian Rose
  2008-11-25  4:36       ` Carsten Dominik
@ 2008-11-25  9:56       ` Carsten Dominik
  2008-11-25 11:58         ` Bernt Hansen
  1 sibling, 1 reply; 11+ messages in thread
From: Carsten Dominik @ 2008-11-25  9:56 UTC (permalink / raw)
  To: Sebastian Rose; +Cc: emacs-orgmode Org-Mode

Applied, thanks.

- Carsten

On Nov 25, 2008, at 2:48 AM, Sebastian Rose wrote:

> Arrgh....
>
> Sorry - there was an unnecessary line.
>
>
> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
> index eafa8fa..3ec48c4 100644
> --- a/lisp/org-publish.el
> +++ b/lisp/org-publish.el
> @@ -470,7 +470,11 @@ matching filenames."
> (defun org-publish-get-project-from-filename (filename)
>   "Return the project FILENAME belongs."
>   (let* ((project-name (cdr (assoc (expand-file-name filename)
>                                    org-publish-files-alist))))
> +    (dolist (prj org-publish-project-alist)
> +      (if (member project-name (plist-get (cdr prj) :components))
> +          (setq project-name (car prj))))
>     (assoc project-name org-publish-project-alist)))
>
> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>
>
>
> Regards,
>
>  Sebastian
>
>
> Sebastian Rose <sebastian_rose@gmx.de> writes:
>> OK, here is the patch. This ensures, that the whole project is  
>> published
>> for
>>
>> C-c C-e P
>>
>> Hence ditaa blocks can be exported together with a changed Org-file
>> again.
>>
>>
>>
>> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
>> index eafa8fa..3ec48c4 100644
>> --- a/lisp/org-publish.el
>> +++ b/lisp/org-publish.el
>> @@ -470,7 +470,11 @@ matching filenames."
>> (defun org-publish-get-project-from-filename (filename)
>>   "Return the project FILENAME belongs."
>>   (let* ((project-name (cdr (assoc (expand-file-name filename)
>> -                                  org-publish-files-alist))))
>> +                                  org-publish-files-alist)))
>> +        (parent-project nil))
>> +    (dolist (prj org-publish-project-alist)
>> +      (if (member project-name (plist-get (cdr prj) :components))
>> +          (setq project-name (car prj))))
>>     (assoc project-name org-publish-project-alist)))
>>
>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>
>>
>>
>> Regards,
>>
>>
>>  Sebastian
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Bernt Hansen <bernt@norang.ca> writes:
>>> Carsten Dominik <dominik@science.uva.nl> writes:
>>>
>>>> New contributed file /org-exp-blocks.el/
>>>> ----------------------------------------
>>>>
>>>>    This new file implements special export behavior of
>>>>    user-defined blocks.  The currently supported blocks are
>>>>
>>>>    - comment :: Comment blocks with author-specific markup
>>>>    - ditaa ::  conversion of ASCII art into pretty png files
>>>>         using Stathis  Sideris' /ditaa.jar/ program
>>>>    - dot :: creation of graphs in the /dot/ language
>>>>    - R :: Sweave type exporting using the R program
>>>>
>>>>    For more details and examples, see the file commentary in
>>>>    /org-exp-blocks.el/.
>>>>
>>>>    Kudos to Eric Schulte for this new functionality, after
>>>>    /org-plot.el/ already his second major contribution.  Thanks
>>>>    to Stathis for this excellent program, and for allowing us to
>>>>    bundle it with Org-mode.
>>>
>>> Thanks for this!  I really like that C-c ' now makes editing the  
>>> ditaa
>>> images easy.
>>>
>>> Now for my questions related to improving my work-flow for  
>>> generating
>>> documents with ditaa images.
>>>
>>> Q1: Can org-publish-current-project somehow automatically pick up  
>>> ditaa
>>>    generated images?
>>>
>>>    I have a play org file http://doc.norang.ca/org-mode.org which
>>>    generates the page at http://doc.norang.ca/org-mode.html.
>>>
>>>    I usually edit the source file and then
>>>       M-x org-publish-current-project
>>>    to publish my changes.
>>>
>>>    This was working great... until ditaa came along :).
>>>
>>>    Now exporting my .org files creates new ditaa generated images  
>>> (.png
>>>    files) which don't get exported with the document because they  
>>> are
>>>    part of a different project.  After org-publish-current-project I
>>>    have to remember to also org-publish doc-png to get the ditaa
>>>    generated images published.
>>>
>>>    Publishing the parent project 'doc' instead
>>>
>>>      doc
>>>         doc-org (org -> HTML export -> publishing target)
>>>         doc-png (copy .png          -> publishing target)
>>>
>>>    works fine so maybe I just need fix my workflow so my publish  
>>> code
>>>    is smart enough to find the appropriate parent project and  
>>> publish
>>>    that instead.
>>>
>>> Q2: Can org-publish handle a source file in more than one project?
>>>
>>>    Sometimes I would like to publish the generated page (org- 
>>> mode.html)
>>>    as well as the source file that creates it (org-mode.org) as in  
>>> Q1
>>>    above.  I don't think I can have a doc-org project that generates
>>>    HTML and a doc-src project that just copies the .org files  
>>> verbatim
>>>    to the target directory since after publishing one of the two
>>>    projects the file is 'unchanged' and skipped for publishing the
>>>    second one.  Is there a way to accomplish this?
>>>
>>>    For now I'm manually touching the org file and manually  
>>> publishing
>>>    the doc-src project to make it work.
>>>
>>>
>>> ditaa images look great on HTML exports.  I'm having some difficulty
>>> including them in other formats (PDF for instance - they end up  
>>> being
>>> tiny.)  Someday I'll find a good solution for that.
>>> http://doc.norang.ca/org-mode.pdf is an example.
>>>
>>> Thanks for org-mode!
>>>
>>> Regards,
>>> Bernt
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>>
>
> -- 
> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449  
> Hannover
>
> Tel.:  +49 (0)511 - 36 58 472
> Fax:   +49 (0)1805 - 233633 - 11044
> mobil: +49 (0)173 - 83 93 417
> Email: s.rose emma-stil de, sebastian_rose gmx de
> Http:  www.emma-stil.de
>
>
> _______________________________________________
> 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

^ permalink raw reply	[flat|nested] 11+ messages in thread

* Re: Release 6.13
  2008-11-25  9:56       ` Carsten Dominik
@ 2008-11-25 11:58         ` Bernt Hansen
  0 siblings, 0 replies; 11+ messages in thread
From: Bernt Hansen @ 2008-11-25 11:58 UTC (permalink / raw)
  To: Carsten Dominik; +Cc: emacs-orgmode Org-Mode

Thanks to both of you :)

-Bernt


Carsten Dominik <dominik@science.uva.nl> writes:

> Applied, thanks.
>
> - Carsten
>
> On Nov 25, 2008, at 2:48 AM, Sebastian Rose wrote:
>
>> Arrgh....
>>
>> Sorry - there was an unnecessary line.
>>
>>
>> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
>> index eafa8fa..3ec48c4 100644
>> --- a/lisp/org-publish.el
>> +++ b/lisp/org-publish.el
>> @@ -470,7 +470,11 @@ matching filenames."
>> (defun org-publish-get-project-from-filename (filename)
>>   "Return the project FILENAME belongs."
>>   (let* ((project-name (cdr (assoc (expand-file-name filename)
>>                                    org-publish-files-alist))))
>> +    (dolist (prj org-publish-project-alist)
>> +      (if (member project-name (plist-get (cdr prj) :components))
>> +          (setq project-name (car prj))))
>>     (assoc project-name org-publish-project-alist)))
>>
>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>
>>
>>
>> Regards,
>>
>>  Sebastian
>>
>>
>> Sebastian Rose <sebastian_rose@gmx.de> writes:
>>> OK, here is the patch. This ensures, that the whole project is
>>> published
>>> for
>>>
>>> C-c C-e P
>>>
>>> Hence ditaa blocks can be exported together with a changed Org-file
>>> again.
>>>
>>>
>>>
>>> diff --git a/lisp/org-publish.el b/lisp/org-publish.el
>>> index eafa8fa..3ec48c4 100644
>>> --- a/lisp/org-publish.el
>>> +++ b/lisp/org-publish.el
>>> @@ -470,7 +470,11 @@ matching filenames."
>>> (defun org-publish-get-project-from-filename (filename)
>>>   "Return the project FILENAME belongs."
>>>   (let* ((project-name (cdr (assoc (expand-file-name filename)
>>> -                                  org-publish-files-alist))))
>>> +                                  org-publish-files-alist)))
>>> +        (parent-project nil))
>>> +    (dolist (prj org-publish-project-alist)
>>> +      (if (member project-name (plist-get (cdr prj) :components))
>>> +          (setq project-name (car prj))))
>>>     (assoc project-name org-publish-project-alist)))
>>>
>>> ;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
>>>
>>>
>>>
>>> Regards,
>>>
>>>
>>>  Sebastian
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Bernt Hansen <bernt@norang.ca> writes:
>>>> Carsten Dominik <dominik@science.uva.nl> writes:
>>>>
>>>>> New contributed file /org-exp-blocks.el/
>>>>> ----------------------------------------
>>>>>
>>>>>    This new file implements special export behavior of
>>>>>    user-defined blocks.  The currently supported blocks are
>>>>>
>>>>>    - comment :: Comment blocks with author-specific markup
>>>>>    - ditaa ::  conversion of ASCII art into pretty png files
>>>>>         using Stathis  Sideris' /ditaa.jar/ program
>>>>>    - dot :: creation of graphs in the /dot/ language
>>>>>    - R :: Sweave type exporting using the R program
>>>>>
>>>>>    For more details and examples, see the file commentary in
>>>>>    /org-exp-blocks.el/.
>>>>>
>>>>>    Kudos to Eric Schulte for this new functionality, after
>>>>>    /org-plot.el/ already his second major contribution.  Thanks
>>>>>    to Stathis for this excellent program, and for allowing us to
>>>>>    bundle it with Org-mode.
>>>>
>>>> Thanks for this!  I really like that C-c ' now makes editing the
>>>> ditaa
>>>> images easy.
>>>>
>>>> Now for my questions related to improving my work-flow for
>>>> generating
>>>> documents with ditaa images.
>>>>
>>>> Q1: Can org-publish-current-project somehow automatically pick up
>>>> ditaa
>>>>    generated images?
>>>>
>>>>    I have a play org file http://doc.norang.ca/org-mode.org which
>>>>    generates the page at http://doc.norang.ca/org-mode.html.
>>>>
>>>>    I usually edit the source file and then
>>>>       M-x org-publish-current-project
>>>>    to publish my changes.
>>>>
>>>>    This was working great... until ditaa came along :).
>>>>
>>>>    Now exporting my .org files creates new ditaa generated images
>>>> (.png
>>>>    files) which don't get exported with the document because they
>>>> are
>>>>    part of a different project.  After org-publish-current-project I
>>>>    have to remember to also org-publish doc-png to get the ditaa
>>>>    generated images published.
>>>>
>>>>    Publishing the parent project 'doc' instead
>>>>
>>>>      doc
>>>>         doc-org (org -> HTML export -> publishing target)
>>>>         doc-png (copy .png          -> publishing target)
>>>>
>>>>    works fine so maybe I just need fix my workflow so my publish
>>>> code
>>>>    is smart enough to find the appropriate parent project and
>>>> publish
>>>>    that instead.
>>>>
>>>> Q2: Can org-publish handle a source file in more than one project?
>>>>
>>>>    Sometimes I would like to publish the generated page (org- 
>>>> mode.html)
>>>>    as well as the source file that creates it (org-mode.org) as in
>>>> Q1
>>>>    above.  I don't think I can have a doc-org project that generates
>>>>    HTML and a doc-src project that just copies the .org files
>>>> verbatim
>>>>    to the target directory since after publishing one of the two
>>>>    projects the file is 'unchanged' and skipped for publishing the
>>>>    second one.  Is there a way to accomplish this?
>>>>
>>>>    For now I'm manually touching the org file and manually
>>>> publishing
>>>>    the doc-src project to make it work.
>>>>
>>>>
>>>> ditaa images look great on HTML exports.  I'm having some difficulty
>>>> including them in other formats (PDF for instance - they end up
>>>> being
>>>> tiny.)  Someday I'll find a good solution for that.
>>>> http://doc.norang.ca/org-mode.pdf is an example.
>>>>
>>>> Thanks for org-mode!
>>>>
>>>> Regards,
>>>> Bernt
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>
>> -- 
>> Sebastian Rose, EMMA STIL - mediendesign, Niemeyerstr.6, 30449
>> Hannover
>>
>> Tel.:  +49 (0)511 - 36 58 472
>> Fax:   +49 (0)1805 - 233633 - 11044
>> mobil: +49 (0)173 - 83 93 417
>> Email: s.rose emma-stil de, sebastian_rose gmx de
>> Http:  www.emma-stil.de
>>
>>
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> 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

^ permalink raw reply	[flat|nested] 11+ messages in thread

end of thread, other threads:[~2008-11-25 11:59 UTC | newest]

Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-11-23  7:20 Release 6.13 Carsten Dominik
2008-11-23 18:24 ` Bernt Hansen
2008-11-24  2:12   ` Sebastian Rose
2008-11-24 21:23     ` Bernt Hansen
2008-11-25  1:31   ` Sebastian Rose
2008-11-25  1:48     ` Sebastian Rose
2008-11-25  4:36       ` Carsten Dominik
2008-11-25  8:32         ` Sebastian Rose
2008-11-25  9:55           ` Carsten Dominik
2008-11-25  9:56       ` Carsten Dominik
2008-11-25 11:58         ` Bernt Hansen

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).