Description: Based on both versions of the Debian-Slate theme from which I took inspiration (and much of the code) for this project.
I extrapolated different features, taken from one or the other version, trying to satisfy my personal tastes and trying to get a satisfying result that would fit my widesceen monitor (both original versions overwhelm the limits of my screen) and I was forced to prune some branches of the tree or, at least, to give a small thinning.
Obviously I adapted this theme on the distribution that I use (Fedora) and to which I wanted to pay tribute.
I wanted to add an alternative configuration file for those who don't use the proprietary nvidia drivers or who use a graphics card other than nvidia (on which the theme was originally based) that uses lm_sensors, in addition to detecting CPU temperature, to detect also GPU temperature.
Required packages: - conky - curl - lm_sensors
Installation instructions:
- Extract the compressed file and copy the configuration file in a path of your choice (e.g. on your home folder). - Edit the configuration file to set network interface to allow correct detection. - If you use the version that uses sensors to detect GPU temperature, edit the configuration file to set the correct parameter to monitor it appropriately. The parameter to be used can be obtained by using the sensors command in the terminal.
*** The theme appearance may change depending on the used video resolution. ***Last changelog:
2.1
wget command replacement with curl since, upon upgrading to Fedora 40, wget no longer returns the WAN IP value.
Hi, thanks for your feedback. This happens simply because your network interface has a different name (as it normally should be) than the default name on the configuration file.
You could simply replace the enp2s0 value with the correct name of your network, which you can know using commands such as 'ifconfig -a' or 'ip addr' from your terminal emulator.
Thanks, even though I'm starting to realize how complex it is to be able to adapt a theme to all contexts. I was forced, for example, to readapt the theme when I started using another desktop environment. In the end I believe that obviously nothing is impossible, but it is not within everyone's reach (including me) to create a theme that can adapt to any context. My hope is that there is someone who can improve, where improvable, the ideas that I propose.
Yes--I design themes to "fit" a number of different uses, but always note that the individual will have to customize the theme to "taste". I have always thought that it is a good thing for people to learn how to do things for themselves. That is the main reason I don't conform to things like Conky Manager---I think that someone needs to know how to do things the manual way.
Maybe 'cause I upload the configuration file as hidden (.conkyrc). Try to rename it as you want and copy it in a folder inside your ~/.conky folder.
Conky Manager surely makes things easier, but try to understand them to have a little mastery of the operating system and its aspects. Open your minds!
No, it is not because it is a hidden file. The problem is the syntax., the way of coding. If i add only the line "TEXT" before "conky.text=[[", it is visible but not working.
Presumably, conky manager is still based on the old conky code while, for some years now (since the release of version 1.10 of conky), the conky configuration files are based on lua.
Then, you should remove both strings that delimit the sections conky.config and conky.text (and relative brackets), as in this example https://is.gd/IluWR5
however I cannot guarantee the correct functioning of the theme using it through conky manager. I didn't change it thinking about that kind of use and I didn't have a chance to test it with conky manager.
Looks Good---I must admit I do my Conkys on a 34" widescreen...It's the one I use most of the time--satisfies wanting a terminal look for my conky. The "own_window_argb_value" & "own_window_color" are needed for use with Gnome3 in debian distros....I don't know what the update request for RPM-based distros need...As it is coded--it uses a dpkg code that is Debian-specific.
I use Mate-Compiz DE on Fedora and the theme works smootly without the need of the "own_window_argb_value" & "own_window_color" variables.
For the update info I've used dnf in sostitution of aptitude. The command dnf check-update work fine when there's updates (it shows the correct number of updates), but always returns 1 as a result when there are no updates.
Ratings & Comments
24 Comments
9 Magnificient theme, always wanted to make a detailed theme like this Nice
Thank you for the feedback, I really appreciate it.
9 The download/upload doesn't seem to work for me , otherwise great
Hi, thanks for your feedback. This happens simply because your network interface has a different name (as it normally should be) than the default name on the configuration file. You could simply replace the enp2s0 value with the correct name of your network, which you can know using commands such as 'ifconfig -a' or 'ip addr' from your terminal emulator.
Thank you! fixed it
10 10 the bestSimple clean and easy to edit. Thank you!
Thank you for the comment.
10 10 the best
thanks
Looking good!! Glad to see you've run with it a bit more.
Thanks, even though I'm starting to realize how complex it is to be able to adapt a theme to all contexts. I was forced, for example, to readapt the theme when I started using another desktop environment. In the end I believe that obviously nothing is impossible, but it is not within everyone's reach (including me) to create a theme that can adapt to any context. My hope is that there is someone who can improve, where improvable, the ideas that I propose.
Yes--I design themes to "fit" a number of different uses, but always note that the individual will have to customize the theme to "taste". I have always thought that it is a good thing for people to learn how to do things for themselves. That is the main reason I don't conform to things like Conky Manager---I think that someone needs to know how to do things the manual way.
I completely agree with you.
Is this only for fedora? Tried on Manjaro Budgie. Copiend the extracted folder on .conky but is not displayed on Conky Manager.
Maybe 'cause I upload the configuration file as hidden (.conkyrc). Try to rename it as you want and copy it in a folder inside your ~/.conky folder. Conky Manager surely makes things easier, but try to understand them to have a little mastery of the operating system and its aspects. Open your minds!
No, it is not because it is a hidden file. The problem is the syntax., the way of coding. If i add only the line "TEXT" before "conky.text=[[", it is visible but not working.
Presumably, conky manager is still based on the old conky code while, for some years now (since the release of version 1.10 of conky), the conky configuration files are based on lua. Then, you should remove both strings that delimit the sections conky.config and conky.text (and relative brackets), as in this example https://is.gd/IluWR5
however I cannot guarantee the correct functioning of the theme using it through conky manager. I didn't change it thinking about that kind of use and I didn't have a chance to test it with conky manager.
${alignr}${offset -6}updates < ${execi 360 aptitude search "~U" | wc -l | tail} > ─┘ try doing execi 360 rpm search instead.....not sure if that would work, I'm not good in low-level rpm commands.
9 +Looks Good!!
Looks Good---I must admit I do my Conkys on a 34" widescreen...It's the one I use most of the time--satisfies wanting a terminal look for my conky. The "own_window_argb_value" & "own_window_color" are needed for use with Gnome3 in debian distros....I don't know what the update request for RPM-based distros need...As it is coded--it uses a dpkg code that is Debian-specific.
I use Mate-Compiz DE on Fedora and the theme works smootly without the need of the "own_window_argb_value" & "own_window_color" variables. For the update info I've used dnf in sostitution of aptitude. The command dnf check-update work fine when there's updates (it shows the correct number of updates), but always returns 1 as a result when there are no updates.
I think I solved it, it was enough to use the --quite option The command dnf -q check-update seems to work much better.
Good to hear it.....have fun with it.