@jutge.org/toolkit 4.4.7 → 4.4.16
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/assets/prompts/creators/create-statement-from-solution.tpl.txt +9 -0
- package/assets/prompts/funcs/creators/create-solution.tpl.txt +23 -0
- package/assets/prompts/funcs/creators/create-statement.tpl.txt +28 -0
- package/assets/prompts/funcs/creators/private-test-cases.tpl.txt +12 -0
- package/assets/prompts/funcs/creators/sample-test-cases.tpl.txt +16 -0
- package/assets/prompts/funcs/creators/sample.dt.tpl.txt +15 -0
- package/assets/prompts/funcs/examples/statement.tex +23 -0
- package/assets/prompts/funcs/proglangs/py.md +9 -0
- package/assets/prompts/io/examples/statement-coda.tex +7 -0
- package/dist/index.js +719 -464
- package/docs/getting-started-guide.md +6 -0
- package/docs/jutge-ai.md +1 -1
- package/package.json +16 -11
- package/toolkit/clean.ts +5 -4
- package/toolkit/convert.ts +3 -3
- package/toolkit/download.ts +16 -0
- package/toolkit/dummies.ts +219 -0
- package/toolkit/generate.ts +105 -13
- package/toolkit/index.ts +4 -0
- package/toolkit/lint.ts +4 -6
- package/toolkit/make.ts +3 -3
- package/toolkit/quiz.ts +3 -3
- package/docs/windows.md +0 -106
- /package/assets/prompts/{examples → funcs/examples}/statement-coda.tex +0 -0
- /package/assets/prompts/{creators → io/creators}/create-solution.tpl.txt +0 -0
- /package/assets/prompts/{creators → io/creators}/create-statement.tpl.txt +0 -0
- /package/assets/prompts/{creators → io/creators}/create-translation.tpl.txt +0 -0
- /package/assets/prompts/{creators → io/creators}/private-test-cases.txt +0 -0
- /package/assets/prompts/{creators → io/creators}/sample-test-cases.txt +0 -0
- /package/assets/prompts/{examples → io/examples}/statement.tex +0 -0
- /package/assets/prompts/{generators → io/generators}/efficiency.md +0 -0
- /package/assets/prompts/{generators → io/generators}/hard.md +0 -0
- /package/assets/prompts/{generators → io/generators}/random.md +0 -0
- /package/assets/prompts/{proglangs → io/proglangs}/cc.md +0 -0
- /package/assets/prompts/{proglangs → io/proglangs}/py.md +0 -0
package/docs/windows.md
DELETED
|
@@ -1,106 +0,0 @@
|
|
|
1
|
-
# Notes for Windows
|
|
2
|
-
|
|
3
|
-
## Installation
|
|
4
|
-
|
|
5
|
-
- Use PowerShell as terminal. Remember to reopen the terminal after the installation of each tool.
|
|
6
|
-
|
|
7
|
-
- Bun is a JavaScript runtime like Node.js but faster and lighter.
|
|
8
|
-
It is required to run the toolkit on Windows. Install `bun` from https://bun.sh/. It is easy.
|
|
9
|
-
|
|
10
|
-
- Install the toolkit using `bun`:
|
|
11
|
-
|
|
12
|
-
```sh
|
|
13
|
-
bun install --global "@jutge.org/toolkit"
|
|
14
|
-
```
|
|
15
|
-
|
|
16
|
-
The first time may take a while as `bun` needs to download and compile some dependencies. If it fails with a `mkdir` error, just try again, it seems to be a transient error.
|
|
17
|
-
|
|
18
|
-
- Check that the installation was successful:
|
|
19
|
-
|
|
20
|
-
```sh
|
|
21
|
-
jtk
|
|
22
|
-
```
|
|
23
|
-
|
|
24
|
-
It should show the help message. You can always add a `--help` flag to any command to get more information.
|
|
25
|
-
|
|
26
|
-
- Check the tools required by the toolkit:
|
|
27
|
-
|
|
28
|
-
```sh
|
|
29
|
-
jtk doctor
|
|
30
|
-
```
|
|
31
|
-
|
|
32
|
-
It should print information about the installed tools. If any tool is missing, consider installing it and try again. Depending on your workflow, some dependencies may not be necessary.
|
|
33
|
-
|
|
34
|
-
## Upgrade
|
|
35
|
-
|
|
36
|
-
Try to use the latest version of the toolkit. Upgrade the toolkit to the latest version with the following command:
|
|
37
|
-
|
|
38
|
-
```powershell
|
|
39
|
-
jtk upgrade
|
|
40
|
-
```
|
|
41
|
-
|
|
42
|
-
Check the version after upgrading:
|
|
43
|
-
|
|
44
|
-
```powershell
|
|
45
|
-
jtk --version
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
## Dependencies
|
|
49
|
-
|
|
50
|
-
- LaTeX: A LaTeX distribution is required to compile problem statements and get their PDFs. It is not necessary but strongly recommended.
|
|
51
|
-
|
|
52
|
-
For Windows, install MiKTeX from https://miktex.org/download. During installation, select the option to install missing packages on-the-fly.
|
|
53
|
-
|
|
54
|
-
- Pandoc: Pandoc with Lua support is required to convert problem statements to Markdown, Text and HTML. It is not necessary but recommended.
|
|
55
|
-
|
|
56
|
-
Install it easily using the Windows Package Manager (`winget`):
|
|
57
|
-
|
|
58
|
-
```powershell
|
|
59
|
-
winget install --id JohnMacFarlane.Pandoc
|
|
60
|
-
```
|
|
61
|
-
|
|
62
|
-
- Python 3: You only need Python 3 if you plan to use Python scripts in your problems.
|
|
63
|
-
|
|
64
|
-
Install Python from https://www.python.org/downloads/windows/. Make sure to check the option to add Python to the system PATH during installation. The toolkit uses `python3` command to run Python scripts.
|
|
65
|
-
|
|
66
|
-
- C/C++ Compiler: You only need a C/C++ compiler if you plan to use C/C++ programs in your problems. The toolkit uses `gcc` and `g++` commands to compile C and C++ programs, respectively.
|
|
67
|
-
|
|
68
|
-
We suggest using [w64devkit](https://github.com/skeeto/w64devkit), a portable C and C++ development kit for Windows. Here are the steps to install it:
|
|
69
|
-
1. **Download** the latest `.exe` file from https://github.com/skeeto/w64devkit/releases.
|
|
70
|
-
|
|
71
|
-
2. **Extract** by double-clicking the downloaded file and choosing a destination (e.g., `C:\w64devkit`).
|
|
72
|
-
|
|
73
|
-
3. **Run** `w64devkit.exe` from the extracted folder to open a terminal with gcc and g++ available.
|
|
74
|
-
|
|
75
|
-
4. **Test** by typing `gcc --version` in the terminal.
|
|
76
|
-
|
|
77
|
-
5. **Compile programs:**
|
|
78
|
-
|
|
79
|
-
```bash
|
|
80
|
-
gcc myprogram.c -o myprogram.exe
|
|
81
|
-
g++ myprogram.cpp -o myprogram.exe
|
|
82
|
-
```
|
|
83
|
-
|
|
84
|
-
Other options are to install [MinGW-w64](http://mingw-w64.org/doku.php) or use the compiler provided by [MSYS2](https://www.msys2.org/).
|
|
85
|
-
|
|
86
|
-
- Java: You only need Java if you plan to use Java programs in your problems. The toolkit uses the `java` and `javac` commands to run and compile Java programs, respectively.
|
|
87
|
-
|
|
88
|
-
Install the Java Runtime Environment (JRE) from https://www.java.com/en/download/manual.jsp. Make sure to download the Windows version.
|
|
89
|
-
|
|
90
|
-
- Likewise, you may need to install Rust, Haskell and Clojure if you plan to use these languages in your problems. If you know how to install them on Windows, please consider contributing to the documentation.
|
|
91
|
-
|
|
92
|
-
## Miscellaneous tips
|
|
93
|
-
|
|
94
|
-
- Open a file with its associated application with `start filename.extension`.
|
|
95
|
-
|
|
96
|
-
- Show environment variables with `echo $env:VARIABLE`.
|
|
97
|
-
|
|
98
|
-
- Set environment temporarly variables with `$env:VARIABLE=value`.
|
|
99
|
-
|
|
100
|
-
- Set environment variables permanently with `[System.Environment]::SetEnvironmentVariable('VARIABLE', 'value', 'User')`.
|
|
101
|
-
|
|
102
|
-
- Console font doesn't support Unicode: The default console font (Raster Fonts) doesn't support many Unicode characters. Change to a font like "Consolas", "Lucida Console", or "Cascadia Code" in your PowerShell window properties.
|
|
103
|
-
|
|
104
|
-
```
|
|
105
|
-
|
|
106
|
-
```
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|
|
File without changes
|