shibedrill/oxidefetch
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
Fixed contact info.
This commit is contained in:
Shibe Drill 2023-09-01 19:06:17 -04:00 committed by GitHub
parent b427d4ed27
commit 551c6a13a2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -8,7 +8,7 @@ Neofetch, being a BASH script, has a few downsides in my opinion.
1: It's slow.
2: It only works on platforms which have the BASH shell.
3: It's kinda big, and I like having more compact info.
As such, I wrote OxideFetch. How cool is that? It displays your information in a manner that's compact, and BLAZINGLY fast.
As such, I wrote OxideFetch. How cool is that? It displays your information in a manner that's compact, cross-platform, and BLAZINGLY fast.
I've measured speeds of up to 25 times faster than normal Neofetch on WSL2.
### Features
@ -45,7 +45,7 @@ GPU detection runs on Windows without any dependencies.)
I need to verify the output of the OS information detection libraries I'm pulling in. To do this, I need the help of people
with varying types of systems. I've tested Arch Linux and Windows 10, but nothing else. To help, you can kindly clone this
repo, and inside the folder, run ```cargo test -- --nocapture```, and send the resultant ```test_output.txt``` file to my
noreply email address, or directly to me on Discord at ```Shibe Drill#9730```. This program does NOT collect information
noreply email address, or directly to me on Discord at ```@shibedrill```. This program does NOT collect information
regarding your real name, IP, location, etc. You can look at the file it generates to be sure- it's all plaintext, babey.
### Bugs, Quirks, Unintended Behavior, And Other Shenanigans