Another copy of my dotfiles. Because I don't completely trust GitHub.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

102 lines
4.2 KiB

4 years ago
  1. paleofetch
  2. ==========
  3. A rewrite of [neofetch](https://github.com/dylanaraps/neofetch) in C.
  4. Currently only supports Linux and Xorg.
  5. Why use paleofetch over neofetch?
  6. -----------------------------------------
  7. One major reason is the performance improvement. For example: neofetch finishes running after about 222 milliseconds where as paleofetch can finish running in a blazing fast 3 milliseconds.
  8. Note: this testing occured on only 1 computer, it's not a good representation on the performance benefit you may gain.
  9. Example output:
  10. ![example output](example.png)
  11. Dependencies
  12. ------------
  13. Paleofetch requires `libX11` and `libpci`. If you're running Xorg you should already have
  14. the former. On Arch Linux, you should have `libpci` already installed if you have `pciutils`
  15. installed. On other linux distrobutions, you may need to install libpci seperatley
  16. if its not already present.
  17. Compiling
  18. ---------
  19. make install
  20. Usage
  21. -----
  22. After compiling, simply run the executable:
  23. paleofetch
  24. By default, `paleofetch` will cache certain information (in `$XDG_CACHE_HOME/paleofetch`)
  25. to speed up subsequent calls. To ignore the contents of the cache (and repopulate it), run
  26. paleofetch --recache
  27. The cache file can safely be removed at any time, paleofetch will repopulate it
  28. if it is absent.
  29. Configuration
  30. -------------
  31. Paleofetch is configured by editing `config.h` and recompiling.
  32. You can change your logo by including the appropriate header file in the logos directory.
  33. The color with which paleo fetch draws the logo can be chosen by defining the `COLOR` macro,
  34. look up ANSI escape codes for information on customizing this.
  35. The last configuration is the `CONFIG` macro, which controls what information paleofetch
  36. prints. Each entry in this macro should look like
  37. { "NAME: ", getter_function, false }, \
  38. Take note of the trailing comma and backslash. The first piece, `"NAME: "`, sets
  39. what paleofetch prints before printing the information; this usually tells you what
  40. bit of information is being shown. Note that the name entry should be unique for entries
  41. which are to be cached. The second piece, `getter_function`, sets
  42. which function paleofetch will call display. Current available getter functions are
  43. * `get_title`: prints `host@user` like in a bash prompt. Host and user will be printed in color.
  44. * `get_bar`: Meant to be added after `get_title`, underlines the title
  45. * `get_os`: Prints your operating system (including distrobution)
  46. * `get_host`: Prints the model of computer
  47. * `get_kernel`: Prints the version of the linux kernel
  48. * `get_uptime`: Shows how long linux has been running
  49. * `get_packages`: Shows how many packages you have installed. Currently only works for pacman.
  50. * `get_shell`: Shows which shell you are using
  51. * `get_resolution`: Prints your screen resolution
  52. * `get_terminal`: Prints the name of your current terminal
  53. * `get_cpu`: Prints the name of your CPU, number of cores, and maximum frequency
  54. * `get_gpu1`, `get_gpu2`: Print the GPU on your system. If you don't have both integrated graphics and an external GPU, `get_gpu2` will likely be blank
  55. * `get_gpu`: (Tries to) print your current GPU
  56. * `get_colors1`, `get_colors2`: Prints the colors of your terminal
  57. To include a blank line between entries, put `SPACER \` between the two lines
  58. you want to separate.
  59. The booleans in `CONFIG` tell paleofetch whether you want to cache an entry.
  60. When cached, paleofetch will save the value and not recompute it whenever you run paleofetch
  61. (unless you specify the `--recache` option).
  62. The CPU and GPU name can be configured as well. This is done under the CPU_CONFIG and GPU_CONFIG section
  63. in the config.h file. Two macros are provided to customize and tidy up the model names:
  64. * `REMOVE(string)`: removes the first occurence of `string`
  65. * `REPLACE(string1, string2)`: replaces the first occurence of `string1` with `string2`
  66. Don't forget to run paleofetch with the --recache flag after compiling it with your new
  67. configuration, otherwise it will still show the old name for already cached entries.
  68. FAQ
  69. ---
  70. Q: Do you really run neofetch every time you open a terminal?
  71. A: Yes, I like the way it looks and like that it causes my prompt to start midway
  72. down the screen. I do acknowledge that the information it presents is not actually useful.