bash: bleopt/check:import_path: No such file or directory

[Freed-Wu]

bleopt import_path="${XDG_DATA_HOME:-$HOME/.local/share}/blesh/local:/usr/share/blesh/contrib"

It will give me:

bash: bleopt/check:import_path: No such file or directory

What happened?

[akinomyoga]

One possibility is that you use an old version of ble.sh with the POSIX mode of the unreleased Bash 5.3. What is the output of the following command?

$ echo "$SHELLOPTS"
$ (set +o posix; ble/widget/display-shell-version)

[akinomyoga]

Could you answer the questions?

[Freed-Wu]

Oh, sorry! After removing declare, everything works normally.

[akinomyoga]

Oh, I have an function declare to declare -f function_name | bat -pplbash.

declare is one of the basic builtin commands of Bash that constitutes the Bash language. If you change the meaning of the declare builtin, it means you effectively define a language different from the Bash language. Then, you cannot expect any "Bash" scripts and functions to work properly.

Is it because ble.sh don't allow it?

Actually, ble.sh allows users to override the declare command, (or otherwise, ble.sh wouldn't have worked in the first place). However, ble.sh still runs the user commands (i.e. the commands that the user inputs and executes through the command line) with the custom declare command, so the command bleopt executed from the command line is processed using the custom declare that you define.

[akinomyoga]

Oh, sorry! After removing declare, everything works normally.

OK, I'll summarize the problem and solution to this discussion in an independent reply.

[akinomyoga]

@Freed-Wu I made #465 (comment) so that you can mark it as an "answer" for this Q&A.

[akinomyoga]

This is the summary.

If one expects the commands executed through the command line to work properly, one shouldn't override the builtin commands of Bash to have a different meaning. In the reported case, the declare builtin was overridden. If one wants to make shell functions using the builtin work properly, one needs to unset the overriding functions/aliases/etc. and recover the original builtins.

Note: Even if you try to override builtins without changing their behavior, it is impossible to emulate the behavior of builtin, eval, declare, type, local, unset, exec, return, break, continue, trap, etc. Their behavior changes if they are called inside a shell function indirectly.