2020-04-22 11:42:34 +09:00
|
|
|
paleofetch
|
|
|
|
|
==========
|
|
|
|
|
|
2020-04-23 07:19:37 +09:00
|
|
|
Like neofetch, but incomplete, written in ~500 lines of C instead of 10,000 lines of bash,
|
2020-04-23 02:43:10 +09:00
|
|
|
and runs a lot faster. Currently it only supports Arch Linux with X running.
|
2020-04-22 11:55:48 +09:00
|
|
|
|
|
|
|
|
Example output:
|
|
|
|
|
|
|
|
|
|
|
2020-04-22 11:42:34 +09:00
|
|
|
|
|
|
|
|
Compiling
|
|
|
|
|
---------
|
|
|
|
|
|
|
|
|
|
make install
|
|
|
|
|
|
2020-04-23 07:19:37 +09:00
|
|
|
Usage
|
|
|
|
|
-----
|
|
|
|
|
|
|
|
|
|
paleofetch
|
|
|
|
|
|
|
|
|
|
By default, `paleofetch` will cache certain information (in `$XDG_CACHE_HOME/paleofetch`)
|
|
|
|
|
to speed up subsequent calls. To ignore the contents of the cache (and repopulate it), run
|
|
|
|
|
|
|
|
|
|
paleofetch --recache
|
|
|
|
|
|
|
|
|
|
The cache file can safely be removed.
|
|
|
|
|
|
2020-04-22 11:42:34 +09:00
|
|
|
FAQ
|
|
|
|
|
---
|
|
|
|
|
|
2020-04-22 14:45:25 +09:00
|
|
|
Q: Do you really run neofetch every time you open a terminal?
|
2020-04-22 14:43:14 +09:00
|
|
|
A: Yes, I like the way it looks and like that it causes my prompt to start midway
|
|
|
|
|
down the screen. I do acknowledge that the information it presents is not actually useful.
|
