PrestoSoft Community

So... with this batch file... have you changed your text editor so that instead of calling EDP directly, it calls the batch file and passes the names of the two files it just wrote into %TEMP% ? Do the files have to be left in %TEMP% afterwards? If not it might be better to delete them. Rather than ...

Even if there's a way to do this, there might need to be a way to limit its effect so that extensionless files elsewhere on the system are not also seen as having this type of contents. I've used two programmers' text editors which allow syntax highlighting to be applied to files based not only on t...

Last time you said you minimised the EDP window then reopened it. This time is different, you say you switch to VS then back to EDP. What are you using to perform the 'switch' - a keyboard shortcut, or Alt-tab switching, or just clicking on part of the other app's window? The effect you describe see...

Hooray! I'm guessing that this is because Windows (or within EDP, a call to a Win API routine to execute a command) would have Windows parsing the passed command line and splitting it into yourcompiledrexx.exe (or rxlauncher.exe) then successive arguments (in C terms) which are then passed to the re...

How, precisely, are you checking in your rexx exec to see how many incoming parms there are?

While writing my contributions above I noticed that sometimes I referred to $OUTPUTFILE and sometimes $OUTPUTFILEPATH and went back to find out why I'd refrerred to both. It turns out that there's a documentation error, and some of my posts were based on what I read in the help file and others on wh...

Well I'm glad you've got something working! I think you would do well to consider installing ooREXX - unlike Jeff's Reginald, it's still being developed; although it's now an open-source project it started off as a 'proper' IBM product. A lot of people used to 'classic' rexx avoid it because they th...

G'morning! "OP" is a commonly-used abbreviation on forums and newsgroups etc, and means almost always (the) "Original Poster" ie whoever started the discussion. Once or twice I've seen it mean (the) Original Post. There's no command that in one command window will allow you to wr...

> In general, the way to debug a plug-in is to forget EDP for a minute and make sure that you can open a CMD window and run a console program > successfully, either by creating an output file or by outputting the result into the command window itself (STDOUT). Once you achieve that, setting > up EDP...

> I tried your variation (I'm using Reginald Rexx, but they should be roughly the same). Reginald's not something I've seen any reference to for years and years. I think it used to crop up in discussions in comp.lang.rexx quite a lot. The problem with it was that Jeff Glatt took an early version of ...

Maybe 'compiled' rexx execs are not meant to produce any sysout - maybe the assumption is that they run 'silently'? Ie either only handle files, or use (in ooREXX terms) ooDialog or the simple prompt and message functions to commmunicate with a user. When you ran your plugin at your last employer, d...

Hang on... I know what the problem is. Your compiled exec isn't running in the command window you call it from, but is opening a new instance of cmd.exe to run the exec. I don't know which version of rexx you're using, but in ooREXX terms this is like the difference between using rexx.exe and rexxh....

> I assume I can't define the argument along the lines of $INPUTFILEPATH >1 (or however you write it) You don't need to. EDP (according to the help pages on plugins) assumes that a plugin, if you don't tell EDP otherwise, will write to sysout. Perhaps if you looked at the definitions of the supplied...

I just tried this here with ooREXX v4.2.0 (and an interpreted rexx exec rather than a compiled one) and it did what I expected. I used a simple 'showargs.rex' which contained: /* REXX */ parse arg alla parse source alls say "Rexx: args:" alla say "Rexx: source:" alls exit 0 My re...

Your rexx exec IS writing to sysout - that's what both 'say' and lineout used that way do. The console window IS sysout. Is the test1 rexx exec compiled? If it isn't then the .exe you need to define in the plugin definition is probably your regina / oorexx interpreter, passing it a parm of the rexx ...