-
Notifications
You must be signed in to change notification settings - Fork 0
Themes and Documentation
use diagprint::{Style, Theme};
let theme = Theme {
border: Style::rgb(20, 185, 181),
patch_add: Style::rgb(100, 255, 100),
patch_remove: Style::rgb(255, 80, 100),
..Theme::default()
};Styles support standard ANSI, ANSI-256, RGB foregrounds and backgrounds, hex colours, bold, dim, italic and underline. color(false) stays authoritative.
With the cybercore feature, diagprint uses the active Cybercore theme, the same CYBERGRID palette as the rest of the Cybercore family (and this wiki):
use diagprint::Theme;
let theme = Theme::cybercore(); // named Cybercore themes are supported tooIt consumes Cybercore's semantic palette rather than duplicating colour values.
cargo run --features cybercore --example cybercoreDocumentationResolver resolves version-aware links using Cargo metadata and lockfiles: Rust error docs, Cargo Book pages, docs.rs for the exact package version, and custom links. Ambiguous versions fail closed.
use diagprint::{DocumentationLink, TerminalDocViewer};
let link = DocumentationLink::rust_error("E0277");
TerminalDocViewer::new().width(96).open_and_print(&link)?;HTTP/HTTPS only, size-limited, control characters sanitized, HTML converted to readable text, code examples extracted and highlighted. It currently uses blocking I/O.
🩺 diagprint · a Cybercore Tech project · MIT OR Apache-2.0
🏠 cybercoretech.net ·
✉️ dev@cybercoretech.net ·
🔒 security@ ·
💬 Discord ·
🐛 Issues ·
☕ Buy Me a Coffee
⚡ Start
- 📥 Installation
- 🚀 Quick Start
- 🧪 Examples
🧱 Build
📤 Ship
🔧 Fix
- 🔧 Remediation
- 🛡️ Safety Model
🔬 Investigate
🛠️ Project
- 🛠️ Contributing
- 🗺️ Roadmap