export_file_name problem with new exporter

export_file_name problem with new exporter

[Alan Schmitt]

Hello,

I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
when I export it (either to beamer or to latex), it's using the name of
the file instead of the given file name.

Am I doing something wrong here?

Thanks,

Alan

Re: export_file_name problem with new exporter

[Suvayu Ali]

On Fri, Dec 07, 2012 at 11:27:40AM +0100, Alan Schmitt wrote:
> Hello,
> 
> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
> when I export it (either to beamer or to latex), it's using the name of
> the file instead of the given file name.
> 
> Am I doing something wrong here?
> 

As far as I am aware, that works for subtree export only.

-- 
Suvayu

Open source is the future. It sets us free.

Re: export_file_name problem with new exporter

[Alan Schmitt]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> On Fri, Dec 07, 2012 at 11:27:40AM +0100, Alan Schmitt wrote:
>> Hello,
>> 
>> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
>> when I export it (either to beamer or to latex), it's using the name of
>> the file instead of the given file name.
>> 
>> Am I doing something wrong here?
>> 
>
> As far as I am aware, that works for subtree export only.

Ah, this is problematic. I need to change the file name for two reasons:
- the org file name has spaces in it, and latexmk fails when processing
it
- processing the file creates a bunch of files that clobber my org
directory, so I want the created files to be out of the way

If someone has suggestions on how to deal with these issues, I'd gladly
try them.

Thanks,

Alan

Re: export_file_name problem with new exporter

[Suvayu Ali]

On Fri, Dec 07, 2012 at 01:38:50PM +0100, Alan Schmitt wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > On Fri, Dec 07, 2012 at 11:27:40AM +0100, Alan Schmitt wrote:
> >> Hello,
> >> 
> >> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
> >> when I export it (either to beamer or to latex), it's using the name of
> >> the file instead of the given file name.
> >> 
> >> Am I doing something wrong here?
> >> 
> >
> > As far as I am aware, that works for subtree export only.
> 
> Ah, this is problematic. I need to change the file name for two reasons:
> - the org file name has spaces in it, and latexmk fails when processing
> it
> - processing the file creates a bunch of files that clobber my org
> directory, so I want the created files to be out of the way
> 
> If someone has suggestions on how to deal with these issues, I'd gladly
> try them.
> 

You could try the publishing facilities in Org.

(info "(org)Publishing")

-- 
Suvayu

Open source is the future. It sets us free.

Re: export_file_name problem with new exporter

[Alan Schmitt]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> You could try the publishing facilities in Org.
>
> (info "(org)Publishing")

I did not know about that, it's a very nice suggestion. I have one
question that I did not see addressed in the documentation, though: is
it possible to use it with the new exporter?

Thanks a lot,

Alan

Re: export_file_name problem with new exporter

[Suvayu Ali]

On Fri, Dec 07, 2012 at 03:02:32PM +0100, Alan Schmitt wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > You could try the publishing facilities in Org.
> >
> > (info "(org)Publishing")
> 
> I did not know about that, it's a very nice suggestion. I have one
> question that I did not see addressed in the documentation, though: is
> it possible to use it with the new exporter?
> 

Since the new exporter is not documented yet, information is absent from
the info manual.  You can find relevant docs in the source files.  I am
slowly working towards a tutorial type docs for org-e-beamer.  When it
is in shape, I'll push to Worg.

That said, publishing is fully supported by the new exporter, just
change the publishing function names to the functions provided by the
new exporter.

Here is an improperly tested example from one of my tests:

(setq org-e-publish-project-alist
      '(("thesis" :components ("thesis-tex" "thesis-html"))
	("thesis-tex" :base-directory "/path/PhD-thesis"
	 :publishing-directory "/path/PhD-thesis/latex"
	 :publishing-function org-e-publish-org-to-latex
	 )))

Hope this helps.

-- 
Suvayu

Open source is the future. It sets us free.

Re: export_file_name problem with new exporter

[Alan Schmitt]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> Since the new exporter is not documented yet, information is absent from
> the info manual.  You can find relevant docs in the source files.  I am
> slowly working towards a tutorial type docs for org-e-beamer.  When it
> is in shape, I'll push to Worg.

