Re: XJed do not set XWINDOWS with -batch

"G. Milde" <g.milde@xxxxxx> wrote:
> On  2.06.05, Joerg Sommer wrote:
>  
>> one example:
>
>> message("You run "+
>> #ifdef XWINDOWS
>>         "XJed"
>> #else
>>         "Jed"
>> #endif
>>         );
>
>> $ xjed -batch -n -l /tmp/test.sl
>> You run Jed
>  
>> Why this?
>
> Try `xjed` on a console, and you'll find that it runs jed (instead of
> complaining about missing DISPLAY).

I thought it execs jed if DISPLAY is missing. Is gpm support missing if I
use xjed in the console?

> I suppose a similar scheme works with -batch: the X layer is (seemingly)
> not needed and hence not activated.

But it should set XWINDOWS.

>> A second problem, that arises with this issue: You can't use precompiled
>> slang files with different jed types. 
>
> IMHO, precompiled files are a different issue. 
>
> You can use precompiled files with proper care. However, as the
> preprocessor options are evaluated during the byte-compile,
> distinguishing between jed and xjed with XWINDOWS doesnot work in
> commonly used byte-compiled files.

Because it is used in jed-lib, should we must create different byte
compiled files in Debian for jed and xjed?

>> Currently I use the .slc files build with jed with xjed. This fails, if
>> they include XJed specific code.
>
> This is why I use "#ifdef XWINDOWS" only in  .jedrc.

But #ifdef is better, because your if (is_defined...) evaluates everytime
to the same value. Or does slang optimize such constructs?

Jörg.
-- 
Ich halte ihn zwar für einen Schurken und das was er sagt für
falsch - aber ich bin bereit mein Leben dafür einzusetzen, daß
er seine Meinung sagen kann.            (Voltair)