how to export an org file, to 2 different locations (in to different formats)

how to export an org file, to 2 different locations (in to different formats)

[Uwe Brauer]

Hi

Currently I use 
#+EXPORT_FILE_NAME: /home/oub/Desktop/some-stuff.html

To export my org file in html format to that location.

But I would also like to export it as a latex file to a different
location, without modifying the above line, or to be more precise to add
a different location, like

    1. if export to latex use that folder

    2. If export to html use this folder

Anybody know about such a functionality?

Thanks and regards

Uwe Brauer 




-- 
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military. 
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine. 

Re: how to export an org file, to 2 different locations (in to different formats)

[Juan Manuel Macías]

Hi Uwe,

Uwe Brauer writes:

> Hi
>
> Currently I use 
> #+EXPORT_FILE_NAME: /home/oub/Desktop/some-stuff.html
>
> To export my org file in html format to that location.
>
> But I would also like to export it as a latex file to a different
> location, without modifying the above line, or to be more precise to add
> a different location, like
>
>     1. if export to latex use that folder
>
>     2. If export to html use this folder
>
> Anybody know about such a functionality?
>
> Thanks and regards
>
> Uwe Brauer 

One (pedestrian) way to achieve it, with this function:

(defun my-org/export-to-path (backend export-path extension)
  (org-element-map (org-element-parse-buffer) 'keyword
    (lambda (k)
      (when (string= (org-element-property :key k) "EXPORT_FILE_NAME")
	(let ((value (org-element-property :value k)))
	  (org-export-to-file backend
	      (format
	       "%s%s.%s"
	       export-path
	       value extension)))))))

And then you could evaluate it inside a block in your document, with the
chosen arguments. For example:

#+EXPORT_FILE_NAME: myfile

