From: Anthony Cowley <acowley@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-latex-compile timestamp checks
Date: Tue, 26 Jan 2016 14:56:13 -0500 [thread overview]
Message-ID: <m2lh7cqfmq.fsf@Sonmi451.home> (raw)
In-Reply-To: <878u3jdj3m.fsf@gmx.us>
Rasmus writes:
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>>>> Eventually, I think at least ox-texinfo.el, ox-man.el and ox-groff.el
>>>> need a similar trick.
>>>
>>> Perhaps there should be an error check in ox-odt as well? I guess the
>>> only thing that could happen is that the zip/odt can’t be written, which
>>> could happen if it’s open in windows, which is extremely picky with locked
>>> files. [I have had to use a windows machine at work].
>>
>> This makes sense, indeed.
>>
>> Would you want to take care of applying the patches and updating the
>> various export back-ends accordingly, or should I?
>
> My life is a bit stressful at the moment (deadlines). I'm happy to do it,
> and maybe I can do it in the weekend, but if you feel like taking doing it
> I won’t stand in your way.
>
> Rasmus
Just a friendly bump to make sure this doesn't get lost. I think the LaTeX patches should still apply; let me know if there's an issue tracker I could use to record the need for adjustments to other back-ends.
Anthony
next prev parent reply other threads:[~2016-01-26 19:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 23:24 [PATCH] org-latex-compile timestamp checks Anthony Cowley
2016-01-15 12:13 ` Rasmus
2016-01-15 20:34 ` Anthony Cowley
2016-01-16 14:16 ` Nicolas Goaziou
2016-01-16 15:17 ` Rasmus
2016-01-16 23:21 ` Anthony Cowley
2016-01-21 9:54 ` Nicolas Goaziou
2016-01-21 15:53 ` Rasmus
2016-01-26 19:56 ` Anthony Cowley [this message]
2016-01-26 22:14 ` Rasmus
2016-01-26 22:20 ` Nicolas Goaziou
2016-01-26 22:25 ` Rasmus
2016-01-28 9:05 ` Nicolas Goaziou
2016-01-28 10:10 ` Rasmus
2016-01-28 15:48 ` Anthony Cowley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lh7cqfmq.fsf@Sonmi451.home \
--to=acowley@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.