neofetch LinuxBBQ

User avatar
catfood
Bad Advice Dog
Posts: 146
Joined: Tue Oct 04, 2016 1:25 am
Location: F google
Contact:

neofetch LinuxBBQ

Unread post by catfood » Tue Jul 28, 2020 5:56 am

So this is 6.5hrs of learning ASCII art by guessing, lol.
Neofetch DAMNIT WHERE'S ORANGE.png
I need help figuring out how to get Orange and LT Brown colors in the neofetch file. I also don't have any idea how to customize ' info "OS" distro ' to just say LinuxBBQ, vs pulling in the running distro (Show's Gnu Linux / Debian Buster/Sid ... on my BBQ comp, lazy Xubu here). I currently have config.conf forcing my LinuxBBQ ASCII as well.

Currently:
from near the end of neofetch file. (link included so someone can make more sense of how it pulls colors. Looked like it picked 1-8 or 1-16 off wm or de settings, but I don't really know what I'm reading here....)
https://github.com/dylanaraps/neofetch/ ... r/neofetch

Code: Select all

	"LinuxBBQ"*)
			set_colors 16 0 99 1 3 7
			read -rd '' ascii_data <<'EOF'
			...bunch of ascii lines...
			...
EOF
		;;
. = 16 Black
+ = 0 (grey, placeholder, WRONG, should be a light brown)
@ = 99 (purple, placeholder, WRONG, needs to be regular orange)
# = 1 (peach, closest to light orange I got)
$ = 3 Yellow
% = 7 White

I tried 1-99 just to see, even though again, it appears like Hexadecimal?
-#s nor Letters work
Switching terminal programs doesn't change colors
Changing XFCE4 themes didn't change colors
Hex Color Codes don't work either. (Though they are, as picked from the BBQ logo:
. = #040400
+ = #7B5538
@ = #EB5504
# = #F08720
$ = #F6D631
% = #F2F3EF
If anyone knows how to force these into neofetch to get exact logo colors for everything, I'd like that a lot better!)
cutuncut S(c) paintbynumbers.png

Once I get colors sorted, I can try a few more sizes so it's not so tall; find best size that doesn't blur it too bad... (Most circular distros were 20x40 pixel, this I ran at 40x40 for 1st try here)
After we make it right/better/perfect, I will correct my code and post it and a How-To on here.
Can maybe try to make a "Small" option like some distro's had too, but that might be horrible attempts at hand drawing tiny burning penguin in txt vs stealing basic .xpm template from GIMP (No promises here)

With Bacon's approval/permission, I'd like to submit FINAL Product to neofetch. We seem to be one of the only "distro's" not represented in there :/
I figured add a line like:
#Code submitted by the MEAT Collective
for everyone else's effort who always has to fix my complete lack of understanding :D
Thank You!
(I remember when debian "non-gui" installer scared me. #never-forget)

User avatar
ivanovnegro
Minister of Truth
Posts: 5059
Joined: Wed Oct 17, 2012 11:12 pm

Re: neofetch LinuxBBQ

Unread post by ivanovnegro » Tue Jul 28, 2020 12:47 pm

catfood wrote:
Tue Jul 28, 2020 5:56 am
We seem to be one of the only "distro's" not represented in there :/
That is probably because we use mostly env-info:

https://github.com/machinebacon/linuxbb ... r/env-info

and no more bloat. :) But of course feel free to add the grill to Neofetch.

pidsley
Hermit
Posts: 2513
Joined: Wed Oct 17, 2012 12:31 pm

Re: neofetch LinuxBBQ

Unread post by pidsley » Tue Jul 28, 2020 11:37 pm

Can't help with the colors, but what do you get when you try this in a terminal?

Code: Select all

cat /etc/os-release
Most utilities use /etc/os-release to determine the running distro. From what I can tell in the incredibly complex neofetch code, it uses this and then does some fancy crap to make what it thinks is a "better" distro name. But it could be doing something completely different.
"The prettier the user interface, and the fewer odd replies the system allows you to make, the dumber you once appeared in the mind of the designer." -- Ellen Ullman

User avatar
catfood
Bad Advice Dog
Posts: 146
Joined: Tue Oct 04, 2016 1:25 am
Location: F google
Contact:

Re: neofetch LinuxBBQ

Unread post by catfood » Wed Jul 29, 2020 12:42 am

Colors(edit: see below) When image is perfected, I could just let neofetch's creator plug my art into his own code better than my guesses...
I'll gladly share finished code here, but wanted Bacon's approval on final art b4 pushing it to any 3rd party. It's not my "branding/logo", so want to respect the authors wishes despite open-source...
I wanted to learn some ASCII art for one of my Wish-a-Spin ideas anyways, so figured why not start with something more universal here and try to contribute the BBQ logo in ascii for others here to use however they please.
(Still wanted to make our presence know on neofetch too though, lol). Once I got this all sorted out, since it seems like a lot of lines likely have to be manual and not distro-detecting, thought about a "neofetch-lite" version to share here; might as well cut out the other 5000 lines we won't be using.