#+begin_src emacs-lisp :exports none :eval never-export :results silent
  (my-org/export-to-path 'html "~/Desktop/" "html")
#+end_src

Best regards,

Juan Manuel 

Re: how to export an org file, to 2 different locations (in to different formats)

[Juan Manuel Macías]

Juan Manuel Macías writes:

> One (pedestrian) way to achieve it, with this function:

I think it can be done better this way, defining an advice around
'org-export-output-file-name'.

In your org file you should add these two local variables:

# my-latex-export-path: "~/path/to/myfile.tex"
# my-html-export-path "~/path/to/myfile.html"

And this is the define-advice code. It should export to one or another path/file every
time you export your document to LaTeX or html. I haven't tried it much:

(define-advice org-export-output-file-name (:around (old-func extension &rest args))
  (setq old-func (lambda (extension &optional subtreep pub-dir)
		   (let* ((visited-file (buffer-file-name (buffer-base-buffer)))
			  (base-name
			   (concat
			    (file-name-sans-extension
			     (or
			      ;; Check EXPORT_FILE_NAME subtree property.
			      (and subtreep (org-entry-get nil "EXPORT_FILE_NAME" 'selective))
			      ;; Check #+EXPORT_FILE_NAME keyword.
			      (org-with-point-at (point-min)
				(catch :found
				  (let ((case-fold-search t))
				    (while (re-search-forward
					    "^[ \t]*#\\+EXPORT_FILE_NAME:[ \t]+\\S-" nil t)
				      (let ((element (org-element-at-point)))
					(when (eq 'keyword (org-element-type element))
					  (throw :found
						 (org-element-property :value element))))))))
			      ;; Extract from buffer's associated file, if any.
			      (and visited-file
				   (file-name-nondirectory
				    ;; For a .gpg visited file, remove the .gpg extension:
				    (replace-regexp-in-string "\\.gpg\\'" "" visited-file)))
			      ;; Can't determine file name on our own: ask user.
			      (read-file-name
			       "Output file: " pub-dir nil nil nil
			       (lambda (n) (string= extension (file-name-extension n t))))))
			    extension))
			  (output-file
			   ;; Build file name.  Enforce EXTENSION over whatever user
			   ;; may have come up with.  PUB-DIR, if defined, always has
			   ;; precedence over any provided path.
			   (cond
			    (pub-dir (concat (file-name-as-directory pub-dir)
					     (file-name-nondirectory base-name)))
			    ((file-name-absolute-p base-name) base-name)
			    (t base-name))))
		     ;; If writing to OUTPUT-FILE would overwrite original file, append
		     ;; EXTENSION another time to final name.
		     (if (and visited-file (file-equal-p visited-file output-file))
			 (concat output-file extension)
		       output-file))))
  (if (and my-latex-export-path my-html-export-path)
      (cond ((equal extension ".tex")
	     my-latex-export-path)
	    ((equal extension ".html")
	     my-html-export-path))
    (apply old-func args)))

Best regards,

Juan Manuel 

Re: how to export an org file, to 2 different locations (in to different formats)

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]

>>> "JMM" == Juan Manuel Macías <maciaschain@posteo.net> writes:

> Juan Manuel Macías writes:
>> One (pedestrian) way to achieve it, with this function:

> I think it can be done better this way, defining an advice around
> 'org-export-output-file-name'.

> In your org file you should add these two local variables:

> # my-latex-export-path: "~/path/to/myfile.tex"
> # my-html-export-path "~/path/to/myfile.html"

> And this is the define-advice code. It should export to one or another path/file every
> time you export your document to LaTeX or html. I haven't tried it much:


Thanks, that looks even more convenient!
I tried to test it with 

#+begin_example
# my-latex-export-path: "./myfile2.tex"
# my-html-export-path "~/Desktop/myfile2.html"

,#+begin_src emacs-lisp :exports none :eval never-export :results silent
  (my-org/export-to-path 'html "~/Desktop/" "html")
,#+end_src


,#+begin_src emacs-lisp :exports none :eval never-export :results silent
  (my-org/export-to-path 'latex "./" "tex")
,#+end_src

,* Excuses


Jim: Which was? Sir Humphrey: 

#+end_example

When I run it I obtain 
if: Symbol’s value as variable is void: my-latex-export-path

Another point is if I decide to export it to ods, I need to modify that
advice, but I agree the new function is more convenient.

Uwe 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

Re: how to export an org file, to 2 different locations (in to different formats)

[Juan Manuel Macías]

Uwe Brauer writes:

> When I run it I obtain 
> if: Symbol’s value as variable is void: my-latex-export-path
>
> Another point is if I decide to export it to ods, I need to modify that
> advice, but I agree the new function is more convenient.

You must add the variables to the document as local variables, at the
end of the document, like this:

# Local Variables:
# my-latex-export-path: "~/path/myfile.tex"
# my-html-export-path: "~/path/myfile.html"
# End:

But (it's important, I didn't tell you, sorry) before you must globally
define the variables with nil value, so that you don't get an error in
other documents:

(setq my-latex-export-path nil
      my-html-export-path nil)

With this 'define-advice' procedure you don't need the other code I gave
you. You can export in the usual way, using the dispatcher. The only
difference is that in any document where these variables exist, the
resulting file will be saved in the directory/name specified in the
variables, depending on whether you export to latex or html.

To add more cases, like odt, simply:

(1) you define a new variable:

  (setq my-latex-export-path nil
	my-html-export-path nil
	my-odt-export-path nil)

and locally:

# Local Variables:
# my-latex-export-path: "~/path/myfile.tex"
# my-html-export-path: "~/path/myfile.html"
# my-odt-export-path: "~/path/myfile.html"
# End:

(2) And you add a new condition at the end of the define-advice:

[...]
(if (and my-latex-export-path
	     my-html-export-path
	     my-odt-export-path)
	(cond ((equal extension ".tex")
	       my-latex-export-path)
	      ((equal extension ".html")
	       my-html-export-path)
	      ((equal extension ".odt")
	       my-odt-export-path))
      (apply old-func args)))

It means that: if those variables exist, it returns as a result the
path/name that you have specified for each case. Otherwise, the
org-export-output-file-name function is executed normally.

Best regards,

Juan Manuel 

Re: how to export an org file, to 2 different locations (in to different formats)

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 1275 bytes --]

>>> "JMM" == Juan Manuel Macías <maciaschain@posteo.net> writes:

> Uwe Brauer writes:
>> When I run it I obtain 
>> if: Symbol’s value as variable is void: my-latex-export-path
>> 
>> Another point is if I decide to export it to ods, I need to modify that
>> advice, but I agree the new function is more convenient.

> You must add the variables to the document as local variables, at the
> end of the document, like this:

> # Local Variables:
> # my-latex-export-path: "~/path/myfile.tex"
> # my-html-export-path: "~/path/myfile.html"
> # End:

Aha, I see, thanks

Just one observation, while this is more convenient your other method has the benefit that it allows me to export to 2 files in different locations having the *same* extension like


> # my-latex-export-path: "~/path/myfile1.tex"
> # my-latex-export-path: "~/path/myfile2.tex"

Which seems more complicated in the other approach. 

I have also to confess, that I usually am I bit hesitant to use defadvice since it changes the vanilla function, and might cause problems, but maybe this is just me.

In any case thanks for both solution, that was very generous and helpful.

Developers: why to include some of this code in a addon file, if Juan agrees of course!

Uwe 


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

Re: how to export an org file, to 2 different locations (in to different formats)

[Juan Manuel Macías]

Uwe Brauer writes:

> I have also to confess, that I usually am I bit hesitant to use
> defadvice since it changes the vanilla function, and might cause
> problems, but maybe this is just me.

You are absolutely right, and I confess that I would have the same
precautions :-). Also, the defadvice code is very poorly tested, and is
likely to cause some collateral kills... If you need it for specific use
cases, you can try evaluating it only for specific sessions, instead of
leaving it in your init file. Or make a mode that turns it on or off.

Best regards,

Juan Manuel 

Re: how to export an org file, to 2 different locations (in to different formats)

[Ihor Radchenko]

Uwe Brauer <oub@mat.ucm.es> writes:

> In any case thanks for both solution, that was very generous and helpful.
>
> Developers: why to include some of this code in a addon file, if Juan agrees of course!

A more canonical solution would be writing
org-export-filter-options-functions that set :output-file export option
directly.

Best,
Ihor

Re: how to export an org file, to 2 different locations (in to different formats)

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]


> Hi Uwe,
> Uwe Brauer writes:


> One (pedestrian) way to achieve it, with this function:

> (defun my-org/export-to-path (backend export-path extension)
>   (org-element-map (org-element-parse-buffer) 'keyword
>     (lambda (k)
>       (when (string= (org-element-property :key k) "EXPORT_FILE_NAME")
> 	(let ((value (org-element-property :value k)))
> 	  (org-export-to-file backend
> 	      (format
> 	       "%s%s.%s"
> 	       export-path
> 	       value extension)))))))

> And then you could evaluate it inside a block in your document, with the
> chosen arguments. For example:

> #+EXPORT_FILE_NAME: myfile

> #+begin_src emacs-lisp :exports none :eval never-export :results silent
>   (my-org/export-to-path 'html "~/Desktop/" "html")
> #+end_src

Very nice I run a test with 

#+begin_src emacs-lisp :exports none :eval never-export :results silent
  (my-org/export-to-path 'html "~/Desktop/" "html")
#+end_src



#+begin_src emacs-lisp :exports none :eval never-export :results silent
  (my-org/export-to-path 'latex "./" "tex")
#+end_src

And it works nicely, thanks a lot, simplifies my workflow quite a bit.


Uwe 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

[ODT?] (was: how to export an org file, to 2 different locations (in to different formats))

[Uwe Brauer]

[-- Attachment #1: Type: text/plain, Size: 799 bytes --]


> Hi Uwe,
> Uwe Brauer writes:


> One (pedestrian) way to achieve it, with this function:
I tried the following 

#+begin_example
#+EXPORT_FILE_NAME: myfile-office


#+begin_src emacs-lisp :exports none :eval never-export :results silent
  (my-org/export-to-path 'html "~/Desktop/" "html")
#+end_src


#+begin_src emacs-lisp :exports none :eval never-export :results silent
  (my-org/export-to-path 'latex "./" "tex")
#+end_src


#+begin_src emacs-lisp :exports none :eval never-export :results silent
  (my-org/export-to-path 'odt "./" "odt")
#+end_src

* Excuses


Jim: Which was? Sir Humphrey: 

#+end_example

But then the export to odt, did not work as expected the file was too small, but maybe odt is not the right setting for the export to LO/OO.

Uwe 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

Re: how to export an org file, to 2 different locations (in to different formats)

[Nick Dokos]

Uwe Brauer <oub@mat.ucm.es> writes:

> Hi
>
> Currently I use 
> #+EXPORT_FILE_NAME: /home/oub/Desktop/some-stuff.html
>
> To export my org file in html format to that location.
>
> But I would also like to export it as a latex file to a different
> location, without modifying the above line, or to be more precise to add
> a different location, like
>
>     1. if export to latex use that folder
>
>     2. If export to html use this folder
>
> Anybody know about such a functionality?
>

org-publish?

You should be able to write a simple publishing config file to do that.

> Thanks and regards
>
> Uwe Brauer 

-- 
Nick

"There are only two hard problems in computer science: cache
invalidation, naming things, and off-by-one errors." -Martin Fowler