|
6 | 6 | #include "cpuid.h" |
7 | 7 | #include "global.h" |
8 | 8 |
|
9 | | -static const char* VERSION = "0.64"; |
| 9 | +static const char* VERSION = "0.65"; |
10 | 10 |
|
11 | 11 | void print_help(char *argv[]) { |
12 | | - printf("Usage: %s [--version] [--help] [--levels] [--style fancy|retro|legacy] [--color 'R,G,B:R,G,B:R,G,B:R,G,B']\n\ |
| 12 | + printf("Usage: %s [--version] [--help] [--levels] [--style \"fancy\"|\"retro\"|\"legacy\"] [--color \"intel\"|\"amd\"|'R,G,B:R,G,B:R,G,B:R,G,B']\n\n\ |
13 | 13 | Options: \n\ |
14 | | - --color Set a custom color scheme. 4 colors must be specified in RGB with the format: R,G,B:R,G,B:...\n\ |
15 | | - These colors correspond to the ASCII art color (2 colors) and for the text colors (next 2)\n\ |
16 | | - Suggested color (Intel): --color 15,125,194:230,230,230:40,150,220:230,230,230\n\ |
17 | | - Suggested color (AMD): --color 250,250,250:0,154,102:250,250,250:0,154,102\n\ |
18 | | - --style Set the style of the ASCII art:\n\ |
19 | | - * fancy \n\ |
20 | | - * retro \n\ |
21 | | - * legacy \n\ |
22 | | - --help Prints this help and exit\n\ |
23 | | - --levels Prints CPU model and cpuid levels (debug purposes)\n\ |
24 | | - --verbose Prints extra information (if available) about how cpufetch tried fetching information\n\ |
25 | | - --version Prints cpufetch version and exit\n", |
| 14 | + --color Set the color scheme. By default, cpufetch uses the system color scheme. This option \n\ |
| 15 | + lets the user use different colors to print the CPU art: \n\ |
| 16 | + * \"intel\": Use to intel color scheme \n\ |
| 17 | + * \"amd\": Use amd default color scheme \n\ |
| 18 | + * custom: If color do not match \"intel\" or \"amd\", a custom scheme can be specified: \n\ |
| 19 | + 4 colors must be given in RGB with the format: R,G,B:R,G,B:... \n\ |
| 20 | + These colors correspond to CPU art color (2 colors) and for the text colors (following 2) \n\ |
| 21 | + For example: --color 239,90,45:210,200,200:100,200,45:0,200,200 \n\n\ |
| 22 | + --style Set the style of CPU art: \n\ |
| 23 | + * \"fancy\" (default style) \n\ |
| 24 | + * \"retro\" (old cpufetch style) \n\ |
| 25 | + * \"legacy\" \n\n\ |
| 26 | + --levels Prints CPU model and cpuid levels (debug purposes)\n\n\ |
| 27 | + --verbose Prints extra information (if available) about how cpufetch tried fetching information\n\n\ |
| 28 | + --help Prints this help and exit\n\n\ |
| 29 | + --version Prints cpufetch version and exit\n\n\ |
| 30 | + \n\ |
| 31 | +NOTES: \n\ |
| 32 | + - Bugs or improvements should be submitted to: github.com/Dr-Noob/cpufetch/issues \n\ |
| 33 | + - Peak performance information is NOT accurate. cpufetch computes peak performance using the max \n\ |
| 34 | + frequency. However, to properly compute peak performance, you need to know the frequency of the \n\ |
| 35 | + CPU running AVX code, which is not be fetched by cpufetch since it depends on each specific CPU. \n", |
26 | 36 | argv[0]); |
27 | 37 | } |
28 | 38 |
|
|
0 commit comments