I’ve been a Fedora user for quite some time now, but I’ve faced a few issues wrt mounting disks at boot, so I made the switch to Bazzite which has been nearly smooth so far: No need to manually install Steam and Nvidia drivers being a massive positive.
Why nearly? Because I also spend ~40% of my time in the terminal. Terminal experience in Fedora was pretty smooth, autocompletions worked flawlessly.
As an example, you would open your terminal at your home directory, and you wanted to install an rpm located in the Downloads folder, you could simply type sudo dnf install Downloads/ and then type the first few letters of your file and then press tab, it would automatically fill the file name for you.
But now that I have made the switch to Bazzite, the terminal experience feels a little odd. I’m in my home directory, and when I type rpm-ostree install Dow and then press tab, it does not even fill out the Downloads folder, let alone typing the name of the rpm file. This was very easily doable on Fedora.
I do have bash-completion package installed in Bazzite. What else am I missing here? Have you guys faced something similar too? If yes how did you solve it?
Hey,
I don’t think this is a bash-completion thing or anything outside from the rpm-ostree command just not doing the file completion part thats needed for the part of the command you want.
I use mostly fish myself but I did install the bash-bling from ujust and I installed bash-completion@2 from brew as well just to have as much fun bash things as possible. From my testing I was able to list out files/directories just fine using other command like:
ls, grep, cat
These were just some of the commands I ran without any issue. The only one that doesnt seem to work was the one you mentioned which is rpm-ostree. I also did this on fish as well to make sure if it was a bash related issue but its not as fish was also having a similar problem just with using rpm-ostree.
As a workaround to this, you could use something like fzf to help select a file/directory you need when this happens for specific commands (or any command for that matter):
# Add the following line to your .bashrc file (if its there, skip)
eval "$(fzf --bash)"
# run this to reload .bashrc file
exec bash
# run this as a test if you want and find any file you want to cat out
cat $(fzf)
rpm-ostree install $(fzf)
Its not perfect but its something that can get around those issues but also using fzf is awesome and powerful to use. I would recommend everyone should have it installed and setup for any shell (bash, fish, zsh).
I hope this helps.