PrestoSoft Community

Dööööhh.

All this time and it's been my fault !!!!! Here's an example of what I was originally using for my code (arg(1) and arg(2) were my last test attempts)

arg parms1 parms2

say 'Number of argument 'arg()

say 'Arg(1) 'arg(1)
say 'Arg(2) 'arg(2)

say 'Parms1 'parms1
say 'Parms2 'parms2


I ...

You DON'T have to have an output file created and then use the 'DOS' (it's not DOS actually, it's cmd.exe under Windows) TYPE command to copy the file to sysout. You just need to have specified $OUTPUTFILEPATH on the definition of the plugin and make the plugin code parse that filename and use that ...

YES !!!!

Many thanks Jeremy for pushing/pointing me in the right direction. I finally got it to work using the following trick/workaround.
Since the BC program expected an output file (which it then used as input) I could use the same code, but, for ED, deliberately set a temporary output file ...

Thanks again for all your efforts.

I did a quick try this morning, and I'm wondering if Jeremy's guess isn't correct (about the console). Here's a SC showing my running test1.exe that simply outputs 10 rows of info. As you can (?) see, the actual Rexx SAY's go to a NEW console window and not the ...

When you ran your plugin at your last employer, did you have the impression that a cmd window ever opened and closed immediately? No. The plug-in was ran, read the input file, created the output file and BC then (under the covers ?) read the output file into memory.

but it would maybe explain ...

Thank you for taking the time to try and help me. I tried your variation (I'm using Reginald Rexx, but they should be roughly the same).

My ED settings are now

Application C:\Program Files (x86)\Reginald\RxLaunch.exe
Arguments H:\A_MS_rexxcode\test1.rex $INPUTFILEPATH (an uncompiled Rexx script ...

If the test1 exec is compiled then the plugin definition presumably only needs the path to the compiled exec followed by the $INPUTFILEPATH symbol.

It IS compiled.My parms for the plug-in look like this. The application is H:\A_MS_exe\test1.exe and the arguments are $INPUTFILEPATH

I assume I can ...

It suddenly occurred to me that I could make life a lot easier. I took the test script shown earlier (TEST1) and specified THAT as my plug-in.

Note the loop of the 10 records and the Rexx script that does this:-

LINEOUT(, 'Record 'i)


Note how the first parm to LINEOUT is missing. This is what ...

Jeremy
You also suggest that the BC plugin is used like: H:\A_MS_exe\BC_CONVERT_MFE_FILE.exe %n %s %t
where %n %s and %t are defined as %s source file %t target file %n original file

- so does that mean the BC plugin gets handed both of the files that are being compared? If not, what did source ...

PSGURU

Assuming that test1 is the app (executable file), what are argument1 and argument2? I was hoping for a real world example, with actual, presumably, file names and the output.

Argument1 and 2 are simply the strings I entered in the DOS window. If I'd entered test1 fred bert yo'd have seen ...

Hmmm, not sure what you mean there.

The EXE is compiled Rexx on the PC. A (hopefully) similar Rexx script looks like this:-

/* REXX */
arg parms
say 'In test1 ***'
do i = 1 to words(parms) /* Loop round showing each argument passed */
say 'Parm 'i' 'word(parms,i)
end
do I = 1 to 10
result ...

Basically, anything you like. The SIMPLEST would be to be able to specify an output file that ED then picks up and reads in and shows.

What seems to be the problem is that I can't seem to specify some sort of output file as an argument that is then picked up in ED the same way it is in BC.

Okay, have tested a bit more at home, and this is what I'm seeing. First of all, I realize/appreciate that the following comments are a bit "apples and pears" (no pun intended based on ED's icon).

In Beyond Compare, I specify the plug-in in the following manner

H:\A_MS_exe\BC_CONVERT_MFE_FILE.exe ...

Thanks Jeremy - I'll test tonight and let you know.

One final (?) append. I removed the output file on the options settings, so now I have arguments = $INPUTFILEPATH only.

I'm now seeing the attached capture. So .... how do I point at the file that ED should be reading?

Thought I'd include one extra screen capture (this was found in C:\Users ...