From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: [patch][test] Avoid writes to non-temp test-example files
Date: Thu, 05 Jan 2012 20:01:43 +0100 [thread overview]
Message-ID: <87r4zenfc8.fsf@Rainer.invalid> (raw)
In-Reply-To: m28vlmrogc.fsf@btinternet.com
Martyn Jago <martyn.jago@btinternet.com> writes:
> Wow! Strictly speaking I guess that's an NTemacs24 bug, but we do have
> the option of over-riding the default Emacs tmp location, which may
> incur some extra house-keeping by the test-runners. I will leave that
> decision to a maintainer.
As I said, I have not yet checked why it ends up where it does (it may
be some time before I get to the bottom of this). It may still have to
do with the environment — I start NTemacs from Cygwin to be able to use
Cygwin's make and this combination is somewhat fragile. Thanks for
confirming that it isn't a setting that the test framework alters.
> I guess the makefile could issue a message on windows if an env var is
> not set?
I'll have to think about the ramifications of doing this, but it is
certainly possible. In fact, I might want to do that anyway to have
texi2pdf put the auxiliary files into a place within the build
directory, but not under doc.
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
next prev parent reply other threads:[~2012-01-05 19:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 17:50 [patch][test] Avoid writes to non-temp test-example files Martyn Jago
2012-01-04 18:29 ` Nick Dokos
2012-01-05 10:35 ` Martyn Jago
2012-01-05 15:31 ` Nick Dokos
2012-01-04 19:02 ` Bastien
2012-01-05 17:01 ` Achim Gratz
2012-01-05 18:31 ` Martyn Jago
2012-01-05 19:01 ` Achim Gratz [this message]
2012-01-06 16:51 ` Achim Gratz
2012-01-06 17:24 ` Martyn Jago
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r4zenfc8.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).