Summary: | Yakuake's path searching algorithm has issues | ||
---|---|---|---|
Product: | [Applications] yakuake | Reporter: | yannl35133 |
Component: | general | Assignee: | Eike Hein <hein> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Manjaro | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
yannl35133
2020-11-01 12:02:43 UTC
After a bit of testing : - if another tab executes "opam --version" before the new version is installed, this other tab also won't notice the change - if another tab is merely created but doesn't interact with opam before the change, it does notice and more importantly : - it affects Konsole similarly Should I report against them? Wait, this issue also happens in GNOME Terminal. Is it some sort of intended behaviour of bash that I don't know? The terminal emulator is not responsible for launching the binaries from the PATH; that's done by the shell. A question then : Where should I file this bug? bash? If the PATH variable is setup correctly, and bash doesn't respect the ordering specified there, it would be a bash bug. If the PATH variable is setup wrongly, you would need to find out which component is responsible for setting it; it could be a distribution issue. I would recommend asking in a help forum first. I asked for help in the Manjaro Forum here : https://forum.manjaro.org/t/apparent-bug-with-path-in-bash/35076 |