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
