That must be it cause all my env variable are working…
Switched to git! Thank you!
That must be it cause all my env variable are working…
Switched to git! Thank you!
Any problem's guys? Did another metal install went well!
( I need something to go wrong! Please 
 
. Must make it better...must make it better....)
I burnt an ISO last night, need to apply it I guess and see what I can see. Always something to do though...today I need to get a new tire mounted.
(I'll add to this...because I need to reboot a time or two to test things I've noticed)
Ok, pretty much all the environment stuff should be moved into /etc/environment.
That way all shells benefit, not just those that actually use .profile.  Shell profiles are for shell specific stuff, not the kitchen sink (opinion).
(please note I abhor fish, but that's neither here nor there and shouldn't make any difference, some people abhor 'vi' 
 )
I think the parse errors in .profile are in works (from above).
A nit pick, but gonna mention, as presented now, garuda-welcome runs every time for me (until I comment it out of autostarted_application). Wouldn't it be nice if it actually obeyed the being unchecked to start every time?
Also that neofetch/paleofetch has crept back in there (thus smashing sway every time I launched a shell) on the fish shell.   Yet another reason to not use fish, eh ? 
Also, why are you (kept forgetting to ask this) hard coding which shell alacritty will use? (darn fish yet again)  I think it's absolutely imperative that you honor the users wish of which shell to use...don't hard code it let it default to whatever the user is using.  Do you have stock in 'fish' ? 
This is an 'I don't know what to do', but as you may recall, I accepted the challenge of switching from firefox to librewolf here...so this is fresh on my mind. As you're undoubtedly aware, cookies are almost an integral part of many websites...evil or not. I think (whether it makes it in here or not), some sticky'd forum post about how to deal with cookies in librewolf (there isn't much on the web really) to make some particularly important sites retain cookies (oh, and there may be a bug in librewolf in retaining cookies, even when you set policies) is required. I use bitwarden myself, so autologin into sites isn't too bad, but when you have to continue to login every page you switch (sites dependent upon cookies) or you have to reauthenticate each login with an authenticator or SMS code...umm yeah...that's maybe more than most people are gonna want to do. An alternative is to pre-load firefox on the iso also? Just thinking about user reaction...don't want them to say it's broken (it's not..just they won't know what/why/how). You may say, but they can load firefox themselves (and this is true..but the users that know that aren't the ones I'm thinking of).
Oh, and never let it be said, that I don't speak my mind 
  But I'm trying to be helpful.
alacritty is needed for all Garuda programmes.
“neofetch/paleofetch”
Can also be started with zsh/bash if the developer so wishes.
This has nothing to do with fish.
 ![]()
Like always, maintain a DE, we need help from experienced users. ![]()
SGS, I think translate and my simulflow babbling got you again.
I am not saying remove alacritty, just don't hardcode it's shell to /bin/fish.
and
If paleo/neo fetch results in sway abending when you launch a terminal, it really really needs to go.
My goal in my babbling is to try to think like someone who doesn't know how to add/remove/modify or isn't comfortable with it. With having an environment that they won't immediately ditch and run away.
The developer (or originator) can do what they wish, I am offering my thoughts and opinions. Not telling you guys what to do.
That is in every edition. User can always change…
Yes! I didn’t find a way to do it! I’m not sure how the apps are actually autostarted is it using XDG and dex? XDG Autostart - ArchWiki
Hmmm…Garuda all about librewolf I guess but I get your point. It doesnt matter really on the live iso and after install the setup assistant runs so they can install whatever browser they want.
The problem does not happen with neofetch for me. Only palofetch and only on the very first boot.
Thank You a lot btw! Your always helpful dbarren!
I know from i3wm you must comment out in ~/.config/i3/config
#exec --no-startup-id garuda-welcome
so in KDE/Sway/BSPWM/…/ maybe in autostart/config settings too?
There may not be a good way (garuda-welcome) really. So..something to think about methodologies. Only thing I can think is something silly like (sed s/exec garuda-welcome//), but that would require some code change in the application itself to trigger that and doesn't allow for setting it to autorun again if they change mind.
Oh, good point, I forgot the setup assistant (since I don't run it) can do that. Ok, so out of scope here, but still would be an excellent idea on the forum (anyone think so?) (Librewolf tips)
Ok, gonna really go out on the limb here (SGS don't read this, because you'll go ballistic..stop right now..I mean it..I warned you.) and say that the Garuda config for alacritty should not contain a hard-coded shell value, not without a really really good reason. If the user chooses to change his shell, he shouldn't have to run down 20 places to change it (yes, exaggeration..but the point).
I really (maybe just me and no one else thinks people that are scared of editors and shells are likely to try it) would like to make it newbie friendly. Most users are scared of tiling window managers (I was one till about 1.5 or 2 years ago) anyway. I think there's potential with nwg's pretty utilities to maybe entice some users into giving it a shot.
Even if it wasnt hardcoded into alacritty, alacritty would still use fish. Cause the way garuda is installed sets fish as the default shell.By showing the shell option in the config then maybe it is easier for the user. Rather than all the chshshshshhs thing.
But it wouldn't use fish if you changed your shell (if it weren't hard coded).  General principle, put information in only one place.
Ok, I'll shutup.
Yeh I guess so. Fish isn't that bad. It makes it easier for new users...or not??
It would be a bit weird for just sway to use bash...people are expecting a fancy shell in garuda.
I get your point but we will anger SGS if we talk more 
. Just kidding SGS we know you never get angry!
No no, I'm not saying change the default either.  Set their shell to fish, just don't make it harder to 'unfish' 
Everyone has biases and preferences, and I have absolutely no idea where the majority lies on shell choice (if most even care?).
XFCE uses bash.
Seems like you still really don’t know me.
![]()
Is it hard to unfish? I move that part of the config to top of the alacritty.yml? Make big letters SHELL!!!!
Would that solve it @dbarron 

@SGS We're treating you as a revered elder, whom we're gently teasing. Yeah...that's it!
The age thing is about right. 
But, why does one even have to specify shell at all in the alacritty.yml?  Everyone has one...their own default.  Is there any reason at all ?  Please, if there is, I don't know.
As far as I know, it's just an override (of their default)..which is my objection.
I have a feeling that I'm of similar vintage to you. Like fine wines?