A gedit plugin which can test OI codes.

• Test your OI codes fast.
• Highly customizable: almost all things of OI Tool can be customized.
• Multiunctions: support building, testing multiple testcases, and stress testing against another program.

• Operating system: Linux
• Do NOT put files with extension with prefix ya (such as a.yaerr and f.yainfo) in the same folder with your code.

Download the files in releases and copy them to ~/.config/gedit/tools.

The configuration file should be named .ya in your user folder.

The configuration file should be named .ya in the workspace folder.

The configuration file should be named <name>.ya in the workspace folder.

The configuration file should be like:

key1 = value1
key2 = "value2" # String should be quoted in " "
...
keyn = valuen
# You can insert comments starting with "#" in the configuration file.

If there is no configuration file found, then the default setting will be used.

1. Open your source file <name>.<ext>. After building, the executable file will be named <exe>(<exe>=<name>).
2. Put your testcases in <i>.in and <i>.ans. (<i> is the ID of the testcases, ranging in [0,<testcases>])
3. Press the shortcut key F5.
4. You can see the results in the panel below. Judge results are: AC(Answer correct), WA(Wrong answer), TLE(Time limit exceeded) and RE(Runtime error). Your stdout and stderr are redirected to <exe><i>.out and <exe>.<i>.yaerr respectively.

It is similar to "OI Tool - Build and run testcases".

The only difference is that "OI Tool - Build" will only build the source file and it will not run testcases.

The shortcut key for "OI Tool - Build" is Ctrl + F5.

1. Put your program's executable file <program>, standard program's executable file <std> and input generator's executable file <gen> in the workspace folder.
2. Press the shortcut key Ctrl + Shift + F12.
3. The first generated data that caused a WA will be copied in <program>.yain and <std>.yaout. Your stdout and stderr are redirected to <program>.yaout and <program>.yaerr respectively.