Terminal cal-style Hijri calendar for scripting and quick lookup
hijri prints a cal-style Islamic calendar to the terminal, showing monthly or full-year views, highlighting the current day and converting dates both ways between Gregorian and Hijri. UtmostBoundary provides this command-line utility as a cross-platform tool for desktop terminals. It offers JSON output for automation, Umm al-Qura accuracy via ICU4X, and English/Arabic localization, making it suited to developers, system administrators, and power users who work in shell environments and need dependable date conversions and event lookups.
What the tool does and how it fits terminal workflows
The app reproduces a classic "cal" experience for the Hijri calendar by printing monthly and full-year views to the console and detecting conversion direction automatically between Gregorian and Hijri dates. It identifies major Islamic events such as Ramadan and Eid and can emit machine-readable output with the --json flag, which lets scripts parse dates and events without manual text scraping.
How it impacts system usage and performance
Lightweight single static binary keeps runtime demands minimal. Built in Rust as a single static executable, the tool has no external runtime dependencies, so it launches quickly from a terminal and can be invoked from scripts or scheduled tasks without loading a runtime environment. That design reduces overhead compared with GUI calendar apps when used in automated workflows.
Safety, accuracy, and localisation mechanics
Calculations use the Umm al-Qura system via ICU4X for civil-calendar accuracy, and the tool supports English transliteration and native Arabic script with a --lang ar flag. It operates as a read-only viewer and converter, so it does not modify system files; output flags and exit codes support reliable integration into larger toolchains.
Who should use it and a practical tip for integration
The tool suits terminal-oriented users who need precise Hijri/Gregorian conversions and scriptable output; developers and sysadmins will get the most value. For automation, run the binary with the JSON output and capture exit codes in your pipeline to avoid string parsing. Recommended.
