RSyntaxTextArea

A syntax highlighting, code folding text editor for Java Swing applications.

Runssource: GitHubJavaBSD-3-Clausecommit a60455d2a20c

Java, BSD-3-Clause licensed. The project labels itself: code editor, java swing applications and syntax highlighting.

RSyntaxTextArea runs. An Argusic agent installed it in 4.5 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.

Gradle build produces rsyntaxtextarea-4.0.2-SNAPSHOT.jar; all 4099 unit tests pass; the RSyntaxTextAreaDemo desktop app starts and runs on the virtual display.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
2
last tested
stars
1,260
forks
269
open issues
122
watchers
55
size
16 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Install time
5 minutes
Cold machine to finish
3 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
./gradlew build --warning-mode all exited 0; 4099 tests passed (0 failures, 0 errors); ./gradlew RSyntaxTextAreaDemo:run launched RSyntaxTextAreaDemoApp on Xvfb display :99 and the process stayed up
Model tokens used
23,006
Exact commit tested
a60455d2a20c
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

All done. Here's the summary:
**Build:** `./gradlew build --warning-mode all` — exited 0, 23 actionable tasks executed.
**Tests:** 4,099 passed, 0 failures, 0 errors, 18 skipped.
**Demo launch:** `./gradlew RSyntaxTextAreaDemo:run` — the `RSyntaxTextAreaDemoApp` Java process st…
The only setup needed was downloading JDK 25 (Adoptium Temurin-25.0.5+8) since none was pre-install…
tokens used
23,006
All done. Here's the summary:
**Build:** `./gradlew build --warning-mode all` — exited 0, 23 actionable tasks executed.
**Tests:** 4,099 passed, 0 failures, 0 errors, 18 skipped.
**Demo launch:** `./gradlew RSyntaxTextAreaDemo:run` — the `RSyntaxTextAreaDemoApp` Java process st…
The only setup needed was downloading JDK 25 (Adoptium Temurin-25.0.5+8) since none was pre-install…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Reached a running state on a clean machine, with the session recorded.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed BSD-3-Clause, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Took 4.5 minutes to install, slower than the median of the 11 comparable projects Argusic has measured.

Of the 12 code-editor projects Argusic has installed and timed, RSyntaxTextArea was the 7th fastest to reach a running state, and 11 of 12 reached one at all.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 4.5 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.02
Argusic Runner1/3Runs100.000.04

Topics (from GitHub)

code-editorjava-swing-applicationssyntax-highlighting

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/RSyntaxTextArea.svg)](https://argusic.com/subject/rsyntaxtextarea)

Questions

Does RSyntaxTextArea run?
Yes. RSyntaxTextArea runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test RSyntaxTextArea?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit a60455d2a20c. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test RSyntaxTextArea?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does RSyntaxTextArea take to install?
4.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does RSyntaxTextArea need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing RSyntaxTextArea?
Nothing did, in the recorded run: zero errors between clone and running.
How does RSyntaxTextArea compare with the alternatives?
Of the 12 code-editor projects Argusic has installed and timed, RSyntaxTextArea was the 7th fastest to reach a running state, and 11 of 12 reached one at all.
Where is the evidence for RSyntaxTextArea?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion