From: Achim Gratz <Stromeko@nexgo.de>
To: emacs-orgmode@gnu.org
Subject: Re: test-ob-sh/session
Date: Fri, 03 Aug 2012 22:25:36 +0200 [thread overview]
Message-ID: <87ipczu3i7.fsf@Rainer.invalid> (raw)
In-Reply-To: 87zk6bu5sv.fsf@gmx.com
Eric Schulte writes:
> There are a number of tests which execute shell code blocks in
> test-ob.el. This file has no guards, so it will be run on every
> system.
I know, I'm not (currently) talking about these. What puzzles me is
that the three tests in test-ob-sh get defined and run even though the
feature ob-sh is not available. It may be that this gets somehow
subverted by having the other tests unguarded, but I can't see how.
> I guess at the time I wrote these tests I assumed that every system
> would support both emacs-lisp and sh code blocks.
Specifically a shell that is more or less POSIX compatible... even
though even tcsh passes all tests. :-)
> At some point either
>
> 1. all tests in test-ob.el which run sh code blocks should be placed
> behind conditional guards so they are only loaded when shell support
> is present
That would be preferrable for tests which really depend on a shell being
available.
> 2. all tests in test-ob.el which run sh code blocks should be switched
> to running emacs-lisp code blocks
And this would be preferred for tests which should always be run without
making any assumptions on the environment.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for Waldorf Q V3.00R3 and Q+ V3.54R2:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada
next prev parent reply other threads:[~2012-08-03 20:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 19:05 test-ob-sh/session Achim Gratz
2012-08-03 19:36 ` test-ob-sh/session Eric Schulte
2012-08-03 20:25 ` Achim Gratz [this message]
2012-08-03 19:48 ` test-ob-sh/session Achim Gratz
2012-08-05 16:37 ` test-ob-sh/session Achim Gratz
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=87ipczu3i7.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).