Find your next open-source project

Search by name, purpose, or keyword — or paste a GitHub repository URL

Illson/RustText

System Tools

A Windows x64 text editor and large-log viewer built in Rust with GPUI, featuring JSON validation, search, and session restore.

513
2
Rust
1 day old

Overview

RustText is a Windows x64 text editor and log viewer written in Rust using GPUI Kit. It targets two related jobs: editing text files with tabs, search and replace, JSON validation and formatting, and browsing very large log files without loading them entirely into memory. Files over 50 MiB open automatically in log-view mode; smaller files can be opened as logs from the menu. The README is written in Russian and the project does not declare a license.

Getting started

The documented distribution is a portable build: unpack the archive and run rusttext.exe; the executable is also available from the GitHub releases page. On first use, open a file with Ctrl+O, by passing a path on the command line, or by dragging it into the window. Tabs can be split into horizontal and vertical groups, and the session, including open tabs, selection and window size, is restored on the next launch. Recent files and closed-tab history are stored under %LOCALAPPDATA%\RustText.

To build from source, install Rust with the x86_64-pc-windows-msvc target, the Visual Studio C++ tools and Windows SDK, and CMake on PATH, then run from the repository root:

cargo run --locked
cargo run --locked -- "C:\path\to\file.txt"

The toolchain version is pinned in rust-toolchain.toml.

To register file associations, run the packaged executable from its permanent folder:

$registration = Start-Process -FilePath (Resolve-Path '.\rusttext.exe').Path -ArgumentList '--register-file-associations' -Wait -PassThru
if ($registration.ExitCode -ne 0) { throw 'Failed to register RustText in Windows' }

After registration, the default app for .txt, .json, .xml and .log is confirmed in Windows Settings. Managed machines can use the documented association policy XML instead.

Working with logs and JSON

Large logs use paged loading with line numbers, progress toward full indexing, and a minimap that samples the file. The log search panel supports regular expressions, case-sensitive and whole-word matching, and returning results in batches. A time field can jump to the first entry at or after a given timestamp, which assumes the log is time-ordered. The README also documents trimming the beginning of a log: this modifies the source file and needs exclusive access plus free space for a full backup next to it.

JSON validation runs automatically for .json files and for text starting with { or [, reporting the line and column of an error. Ctrl+Shift+J formats selected or whole-document JSON, with input and output each limited to 64 MiB. The line generator supports {int_from_5}, {guid} and {rand_string_24} style placeholders and can write large outputs directly to a file with progress and cancellation.

Constraints

The build and testing instructions target Windows PowerShell; the README says the build was verified on Windows 11 x64 and that Windows 10 x64 still needs separate verification. Source builds require the MSVC target and CMake, and the provided test script is PowerShell 7 based. Logs and large generated outputs are handled by streaming or paging, but JSON formatting has a 64 MiB per-side limit. Updating from inside the app downloads the release archive and checks it against SHA-256, and packaging requires a release tagged like v0.1.1 with RustText.zip and RustText.zip.sha256 attached. The repository declares no license, so redistribution and reuse terms are not stated.

HotRepo's take

The project appeared on HotRepo's new-project list on 2026-11-17, with 28 stars gained in about an hour and 137 stars total in the observed window. That is a short record, so it supports only the fact that the project drew attention at launch, not a trend. The README is unusually detailed about interaction behavior, packaging and tests, which is more than a shell around a download link; the open question is the binary itself, since the documented portable release is a prebuilt Windows executable whose link to the source and publisher is not described in the README.

Written by AI from the project's README, updated . The project's own docs are the source of truth.