| Summary: | No support of fish shell in `kdevelop!` script | ||
|---|---|---|---|
| Product: | [Applications] kdevelop | Reporter: | Petrov Egor <dikey0ficial> |
| Component: | general | Assignee: | kdevelop-bugs-null |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | dikey0ficial, igorkuo |
| Priority: | NOR | ||
| Version First Reported In: | 5.11.230403 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Petrov Egor
2023-09-03 07:10:58 UTC
> Support of fish shell https://commits.kde.org/kdevelop/f3bde6dcd4767396b5fce7572be565f345adf271 added support for zsh relatively recently. If fish is similar enough to bash, you could easily add support for it too and create a merge request. > or at least not run `kdevelop!` script in unsupported shells Not running the `kdevelop!` script in unsupported shells would make KDevelop-specific functions defined in kdevplatform_shell_environment.sh unavailable. So this doesn't look like a viable general solution for me. > --- Comment #1 from Igor Kushnir <igorkuo@gmail.com> --- > > Support of fish shell > https://commits.kde.org/kdevelop/f3bde6dcd4767396b5fce7572be565f345adf271 added > support for zsh relatively recently. If fish is similar enough to bash, you > could easily add support for it too and create a merge request. However, it's not so similar; at least, fish isn't POSIX and has own syntax. > > or at least not run `kdevelop!` script in unsupported shells > Not running the `kdevelop!` script in unsupported shells would make > KDevelop-specific functions defined in kdevplatform_shell_environment.sh > unavailable. So this doesn't look like a viable general solution for me. I mean, adding an option to disable it in terminal pane would be enough, although it's not an ideal solution ;) (In reply to Petrov Egor from comment #2) > I mean, adding an option to disable it in terminal pane would be > enough, although it's not an ideal solution ;) If the path where `kdevelop!` is installed is not the first entry in $PATH, you can create a custom, possibly empty, `kdevelop!` script in a preceding path, e.g. ~/.local/bin/kdevelop!. This script should take precedence over the script provided by KDevelop. So, in this sense, the option you ask for already exists. The ideal solution is obvious: translate KDevelop's scripts into fish. But apparently no one priorities this solution highly enough to implement it. > If the path where `kdevelop!` is installed is not the first entry in $PATH, you > can create a custom, possibly empty, `kdevelop!` script in a preceding path, > e.g. ~/.local/bin/kdevelop!. This script should take precedence over the script > provided by KDevelop. So, in this sense, the option you ask for already exists. Just tried — that's works, thanks! But i believe that it should be only workaround, not a recommended way ;) By option i mean checkbox in KDevelop settings menu that sets should konsole load kdevelop! script or something else. > The ideal solution is obvious: translate KDevelop's scripts into fish. But > apparently no one priorities this solution highly enough to implement it. Okay. (In reply to Petrov Egor from comment #4) > By option i mean checkbox in KDevelop settings menu that sets should > konsole load kdevelop! script or something else. KDevelop developers have been wary of adding options useful to a small percentage of users. The configuration UI shouldn't be cluttered more than it already is. In this case a simple and effective workaround exists for the few users that might want it. So I don't think the proposed checkbox should be implemented. Okay, thanks for attention. |