{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Welcome to the LinUtil Documentation!","text":""},{"location":"#running-the-latest-release-of-linutil","title":"Running the latest release of LinUtil","text":"<p>To get started, run the following command in your terminal:</p>"},{"location":"#stable-branch","title":"Stable branch","text":""},{"location":"#curl-fssl-httpschristituscomlinux-sh","title":"<pre><code>curl -fsSL https://christitus.com/linux | sh\n</code></pre>","text":""},{"location":"#installation","title":"Installation","text":"<p>LinUtil is also available as a package in various repositories:</p> <p></p> Arch Linux LinUtil can be installed on [Arch Linux](https://archlinux.org) with three different [AUR](https://aur.archlinux.org) packages: - `linutil` - Stable release compiled from source - `linutil-bin` - Stable release pre-compiled - `linutil-git` - Compiled from the last commit (not recommended) by running: <pre><code>git clone https://aur.archlinux.org/<package>.git\ncd linutil\nmakepkg -si\n</code></pre> Replace `` with your preferred package. If you use [yay](https://github.com/Jguer/yay), [paru](https://github.com/Morganamilo/paru) or any other [AUR Helper](https://wiki.archlinux.org/title/AUR_helpers), it's even simpler: <pre><code>paru -S linutil\n</code></pre> Replace `paru` with your preferred helper and `linutil` with your preferred package. Cargo LinUtil can be installed via [Cargo](https://doc.rust-lang.org/cargo) with: <pre><code>cargo install linutil\n</code></pre> Note that crates installed using `cargo install` require manual updating with `cargo install --force` (update functionality is [included in LinUtil](https://christitustech.github.io/linutil/userguide/#applications-setup)) <p>After you've ran the command, you should see a GUI on your screen; It will look something like this:</p> <p></p> <p>Info</p> <p>LinUtil is updated weekly as of the time of writing. Consequently, features and functionalities may evolve, and the documentation may not always reflect the most current images or information.</p>"},{"location":"KnownIssues/","title":"Known Issues","text":"<ul> <li>Known Issues</li> </ul>"},{"location":"contributing/","title":"Contributing Guide","text":"<p>\\n\\n# Contributing Guidelines for Linutil</p> <p>Thank you for considering contributing to Linutil! We appreciate your effort in helping improve this project. To ensure that your contributions align with the goals and quality standards of Linutil, please follow these guidelines:</p>"},{"location":"contributing/#1-install-rust","title":"1. Install Rust:","text":"<p>Make sure you have Rust installed on your machine. You can install it by following the instructions at rust-lang.org.</p>"},{"location":"contributing/#2-fork-and-clone-the-repo","title":"2. Fork and Clone the repo","text":"<ol> <li>Make a fork of the repo in GitHub</li> <li>Clone the fork <code>bash git clone https://github.com/YOUR_USERNAME_HERE/linutil.git cd linutil</code></li> </ol>"},{"location":"contributing/#3-make-your-changes","title":"3. Make your changes","text":"<ul> <li>Edit the files you want to change: Make your changes to the relevant files.</li> <li>Test your changes: Run <code>cargo run</code> to test your modifications in a local environment and ensure everything works as expected.</li> </ul>"},{"location":"contributing/#4-understand-the-existing-code","title":"4. Understand the existing code","text":"<ul> <li>Have a clear reason: Don\u2019t change the way things are done without a valid reason. If you propose an alteration, be prepared to explain why it\u2019s necessary and how it improves the project.</li> <li>Respect existing conventions: Changes should align with the existing code style, design patterns, and overall project philosophy. If you want to introduce a new way of doing things, justify it clearly.</li> </ul>"},{"location":"contributing/#5-learn-from-past-pull-requests-prs","title":"5. Learn from Past Pull Requests (PRs)","text":"<ul><li>CheckmergedPRs:R
