- Subject: Re: Disable jed.conf (was: Re: Intention of jed-script)
- From: "John E. Davis" <davis@xxxxxxxxxxxxx>
- Date: Tue, 12 Jul 2005 10:36:09 -0400
Joerg Sommer <joerg@xxxxxxxxxxxx> wrote:
>I think it is really necessary to _not_ load jed.conf some times. One
>time is when jed is called as jed-script and the other situation when a
>command line option is given, e.g. --no-etc-conf. How do you think?
As previously mentioned, I do not believe that the problem is with
jed's loading of jed.conf; rather the problem is with the contents of
jed.conf.
>> in your .jedrc file, and then run `jed --batch`. Now create a script,
>> e.g., /tmp/foo that contains:
>>
>> #!/usr/bin/env jed-script
>> vmessage ("jed-script running: BATCH=%d", BATCH);
>
>Interesting. Really interesting.
If jed.conf does something that it should not in batch or script mode,
then it should be modified to perform such operations in a conditional
manner, e.g.,
% jed.conf
if (Batch === 0)
{
% interactive mode
.
.
}
if (Batch == 1)
{
% jed started via `jed --batch`
.
.
}
if (Batch == 2)
{
% jed started via `jed --script` or `jed-script`.
.
.
}
Thanks,
--John
--------------------------
To unsubscribe send email to <jed-users-request@xxxxxxxxxxx> with
the word "unsubscribe" in the message body.
Need help? Email <jed-users-owner@xxxxxxxxxxx>.
[2005 date index]
[2005 thread index]
[Thread Prev] [Thread Next]
[Date Prev] [Date Next]