Easily create, test, upload and check problems from jutge.org without leaving the terminal.

go get https://github.com/Leixb/jutge

All configuration is done through with enviroment variables, mainly: JUTGE_WORK_DIR, JUTGE_USERNAME and JUTGE_PASSWORD (Although the same options can be set with their respective flags: --work-dir, --user, -password.

• JUTGE_WORK_DIR is the directory where you want all the problem files and data to be downloaded.

• JUTGE_USERNAME (OPTIONAL): is the username (email address) to use when logging into jutge.

• JUTGE_PASSWORD (OPTIONAL): is the password to use when logging into jutge. (!! I do not recommend to set this enviroment variable)

If no user or password are provided, the user will be prompted to enter them when needed.

It is very important to define JUTGE_WORK_DIR as an absolute path and add it to your ~/.bashrc (or the equivalent for your shell).

Example ~/.bashrc:

export JUTGE_WORK_DIR="${HOME}/Documents/jutge/"
export JUTGE_USERNAME="[email protected]"

If you want to use the new command you need to add the file jutge.db into your $JUTGE_WORK_DIR . You can download it directly from this repo with curl:

curl -o "${JUTGE_WORK_DIR}/jutge.db" https://raw.githubusercontent.com/Leixb/jutge/master/jutge.db

Alternatively, you can download it directly using the jutge db download command.

A very common task is to compile and then test the binary, or to compile test and then upload a file. This cannot be done directly with jutge but is fairly easy to do it with some basic shell scripting. For example, you can declare the following functions in your shell configuration file (~/.bashrc):

# Compile and test C   program
jutgecpp() {
  name=$(basename -- "$1")
  out=$(mktemp /tmp/${name%.*}_XXXXX
  g   "$1" -o "$out" -std=c  11 && jutge test "$out"
  rm $out
}

# Compile, test and upload if tests pass. Then wait for veredict and print it.
jutgeall() {
  jutgecpp "$1" && jutge upload "$@" --check
}

You can add auto completion of commands by adding the following line to your shell configuration:

• If you use bash (~/.bashrc):

eval $(jutge --completion-script-bash)

• If you use zsh (~/.zshrc):

eval $(jutge --completion-script-zsh)

There are 6 commands:

• Standard commands:
  • new: creates a new file for a problem (the filename contains the problem code followed by the problem title without accents or spaces e.g.: P71753_ca_Maxim_de_cada_sequencia.cpp)
  • test: tests an executable file against jutge samples (it will download the samples if needed)
  • upload: submits a problem to jutge
• Rarely used commands:
  • check: check veredict of a submission
  • download: downloads sample test cases from jutge (usually not used since tests handles downloads when needed)
  • db: provies some sub commands to edit the the correspondence between codes and titles.

If you want help for any of the commands just run jutge command --help to view all the options and their descriptions.