Config related changes?

[Jarvvski]

Hey there

Have there been any config related changes? I did an upgrade the other day - rebooted today, and realized my old i3 config within $HOME/.config/regolith/i3.config has effectively been wiped

[gardotd426]

What do you mean it's "effectively been wiped." Is it there or not?

And is ~/.config/regolith/i3.config a typo? Because that's not where it goes, it's ~/.config/regolith/i3/config.

I just checked and my ~/.config/regolith/i3/config is untouched, so I'm not really sure what exactly you're talking about, I definitely need some more information.

There hasn't even been a change to any of the packages involved with regolith's i3 components, because there are no more changes coming until Regolith 2.0 comes out sometime in April or May. The last update was to add a missing dependency or something like that. So there's no way anything should have touched your config file.

[Jarvvski]

Yeah, it was a typo

I was using ~/.config/regolith/i3/config

So, what happened was I have a script written up to pull my dots on a system restart. At work, I use an ubuntu machine using regolith. I'm not sure how, or why - but that has seemingly changed to i3.config within the config dir

When that pushed up to my dots, and then my home computer pulled it, it changed my manjaro install to using i3.config also

That doesn't seem to work here, and it reverted back to /etc/regolith/config

[gardotd426]

I can't reproduce on any Arch-based machine. I'm not sure what your script looks like, or your dotfiles (a link would be helpful), but I suggest trying to use the DE as intended and see if you have the same issues. If you don't, then the issue lies in your script. I'm happy to help you debug that, and if we find any instances where the Regolith DE port could be modified to better accommodate use-cases like yours, then I'm happy to oblige and make those modifications, assuming it doesn't require compromising anything that would cause this port to stray too far from upstream.

See, this is more or less the de facto (though not quite de jure, at least not yet) official Regolith Desktop Environment Arch Linux port. I have been added as an official member of the Regolith Linux Organization by Ken (the Regolith Linux creator and lead developer), and so I am now officially a part of Regolith Linux. I am free to editorialize the port when it comes to minor things, and obviously I am free (and encouraged) to make any modifications necessary to fix issues derived from differences between the way Ubuntu and Arch work, and I have been enlisted to help Ken make Regolith more distro-agnostic, but this isn't a fork, it's a port.

So, I can give the following recommendations:

• Try firing up the latest version of Regolith (the distro) in a VM and install it in said VM, and try to pull in your dotfiles, and see if the issue persists there.
• Try using my port on an Arch-based distro but without your script, just by copying your dotfiles, and see if the issue persists there.
• Provide your dotfiles and your script for me to look over and see where the issue might be, and I can try and either help you modify your script, or modify the port to better accommodate your use-case, or both.

But the thing is, even though I've provided some updates to the AUR pacakges in recent months, the actual relevant Regolith i3 packages I'm using haven't been updated in that time, so there haven't been any updates that would explain your issue.

If you're unwilling to do all of that, at least provide me with your script and a link to your dotfile repo (or at least some gists with your configs), and I'll happily take a look and see what I can do to help.