My OS release on the bbq is running BBQ Break. I had to manually force the ascii art in neofetch by changing one line from ascii_distro=auto to ascii_distro=LinuxBBQ (so it found my LinuxBBQ entry in the list of ascii art.) I read through all the code, but not knowing what I'm looking at per say, I didn't see a line like OS_distro=auto or OS_distro= cat proc os/lsb release etc. that I could also just manually type BBQ in place of that worked. The few unhashed lines with OS: distro, I tried playing around with, but it just always broke that line and wouldn't display OS line if anything was changed.

I kinda want to find that, cause I'm sure they won't wanna bloat neofetch further with every BBQ spin under the sun, and each one is likely to show different os-release.(For the art, the code #notes tell you to force Xubu, Ubu-Gnome, Lubu, etc directly into that line for yourself if you have an Ubu spin anyways. Assume we'd fall under similar category for OS: , ie manually change Debian to "LinuxBBQ _ _" somewhere in the code).

Code: Select all

 OS: LinuxBBQ Sid.0.Forever NoTermSupport

They do have some other If variable sections I could mimic though when I know where to put it; like case$os if [ os-release = LinuxBBQ*] then printf=("OS\: LinuxBBQ") or something. Just not sure where it should go. One example I think is forcing a truncated display output like that:

Code: Select all

 case $os in
        Linux|BSD|MINIX)
            if [[ -f /bedrock/etc/bedrock-release && $PATH == */bedrock/cross/* ]]; then
                case $distro_shorthand in
                    on|tiny) distro="Bedrock Linux" ;;
                    *) distro=$(< /bedrock/etc/bedrock-release)
                esac
Bacon already has it figured out somehow in env-info:

Code: Select all

print-distro() {
    [[ -e /etc/os-release ]] && source /etc/os-release
    if [ -n "$PRETTY_NAME" ]; then
        color-echo 'OS' "$PRETTY_NAME"
    else
        color-echo 'OS' "not found"
    fi
}
, as all his Releases scrots say "OS: LinuxBBQ ______" . I have no idea how $PRETTY_NAME" pulls that info though.



It looks like it's written in C? Since everything I seem to want to customize has also been in C, I'm starting to study it and watch online classes, so maybe understand how it works better in the near future, then be able to dissect it myself further. Wanted to ask here though cause you guys seem to know everything quickly. Takes Bacon 30 seconds to pull answers out of a hat for me time and time again, lol. You've done the same as well with my 2wm circus.
Last edited by catfood on Wed Jul 29, 2020 2:04 am, edited 3 times in total.
Thank You!
(I remember when debian "non-gui" installer scared me. #never-forget)

User avatar
catfood
Bad Advice Dog
Posts: 146
Joined: Tue Oct 04, 2016 1:25 am
Location: F google
Contact:

Re: neofetch LinuxBBQ

Unread post by catfood » Wed Jul 29, 2020 1:23 am

ivanovnegro wrote:
Tue Jul 28, 2020 12:47 pm
That is probably because we use mostly env-info:
Speaking of, I think you(and getting another copy of Adipositas) just figured colors out for me, lol.
env-info color names come from where.png
env-info color names come from where.png (64.77 KiB) Viewed 258 times
dkeger and .Xresources_colors

I didn't notice it in neofetch because it just has the two color bars. Forgot env-info showing the names of "colors it's planning on using by name" displayed in the "color you have set for them" ie:
black red green yellow blue magenta cyan white
Ironically, may even be pulled in that order for the ASCII color slots :D


I'll be back with an update in a day or two. Gonna make rnd2 20x40pix ascii, send it to my bbq laptop, then run through my dekeger options and see how it changes. Then just have to see if dkeger can overwrite neofetch easily(or which has final say in terminal display .Xresources or neo...).
Thank You!
(I remember when debian "non-gui" installer scared me. #never-forget)

User avatar
catfood
Bad Advice Dog
Posts: 146
Joined: Tue Oct 04, 2016 1:25 am
Location: F google
Contact:

Re: neofetch LinuxBBQ

Unread post by catfood » Thu Jul 30, 2020 3:33 am

bbq20x40.png
20x40 (size right, colors incomplete.)

dkeger/xcolor_resources will change neofetch and could be made correct, but unless you want Orange/Red/Yellow/B&W for all your terminal colors, need a better solution.

Attatched:
-ascii art in .txt format with c${#} additions for neofetch, (but can be used whereever you like with a few minor adjustments I'm sure. Correct HexColors #'d
out at top of file.)
-20x40 bbq logo .xpm (had to upload as a png here, but can be saved back to .xpm with GIMP if you want to see the letter/symbol structures when it's auto-converted to ascii art...)

Going to email neofetch creators to figure out a better way to get hex colors in only for the ascii, and without ruing other terminal themes.
Will ask them, but may need help here too mixing BBQ "Pretty_Name" spin finder code with whatever auto-distro naming section specifically I get back from them. More later...
Attachments
bbq_20x40(,xpm).png
bbq_20x40(,xpm).png (617 Bytes) Viewed 206 times
bbq_20x40asciiartDONE.txt
(1.65 KiB) Downloaded 10 times
Thank You!
(I remember when debian "non-gui" installer scared me. #never-forget)

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: neofetch LinuxBBQ

Unread post by machinebacon » Wed Aug 05, 2020 10:44 pm

catfood wrote:
Tue Jul 28, 2020 5:56 am

With Bacon's approval/permission, I'd like to submit FINAL Product to neofetch. We seem to be one of the only "distro's" not represented in there :/
I figured add a line like:
#Code submitted by the MEAT Collective
for everyone else's effort who always has to fix my complete lack of understanding :D
[APPROVED]

sorry for the slow response, just do it :) thanks for your efforts, it looks good (though as Comrade pidsley has stated, we use his env-info script, if ever. I don't usually need to remind myself what OS I'm using lol)
..gnutella..

machinebacon
Baconator
Posts: 10253
Joined: Thu Sep 16, 2010 11:03 am
Location: Pfälzerwald
Contact:

Re: neofetch LinuxBBQ

Unread post by machinebacon » Wed Aug 05, 2020 10:47 pm

btw trouble is that every dist-upgrade that pulls in a new systemd or lsb-release will overwrite the edits in /etc/os-release and /usr/lib/os-release

I'm okay if it's shown as Debian sid, after all it is nothing else than a frankenstein siduction :D
..gnutella..

User avatar
catfood
Bad Advice Dog
Posts: 146
Joined: Tue Oct 04, 2016 1:25 am
Location: F google
Contact:

Re: neofetch LinuxBBQ

Unread post by catfood » Thu Aug 06, 2020 12:46 am

Thanks Bacon.

I made a vague support submit to neofetch git help, but no ascii code was shared until i got your approval!
They should help me fix colors with accurate hex code at some point.

Next question here:

How exactly does "Pretty-Name" pull spins by "name" in env-info?


Regardless every spin burned cd I play with, env-info always works. So even when you guys make new spins/base updates,:
(good to know it's Pidsley's scrip for env-info now, so know who to ask further)
I'm guessing Pidsley does not "package-maintain" env-info every time a new spin comes out... So wondering how it pulls "distro names" out of each releases code...
If the releases have "Pretty-name" as some sort of internal nomenclature, then "pretty_name" might work as default, just shoved into neofetch code?

It does show "deb Sid" by default already. With minor manual tweaks, it can force show Lubuntu, Xubu, etc. I'm asking them, and still staring at code I don't get, but eventually, instead of "Force show Xubu", something like if=linuxbbq, then search /etc/lsb****pretyyname?

but I just think a bunch more burning penguins on google images search for neofetch is funny, and if each shows every spin you guys make, it's like ants taking over a picnic :D
Thank You!
(I remember when debian "non-gui" installer scared me. #never-forget)

pidsley
Hermit
Posts: 2513
Joined: Wed Oct 17, 2012 12:31 pm

Re: neofetch LinuxBBQ

Unread post by pidsley » Thu Aug 06, 2020 2:09 am

catfood wrote:(good to know it's Pidsley's scrip for env-info now, so know who to ask further)
NO NO NO NO -- While env-info was originally my script, I closed my github repo long ago and no longer maintain the script for anything but my own use.

I never offered to suport this script. If you look at the code, you should see this at the top:

Code: Select all

# this script is provided with NO GUARANTEE and NO SUPPORT 
# if it breaks or does not do what you want, FIX IT YOURSELF
Having said that, I will tell you that PRETTY_NAME is defined in /etc/os-release, and env-info uses the "source" command to make that variable available in the script (you even quoted that code in one of your earlier posts). Any bash reference should tell you what the "source" command does. As bacon says, if os-release is updated as part of a dist-upgrade, env-info will show whatever is in the file. This is not a bug.

env-info is a very simple bash script. It does not do a lot of error checking for edge cases, and any bash "expert" will tell you there are "better" ways to do many of the things it does. Even so, one way for you to learn more bash would be to go through the script and look up things you don't understand.

Some bash references and tutorials: https://wiki.archlinux.org/index.php/Bash#Tutorials
"The prettier the user interface, and the fewer odd replies the system allows you to make, the dumber you once appeared in the mind of the designer." -- Ellen Ullman

User avatar
catfood
Bad Advice Dog
Posts: 146
Joined: Tue Oct 04, 2016 1:25 am
Location: F google
Contact:

Re: neofetch LinuxBBQ

Unread post by catfood » Sun Aug 09, 2020 5:44 pm

I don't expect you to support or maintain it, but if I get really stuck playing around with it, I might ask more...
I will read up, study, test, break it, and repeat on my own first to get the dumb potential questions out of the way. I'm starting to learn that etiquette at least(slowly but... appreciate everyone's patience).

I'm also starting to look at how I could just shove ascii bbq art into env-info. Seems like that would be much easier to just put the one part I like from neofetch into a way more understandable small code....

A new Spork(bloat fork):
environeo-info :D
Thank You!
(I remember when debian "non-gui" installer scared me. #never-forget)

Post Reply