Thanks for the quick response! I haven't had time to address this myself. I'm getting some basic syntax coloring, just by indenting.

Nice!

Mup requires me to run two command lines:

mup myfile.mup

when this is run, if it has no errors, it creates the file:

myfile.gs

which then needs to be run by ghostscript.

I'm getting the hang of running both these from the command line, but I haven't been able to get my head around commando yet, and I don't know how to direct the created file on to the next app.

It's always the same thing, so I don't need a gui--just a macro with a key command would be great.

Any advice appreciated. I imagine it's quite easy to do, but I'm having trouble finding information in the documentation that doesn't presume a lot more command line experience than I have.... Thanks! eric

K. There are at least 2 easy ways to do this. The first would be to create a macro that compiles the file you are currently editing in jedit. This macro would basically just run the commands you provided, in the console plugin. You should read the writing macros section in the help docs, so you at least know how to install them. Then you can install this macro (saved as Compile_Current_File.bsh):
[code]

// replace the strings with the actual commands if they are wrong.
String mupCompileCommand = "mup";
String ghostScriptCommand = "gs";
// get the current directory
String bufferPath = buffer.getPath();
String fileName = buffer.getName();
String rootFileName = fileName;
// remove the ".mup" file extension 
rootFileName = rootFileName.substring(0, rootFileName.length() - 4);
// the buffer path has the file name in it - so remove it.
bufferPath = bufferPath.replace(fileName, "");
if(bufferPath.contains(" ")) {
    // for windows: if there's a space in the path then we need to wrap the
    // path in quotes.
    bufferPath = "\"" + bufferPath + "\"";
}
// change directory - I'm assuming that you need to be in the directory of 
// the file to compile it.
runInSystemShell(view, "cd " + bufferPath);
// wait for that command to finish
waitForConsole(view);

if(fileName.contains(" ")) {
    // for windows: if there's a space in the name then we need to wrap the
    // path in quotes.
    fileName = "\"" + fileName + "\"";
}
// compile current file with mup compile command
runInSystemShell(view, mupCompileCommand + " " + fileName);
// wait for that command to finish
waitForConsole(view);

// create gs file
String gsFileName = rootFileName + ".gs";
if(gsFileName.contains(" ")) {
    // for windows: if there's a space in the name then we need to wrap the
    // path in quotes.
    gsFileName = "\"" + gsFileName + "\"";
}
// execute ghostscript on newly created gs file.
runInSystemShell(view, ghostScriptCommand + " " + gsFileName);
// wait for that command to finish
waitForConsole(view);

[/code]
Learn from the past. Live in the present. Plan for the future.

Wow, that's unbelievably helpful. I have already figured out how to set up macros, so I will try this out right away.

-edit- it works. Wow, I can't thank you enough. This would have taken a long time to figure out on my own!!!!

Thanks again! -eric

I'm very happy to help. I know you happy with that macro, but I feel I should at least mention the other option. The other option is pretty much the same, in fact it uses exactly the same code w/out the calls to "runInSystemShell". The second option is to create a commando file. You should read the Console plugin help docs enough so you can install them, then you can install this.
[code]

<?xml version="1.0" ?>
<!DOCTYPE COMMANDO SYSTEM "commando.dtd">
<COMMANDO>
    <UI>
        <ENTRY LABEL="MUP Compile Command" VARNAME="mupCompileCommand" DEFAULT="mup" />
        <ENTRY LABEL="GhostScript Command" VARNAME="ghostScriptCommand" DEFAULT="gs" />
    </UI>
    <COMMANDS>
        <COMMAND SHELL="System" CONFIRM="FALSE">
            <!-- Changing directories to your file -->
            // get the current directory
            String bufferPath = buffer.getPath();
            String fileName = buffer.getName();
            String rootFileName = fileName;
            // remove the ".mup" file extension 
            rootFileName = rootFileName.substring(0, rootFileName.length() - 4);
            // the buffer path has the file name in it - so remove it.
            bufferPath = bufferPath.replace(fileName, "");
            if(bufferPath.contains(" ")) {
                // for windows: if there's a space in the path then we need to wrap the
                // path in quotes.
                bufferPath = "\"" + bufferPath + "\"";
            }
            // change directory - I'm assuming that you need to be in the directory of 
            // the file to compile it.
            return "cd " + bufferPath;
        </COMMAND>
        <COMMAND SHELL="System" CONFIRM="FALSE">
            <!-- Compiling mup file -->
            if(fileName.contains(" ")) {
                // for windows: if there's a space in the name then we need to wrap the
                // path in quotes.
                fileName = "\"" + fileName + "\"";
            }
            // compile current file with mup compile command
            return mupCompileCommand + " " + fileName;
        </COMMAND>
        <COMMAND SHELL="System" CONFIRM="FALSE">
            <!-- Executing gs on newly created gs file -->
            String gsFileName = rootFileName + ".gs";
            if(gsFileName.contains(" ")) {
                // for windows: if there's a space in the name then we need to wrap the
                // path in quotes.
                gsFileName = "\"" + gsFileName + "\"";
            }
            // execute ghostscript on newly created gs file.
            return ghostScriptCommand + " " + gsFileName;
        </COMMAND>
    </COMMANDS>
</COMMANDO>

[/code]
The difference here is that if there is an error it will prompt you to ask if you want to continue on with the rest of the commands. This way, if you compile a simple mup file and gs runs it, then you make changes to your mup file and it doesn't compile, gs won't just run your last one. You also get a nice simple UI to help you with optional inputs.

They are both very similar, just thought it was worth mentioning.

Cheers,
Eric

Learn from the past. Live in the present. Plan for the future.