Summary: | ./kdesrc-build --initial-setup adds invalid `complete` command to .zshrc | ||
---|---|---|---|
Product: | [Developer tools] kdesrc-build | Reporter: | skierpage <info> |
Component: | setup wizard | Assignee: | Xynt Xo <xyntxo> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ashark, bjdm.92, smit17xp, snehitsah, xyntxo |
Priority: | NOR | ||
Version First Reported In: | Git | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
skierpage
2021-06-13 02:52:30 UTC
Can reproduce this bug on Arch Linux using the same repro steps Operating System: Arch Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.2 Kernel Version: 5.14.11-arch1-1 (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 1700 Eight-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: Radeon RX 580 Series Adding `autoload -U +X bashcompinit && bashcompinit` before the call to `complete` removed the error for me. I have added a tiny note on wiki page : https://community.kde.org/index.php?title=Get_Involved/development&diff=prev&oldid=93638 Confirming. The completion function is bash-only, and we're putting it into .zshrc. zsh does have a bash compatibility plugin (`bashcompinit`), but 1) this is not loaded by default on many systems (including Neon), and 2) loading the bash layer also requires loading a broad set of zsh completions which the user might not want. It seems to me that the correct path forward is to: 1) Test for the presence of the bash compatibility layer, and if it is not present then don't put bash code into .zshrc 2) Create a zsh-specific completion function I'll create a merge request for #1 and look into #2. A possibly relevant merge request was started @ https://invent.kde.org/sdk/kdesrc-build/-/merge_requests/172 FYI, there is another MR open for a zsh completion function: https://invent.kde.org/sdk/kdesrc-build/-/merge_requests/165 This is not installed now. |