Great.

> That said, publishing is fully supported by the new exporter, just
> change the publishing function names to the functions provided by the
> new exporter.
>
> Here is an improperly tested example from one of my tests:
>
> (setq org-e-publish-project-alist
>       '(("thesis" :components ("thesis-tex" "thesis-html"))
> 	("thesis-tex" :base-directory "/path/PhD-thesis"
> 	 :publishing-directory "/path/PhD-thesis/latex"
> 	 :publishing-function org-e-publish-org-to-latex
> 	 )))
>
> Hope this helps.

It does, but for some reason I can't make it work. It seems that it has
issues getting the base file. Here is my setup:

(setq org-e-publish-project-alist
      '(("jsseccloud"
         :base-directory "~/Documents/Org"
         :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org"
         :publishing-directory "~/tmp"
         :publishing-function org-e-beamer-publish-to-latex
         )))

and with this I get an error:

Debugger entered--Lisp error: (wrong-type-argument sequencep 50)
  #[(f) "\304\b	P!\305\n\v\"\203\0\v\202\0\n\vB\211)\207" [base-dir f x org-e-publish-temp-files expand-file-name memql] 3](50)
  mapc(#[(f) "\304\b	P!\305\n\v\"\203\0\v\202\0\n\vB\211)\207" [base-dir f x org-e-publish-temp-files expand-file-name memql] 3] "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org")
  org-e-publish-get-base-files(("jsseccloud" :base-directory "~/Documents/Org" :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org" :publishing-directory "~/tmp" :publishing-function org-e-beamer-publish-to-latex) nil)
  #[(project) "\306\b@!\210\bA\307	\310\"\307	\311\"\307	\312\"\206\0\313\307	\314\"\206#\315\307	\316\"\206-\x0e\x1f \307	\317\"\2068\x0e!\"\307	\320\"\x15\307	\321\"\x1d\322\b\n\"#\323$\x15\203X\324\325!\210\v\203a
\b\f\"\210#\323$\211%\203\201\x0e%@$\326$\b\327#\210%A\211%\204l*\307	\330\"\203\235\331\b\307	\332\"\"\210\326\333\334\307	\332\"\"\b\327#\210\x1d\203\246\324\335!\210\336 .\v\207" [project project-plist exclude-regexp sitemap-p sitemap-filename sitemap-function org-e-publish-initialize-cache plist-get :exclude :auto-sitemap :sitemap-filename "sitemap.org" :sitemap-function org-e-publish-org-sitemap :sitemap-date-format :sitemap-file-entry-format :preparation-function :completion-function org-e-publish-get-base-files nil run-hooks preparation-function org-e-publish-file t :makeindex org-e-publish-index-generate-theindex :base-directory expand-file-name "theindex.org" completion-function org-e-publish-write-cache-file org-e-publish-sitemap-date-format org-sitemap-date-format org-e-publish-sitemap-file-entry-format org-sitemap-file-entry-format files file --cl-dolist-temp--] 7](("jsseccloud" :base-directory "~/Documents/Org" :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org" :publishing-directory "~/tmp" :publishing-function org-e-beamer-publish-to-latex))
  mapc(#[(project) "\306\b@!\210\bA\307	\310\"\307	\311\"\307	\312\"\206\0\313\307	\314\"\206#\315\307	\316\"\206-\x0e\x1f \307	\317\"\2068\x0e!\"\307	\320\"\x15\307	\321\"\x1d\322\b\n\"#\323$\x15\203X\324\325!\210\v\203a
\b\f\"\210#\323$\211%\203\201\x0e%@$\326$\b\327#\210%A\211%\204l*\307	\330\"\203\235\331\b\307	\332\"\"\210\326\333\334\307	\332\"\"\b\327#\210\x1d\203\246\324\335!\210\336 .\v\207" [project project-plist exclude-regexp sitemap-p sitemap-filename sitemap-function org-e-publish-initialize-cache plist-get :exclude :auto-sitemap :sitemap-filename "sitemap.org" :sitemap-function org-e-publish-org-sitemap :sitemap-date-format :sitemap-file-entry-format :preparation-function :completion-function org-e-publish-get-base-files nil run-hooks preparation-function org-e-publish-file t :makeindex org-e-publish-index-generate-theindex :base-directory expand-file-name "theindex.org" completion-function org-e-publish-write-cache-file org-e-publish-sitemap-date-format org-sitemap-date-format org-e-publish-sitemap-file-entry-format org-sitemap-file-entry-format files file --cl-dolist-temp--] 7] (("jsseccloud" :base-directory "~/Documents/Org" :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org" :publishing-directory "~/tmp" :publishing-function org-e-beamer-publish-to-latex)))
  org-e-publish-projects((("jsseccloud" :base-directory "~/Documents/Org" :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org" :publishing-directory "~/tmp" :publishing-function org-e-beamer-publish-to-latex)))
  org-e-publish(("jsseccloud" :base-directory "~/Documents/Org" :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org" :publishing-directory "~/tmp" :publishing-function org-e-beamer-publish-to-latex) nil)
  call-interactively(org-e-publish record nil)
  command-execute(org-e-publish record)
  smex-read-and-run(("set-variable" "org-e-publish" "info" "gnus" "visual-line-mode" "org-export-dispatch" "turn-on-gnus-dired-mode" "erc" "gnus-group-mail" "auto-fill-mode" "eshell" "bbdb-save" "package-list-packages" "flyspell-mode" "calc" "dired" "compile" "grep" "flyspell-buffer" "load-theme" "bbdb-merge-records" "org-store-link" "ispell-change-dictionary" "ansi-term" "magit-status" "customize-face" "list-colors-display" "lld-notmuch-goto-message-in-gnus" "multi-term" "recover-file" "rename-buffer" "color-theme-solarized-light" "set-buffer-file-coding-system" "help" "svn-status" "list-packages" "customize-group" "eval-expression" "bbdb" "shell" "why-mode" "revert-buffer" "list-faces-display" "org-mode" "customize" "LaTeX-mode" "org-reload" "re-builder" "follow-mode" "org-version" ...))
  smex()
  call-interactively(smex nil nil)

I tried specifying the file with and without the ".org" and it does not
change anything.

Alan

Re: export_file_name problem with new exporter

[Suvayu Ali]

On Fri, Dec 07, 2012 at 05:12:46PM +0100, Alan Schmitt wrote:
> Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> 
> > Since the new exporter is not documented yet, information is absent from
> > the info manual.  You can find relevant docs in the source files.  I am
> > slowly working towards a tutorial type docs for org-e-beamer.  When it
> > is in shape, I'll push to Worg.
> 
> Great.
> 
> > That said, publishing is fully supported by the new exporter, just
> > change the publishing function names to the functions provided by the
> > new exporter.
> >
> > Here is an improperly tested example from one of my tests:
> >
> > (setq org-e-publish-project-alist
> >       '(("thesis" :components ("thesis-tex" "thesis-html"))
> > 	("thesis-tex" :base-directory "/path/PhD-thesis"
> > 	 :publishing-directory "/path/PhD-thesis/latex"
> > 	 :publishing-function org-e-publish-org-to-latex
> > 	 )))
> >
> > Hope this helps.
> 
> It does, but for some reason I can't make it work. It seems that it has
> issues getting the base file. Here is my setup:
> 
> (setq org-e-publish-project-alist
>       '(("jsseccloud"
>          :base-directory "~/Documents/Org"
>          :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org"
>          :publishing-directory "~/tmp"
>          :publishing-function org-e-beamer-publish-to-latex
>          )))
> 
> and with this I get an error:
> 

I believe that is because org-e-beamer does not support publishing yet.
Nicolas can confirm.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: export_file_name problem with new exporter

[Alan Schmitt]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

>> > That said, publishing is fully supported by the new exporter, just
>> > change the publishing function names to the functions provided by the
>> > new exporter.
>> >
>> > Here is an improperly tested example from one of my tests:
>> >
>> > (setq org-e-publish-project-alist
>> >       '(("thesis" :components ("thesis-tex" "thesis-html"))
>> > 	("thesis-tex" :base-directory "/path/PhD-thesis"
>> > 	 :publishing-directory "/path/PhD-thesis/latex"
>> > 	 :publishing-function org-e-publish-org-to-latex
>> > 	 )))
>> >
>> > Hope this helps.
>> 
>> It does, but for some reason I can't make it work. It seems that it has
>> issues getting the base file. Here is my setup:
>> 
>> (setq org-e-publish-project-alist
>>       '(("jsseccloud"
>>          :base-directory "~/Documents/Org"
>>          :include "2012-12-05-Cprs-SecCloud-Formal_JavaScript_Semantics.org"
>>          :publishing-directory "~/tmp"
>>          :publishing-function org-e-beamer-publish-to-latex
>>          )))
>> 
>> and with this I get an error:
>> 
>
> I believe that is because org-e-beamer does not support publishing yet.
> Nicolas can confirm.

Well, replacing "org-e-beamer-publish-to-latex" by
"org-e-latex-publish-to-latex" results in the same error. I looked at
the code, and my problem was that ":include" expects a list, so I'm able
to make this .

I'll try to see if adding beamer support is difficult.

Alan

Re: export_file_name problem with new exporter

[Alan Schmitt]

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

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> Well, replacing "org-e-beamer-publish-to-latex" by
> "org-e-latex-publish-to-latex" results in the same error. I looked at
> the code, and my problem was that ":include" expects a list, so I'm able
> to make this .

I forgot one word: "work".

> I'll try to see if adding beamer support is difficult.

It was trivial to add. Please find a patch attached.

Should I push this commit myself, or let someone else do it?

Alan


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-contrib-lisp-org-e-beamer.el-Publishing.patch --]
[-- Type: text/x-patch, Size: 1885 bytes --]

From ce787823cec892d8cfb8391145ae374adad7dc59 Mon Sep 17 00:00:00 2001
From: Alan Schmitt <alan.schmitt@polytechnique.org>
Date: Sat, 8 Dec 2012 12:09:22 +0100
Subject: [PATCH] * contrib/lisp/org-e-beamer.el (Publishing):   added
 publishing functions org-e-beamer-publish-to-latex and  
 org-e-beamer-publish-to-pdf

TINYCHANGE
---
 contrib/lisp/org-e-beamer.el | 27 +++++++++++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/contrib/lisp/org-e-beamer.el b/contrib/lisp/org-e-beamer.el
index bab655e..9333a7a 100644
--- a/contrib/lisp/org-e-beamer.el
+++ b/contrib/lisp/org-e-beamer.el
@@ -1145,6 +1145,33 @@ aid, but the tag does not have any semantic meaning."
       (insert "#+COLUMNS: " org-e-beamer-column-view-format "\n"))
     (insert "#+PROPERTY: BEAMER_col_ALL " org-e-beamer-column-widths "\n")))
 
+;;;###autoload
+(defun org-e-beamer-publish-to-latex (plist filename pub-dir)
+  "Publish an Org file to a Beamer presentation (LaTeX).
+
+FILENAME is the filename of the Org file to be published.  PLIST
+is the property list for the given project.  PUB-DIR is the
+publishing directory.
+
+Return output file name."
+  (org-e-publish-org-to 'e-beamer filename ".tex" plist pub-dir))
+
+;;;###autoload
+(defun org-e-beamer-publish-to-pdf (plist filename pub-dir)
+  "Publish an Org file to a Beamer presentation (PDF, via LaTeX).
+
+FILENAME is the filename of the Org file to be published.  PLIST
+is the property list for the given project.  PUB-DIR is the
+publishing directory.
+
+Return output file name."
+  ;; Unlike to `org-e-beamer-publish-to-latex', PDF file is generated
+  ;; in working directory and then moved to publishing directory.
+  (org-e-publish-attachment
+   plist
+   (org-e-latex-compile (org-e-publish-org-to 'e-beamer filename ".tex" plist))
+   pub-dir))
+
 
 (provide 'org-e-beamer)
 ;;; org-e-beamer.el ends here
-- 
1.7.12

Re: export_file_name problem with new exporter

[Suvayu Ali]

On Sat, Dec 08, 2012 at 12:13:30PM +0100, Alan Schmitt wrote:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
> 
> > I'll try to see if adding beamer support is difficult.
> 
> It was trivial to add. Please find a patch attached.

Thanks!

> Should I push this commit myself, or let someone else do it?
> 

If you have push access, I guess you can.  But I would wait for someone
to comment on it first.  I'm not familiar with the API, so sorry I can't
comment.

Cheers,

-- 
Suvayu

Open source is the future. It sets us free.

Re: export_file_name problem with new exporter

[Achim Gratz]

Alan Schmitt writes:
> TINYCHANGE

As much as you would wish it wasn't so, your patch exceeds the tiny
change limit (not even counting your previous contributions) and you'll
need signed copyright papers for this to go into Org and Emacs.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: export_file_name problem with new exporter

[Alan Schmitt]

Achim Gratz <Stromeko@nexgo.de> writes:

> Alan Schmitt writes:
>> TINYCHANGE
>
> As much as you would wish it wasn't so, your patch exceeds the tiny
> change limit (not even counting your previous contributions) and you'll
> need signed copyright papers for this to go into Org and Emacs.

OK, there's something I'm missing here. First, the patch is a copy of
the same functions in org-e-latex with about 100 characters modified (by
repeatedly renaming "latex" into "beamer" in several places). I thought
it would qualify for a "TINYCHANGE", but I guess this just proves I'm
not a lawyer ;-)

Second, I was under the impression that commits to contrib did not
participate to the 20 lines limit, as this directory is not included in
emacs. I put "TINYCHANGE" because Nicolas asked me when I did a small
change to org-e-latex.

I have actually signed and sent the papers to the FSF, I'm waiting to
get them back. Nevertheless it may be good to clarify whether the
TINYCHANGE restriction applies to files in contrib.

Best,

Alan

Re: export_file_name problem with new exporter

[Achim Gratz]

Alan Schmitt writes:
> OK, there's something I'm missing here. First, the patch is a copy of
> the same functions in org-e-latex with about 100 characters modified (by
> repeatedly renaming "latex" into "beamer" in several places). I thought
> it would qualify for a "TINYCHANGE", but I guess this just proves I'm
> not a lawyer ;-)

Yes, that is one of the murkier parts of what is or is not counted as a
contribution that needs copyright assigned and I don't claim to
understand the implications w.r.t. the "20 lines or less" rule (or where
that 20 lines come from really, since you can do something substantial
in much less than 20 lines or something trivial in many more than 20).
However if you want to use that exemption, I guess it would be easier to
verify if that patch was made in two parts, one adding a literal copy
from org-e-latex (with a commit message that marks it as such) and the
second making those repetitive changes, marked as a TINYCHANGE.  Just a
suggestion.

> Second, I was under the impression that commits to contrib did not
> participate to the 20 lines limit, as this directory is not included in
> emacs. I put "TINYCHANGE" because Nicolas asked me when I did a small
> change to org-e-latex.

They don't usually, but the new exporter is scheduled to be moved into
Org core and at that time the copyright needs to be assigned, which is
why Nicolas is already keeping an eye on it.

> I have actually signed and sent the papers to the FSF, I'm waiting to
> get them back. Nevertheless it may be good to clarify whether the
> TINYCHANGE restriction applies to files in contrib.

Then I would think that everything should be resolved soon, however the
processing of papers can sometimes take a good deal of time.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Terratec KOMPLEXER:
http://Synth.Stromeko.net/Downloads.html#KomplexerWaves

Re: export_file_name problem with new exporter

[Suvayu Ali]

On Sun, Dec 09, 2012 at 12:04:18PM +0100, Achim Gratz wrote:
> Alan Schmitt writes:
> > I have actually signed and sent the papers to the FSF, I'm waiting to
> > get them back. Nevertheless it may be good to clarify whether the
> > TINYCHANGE restriction applies to files in contrib.
> 
> Then I would think that everything should be resolved soon, however the
> processing of papers can sometimes take a good deal of time.
> 

The FSF now accepts scans of the signed form I believe.  So the process
can be completed without using snail-mail.

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.

Re: export_file_name problem with new exporter

[Jambunathan K]

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> On Sun, Dec 09, 2012 at 12:04:18PM +0100, Achim Gratz wrote:
>> Alan Schmitt writes:
>> > I have actually signed and sent the papers to the FSF, I'm waiting to
>> > get them back. Nevertheless it may be good to clarify whether the
>> > TINYCHANGE restriction applies to files in contrib.
>> 
>> Then I would think that everything should be resolved soon, however the
>> processing of papers can sometimes take a good deal of time.
>> 
>
> The FSF now accepts scans of the signed form I believe.  So the process
> can be completed without using snail-mail.

Depends on country of the contributor...

> Hope this helps,

-- 

Re: export_file_name problem with new exporter

[Achim Gratz]

Suvayu Ali writes:
> The FSF now accepts scans of the signed form I believe.  So the process
> can be completed without using snail-mail.

The snail mail part wasn't the limiting factor, at least in my case.
:-)


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Waldorf MIDI Implementation & additional documentation:
http://Synth.Stromeko.net/Downloads.html#WaldorfDocs

Re: export_file_name problem with new exporter

[Nicolas Goaziou]

Hello,

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> I have "#+EXPORT_FILE_NAME: ~/tmp/jsseccloud.tex" in an org file, but
> when I export it (either to beamer or to latex), it's using the name of
> the file instead of the given file name.
>
> Am I doing something wrong here?

There is no #+EXPORT_FILE_NAME: keyword. But there is
an :EXPORT_FILE_NAME: node-property for subtree export. There could be
a #+FILE_NAME: keyword (much like :EXPORT_AUTHOR: and #+AUTHOR). Though,
it is too dangerous to my liking.

For example, publishing expects the output file to be generated in the
working directory. Using a different export path per file could lead to
much confusion.

Hence I'd rather not implement it.


Regards,

-- 
Nicolas Goaziou

Re: export_file_name problem with new exporter

[Alan Schmitt]

Nicolas Goaziou writes:

> There is no #+EXPORT_FILE_NAME: keyword. But there is
> an :EXPORT_FILE_NAME: node-property for subtree export. There could be
> a #+FILE_NAME: keyword (much like :EXPORT_AUTHOR: and #+AUTHOR). Though,
> it is too dangerous to my liking.
>
> For example, publishing expects the output file to be generated in the
> working directory. Using a different export path per file could lead to
> much confusion.
>
> Hence I'd rather not implement it.

I understand it. What I actually would like is to be able to specify a
different "working directory". Right now it defaults to the directory
where the org file is, but it's often not satisfactory (especially when
compilation creates additional files). Would this be difficult to add?

Thanks,

Alan

Re: export_file_name problem with new exporter

[Nicolas Goaziou]

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> I understand it. What I actually would like is to be able to specify a
> different "working directory". Right now it defaults to the directory
> where the org file is, but it's often not satisfactory (especially when
> compilation creates additional files). Would this be difficult to add?

That is the purpose of publishing, as discussed in this thread.

Btw, please commit your changes to org-e-beamer.el when you have
validated your FSF papers.


Regards,

-- 
Nicolas Goaziou

Re: export_file_name problem with new exporter

[Alan Schmitt]

Nicolas Goaziou writes:

> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> I understand it. What I actually would like is to be able to specify a
>> different "working directory". Right now it defaults to the directory
>> where the org file is, but it's often not satisfactory (especially when
>> compilation creates additional files). Would this be difficult to add?
>
> That is the purpose of publishing, as discussed in this thread.

Not really: looking at the code, publishing does all its work in the
current directory, then moves the final file to its place (leaving all
the mess compilation made behind). I understand the reason for such a
thing: publishing should only publish the final result.

In other words, I see three places of interest:
- where the org file is
- where export and compilation occurs
- where the final result is put

Publishing lets us deal with the last one, but I don't think there is a
way to distinguish between the first two.

> Btw, please commit your changes to org-e-beamer.el when you have
> validated your FSF papers.

By "validating", do you mean that I have received them back signed from
the FSF? (I signed and sent them a few weeks ago, still waiting to get
them back ...)

Alan

Re: export_file_name problem with new exporter

[Nicolas Goaziou]

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> In other words, I see three places of interest:
> - where the org file is
> - where export and compilation occurs
> - where the final result is put
>
> Publishing lets us deal with the last one, but I don't think there is a
> way to distinguish between the first two.

No, there isn't.

OTOH, step 2 only makes sense for back-ends that require to compile
output. Maybe a local solution can be provided for them. For example,
tweaking `org-e-latex-pdf-process' probably allows to move compilation
elsewhere.

> By "validating", do you mean that I have received them back signed from
> the FSF? (I signed and sent them a few weeks ago, still waiting to get
> them back ...)

Yes. We have to wait for confirmation from the FSF. It shouldn't be too
long now.


Regards,

-- 
Nicolas Goaziou

Re: export_file_name problem with new exporter

[Alan Schmitt]

Nicolas Goaziou writes:

>> By "validating", do you mean that I have received them back signed from
>> the FSF? (I signed and sent them a few weeks ago, still waiting to get
>> them back ...)
>
> Yes. We have to wait for confirmation from the FSF. It shouldn't be too
> long now.

I have received the confirmation from the FSF (the scanned papers with
their signature).

I'll commit as soon as I can find the magic git incantations to get rid
of the "merge" commits that happened as I was pulling changes from the
repository.

Alan

Re: export_file_name problem with new exporter

[Achim Gratz]

Alan Schmitt writes:
> I'll commit as soon as I can find the magic git incantations to get rid
> of the "merge" commits that happened as I was pulling changes from the
> repository.

Just cherry-pick your changes on top of the new master or use the
rewrite facility in magit.  If you want to avoid this in general, see:

http://orgmode.org/worg/org-faq.html#keeping-local-changes-current-with-Org-mode-development


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

Re: export_file_name problem with new exporter

[Bastien]

Hi Alan,

Achim Gratz <Stromeko@nexgo.de> writes:

> Alan Schmitt writes:
>> I'll commit as soon as I can find the magic git incantations to get rid
>> of the "merge" commits that happened as I was pulling changes from the
>> repository.
>
> Just cherry-pick your changes on top of the new master or use the
> rewrite facility in magit.  If you want to avoid this in general, see:
>
> http://orgmode.org/worg/org-faq.html#keeping-local-changes-current-with-Org-mode-development

... or simply don't worry too much about the merge commits.

-- 
 Bastien

Re: export_file_name problem with new exporter

[Alan Schmitt]

Achim Gratz writes:

> Alan Schmitt writes:
>> I'll commit as soon as I can find the magic git incantations to get rid
>> of the "merge" commits that happened as I was pulling changes from the
>> repository.
>
> Just cherry-pick your changes on top of the new master or use the
> rewrite facility in magit.

I tried and it did not work. So I just reset everything and applied my
change on top of a clean checkout. It's been pushed.

> If you want to avoid this in general, see:
>
> http://orgmode.org/worg/org-faq.html#keeping-local-changes-current-with-Org-mode-development

This will be most useful, thanks a lot.

Alan

Re: export_file_name problem with new exporter

[Achim Gratz]

Alan Schmitt writes:
> In other words, I see three places of interest:
> - where the org file is
> - where export and compilation occurs
> - where the final result is put
>
> Publishing lets us deal with the last one, but I don't think there is a
> way to distinguish between the first two.

Having a separate build directory would really need to be accompanied by
a proper build system for all but the most simple tasks.  I think you
can very well hand off the publishing to make or something like that.
If you are only concerned about the litter from LaTeX, use a variant of
"texi2pdf --tidy" instead of invoking pdftex directly.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf rackAttack:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

Re: export_file_name problem with new exporter

[Alan Schmitt]

Achim Gratz writes:

> Alan Schmitt writes:
>> In other words, I see three places of interest:
>> - where the org file is
>> - where export and compilation occurs
>> - where the final result is put
>>
>> Publishing lets us deal with the last one, but I don't think there is a
>> way to distinguish between the first two.
>
> Having a separate build directory would really need to be accompanied by
> a proper build system for all but the most simple tasks.  I think you
> can very well hand off the publishing to make or something like that.
> If you are only concerned about the litter from LaTeX, use a variant of
> "texi2pdf --tidy" instead of invoking pdftex directly.

Actually, I think this is the way to go. Having a "run this command
(asynchronously) after publishing" would be perfect. I need to look into
org-publish to see if this is not already present, and if it would be
difficult to add.

Alan