I recently faced an issue with Fish shell for not having direct access to flatpak apps in the menu. It is termed a non-POSIX shell. Can someone tell me the difference between having the non-POSIX shell and a regular one?
I just want a good-looking shell with auto-completion features that makes my terminal experience easier and it should not cause any issues like as in fish.
I came up with these from the web
Please suggest me to pick the right one for my use case!
Did you try changing the shell to fish in the profile settings of konsole instead of for the user?
I think it’s under the general section when you’re editing a profile. Should be a command text box, you’d enter the path to fish there.
Personally I use zsh.
I tried it yesterday when I broke it does nothing.
Is it neccessary to install Nerd Fonts which are 2.2GiB??
No it is not.
Did you try what the Manual proposes:
To make fish your default shell:
/usr/local/bin/fish to /etc/shells .chsh -s /usr/local/bin/fish .For detailed instructions see Switching to fish.
I do not want to be in fish anymore as it clashes with my flapaks being displayed on menu
You can use fish without having it be your default shell.
Just set it to be the shell program in konsole. This won’t have any impact on flatpaks.
But your system was broken at the time. Are you fish was even installed when you tried that?
Oh! okay. I get it.
I use fish shell and my Flatpaks run fine.
The issue isn’t with running flatpaks. It is with them being added to the menu in certain DEs.
The code that does that by default is in a shell script in /etc/profile.d which fish doesn’t source.
If you use one of those DEs, you need to either not have fish as your default shell or replicate those changes in fish.
In general, I, personally think it is bad idea to set a non-POSIX compliant shell as your default shell. flatpak isn’t the only piece of software that has this problem. By setting a POSIX compliant shell as your default and then setting fish as the default shell in your terminal, you get all the benefits of fish without the side-effects.
Yeah, but wouldn’t you just copy those scripts to /etc/fish/conf.d or reflink them there?
I have installed flatpaks both before and after starting to use fish as a shell, and they all work, have Icons that you click to start, etc… If they aren’t working for @hemanthch then I am suggesting something else is the underlying issue.
You could, after verifying they worked with fish as-is. If not, they may need modification.
Are you also using plasma like he is?
To be clear, I never stated “It is impossible to get this to work with fish as your default shell”. My opinion is if you want things to “just work” without intervention, you are better off having your default shell be POSIX compliant even if you use a different shell for your interactive sessions.
To be clear, I never had to do anything other than install fish as my shell to “get it to work”. It works, at least out of the box on Gnome, I don’t use KDE, and haven’t since well a really long time, so I cannot speak to that.
Do you know powerline?
You can use it wih a lot of different shells (bash, zsh, fish, …)
Here are some related articles worth a read:
The flatpak package includes this script as `/etc/profile.d/flatpak.sh:
if command -v flatpak > /dev/null; then
# set XDG_DATA_DIRS to include Flatpak installations
new_dirs=$(
(
unset G_MESSAGES_DEBUG
echo "${XDG_DATA_HOME:-"$HOME/.local/share"}/flatpak"
GIO_USE_VFS=local flatpak --installations
) | (
new_dirs=
while read -r install_path
do
share_path=$install_path/exports/share
case ":$XDG_DATA_DIRS:" in
(*":$share_path:"*) :;;
(*":$share_path/:"*) :;;
(*) new_dirs=${new_dirs:+${new_dirs}:}$share_path;;
esac
done
echo "$new_dirs"
)
)
export XDG_DATA_DIRS
XDG_DATA_DIRS="${new_dirs:+${new_dirs}:}${XDG_DATA_DIRS:-/usr/local/share:/usr/share}"
fi
This is needed on plasma for flatpaks to be available in the menu. If it isn’t needed on gnome, that is fine but that doesn’t really relate to the OP’s issue.
Fish uses XDG_DATA_DIRS just like any other shell, if Plasma is having difficulty with flatpaks and fish, then I am saying it is an issue with plasma, not fish since I didn’t have to do anything special to get it up and running in Gnome, and I would assume if I spin up a KDE VM with Plasma it would work fine too.
But it doesn’t source the scripts in /etc/profile.d so it doesn’t get those changes…
If you add those paths to your XDG_DATA_DIRS some other way in fish it would probably work just fine.
I suppose, technically, it is an issue with flatpak. Also, it is apparently one they fixed a few days ago:
https://github.com/flatpak/flatpak/issues/3109
Finally liked the ZSH and the powerline10k theme!
Looking forward for a new learning curve with ZSH as it seems to have a lot to configure.
zsh Rocks for sure and with Powerline you can have a real cool terminal experience! Glad you like it. Could you mark that comment that led you to try out Powerline as the solution please?