Closed nonetrix closed 1 year ago
I will name the fork normie-fetch
Right now I prefer to not implement this feature (at least not as a cli option or in the configuration file): I think that calling a program named uwufetch
and getting no uwu output is not so good; on the other hand, if I call normie-fetch
(or normiefetch
) I would expect something more "normal".
That said, I like the idea and I will support the fork. (uwufying lines are 1332-1335, 473 and all the print statement with the name of an info like CPUWU).
I thought about this topic, and I believe that a library based on the get_info()
code could help to write more fetch programs based on uwufetch
without rewriting everything, so I am working on splitting the code in a frontend and a backend (both in c of course).
This will change a few things:
libuwufetch
(I'm still deciding a name) in other languages will be easierClosing because of inactivity.
Also tecnically this request was kind of fullfilled with libfetch
(Release 2.0)
This program is a extremely good neofetch replacement mainly because it is written in C and is much faster
I do find the UwUifyed text obviously superior but it would be great if it could be disabled perhaps with something like
--no-uwu
or a .config fileIf this is not in the scope of the project I am willing to maintain a fork