-
-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"compgen: command not found" while typing #399
Comments
I'm not sure what is happening there either. At least, I've never hit this behavior in my environment. I think this is related to completions because
$ bleopt complete_auto_complete=
$ ble/widget/display-shell-version I have also other questions, but I'll ask them after checking an answer to Q1. |
I've found something similar at NixOS/nixpkgs#157882, though it seems to be reported against Zsh. |
$ complete -p git
$ type compgen
$ ble/function#advice before git 'echo "${ADVICE_WORDS[@]}" >> ~/debug.txt'
$ git annex .... # <-- here, please input something and try to reproduce the error messages
$ echo "$SHELL"
$ export SHELL=$BASH
$ git annex .l.. # <-- see if the error messages appear
$ getent passwd | awk -F : -v UID="$UID" '$3==UID {print $7}'
|
$ bleopt complete_auto_complete=
$ git annex ... [press TAB here]
$ ble/function#push enable true
$ git annex ... # <-- see if the error messages reproduce |
This seems to be related: dhall-lang/dhall-haskell#2362 Hmm, the discussion there reminds me of another discussion started at #169 (comment).
$ echo "$BASH"
$ readlink /proc/$$/exe
$ BASH=$(readlink /proc/$$/exe)
$ git annex ... # <-- does the problem reproduce here?
$ type -a bash |
Fun thing is: I cannot reproduce the issue right now, so I cannot answer all your questions right now... I'll answer everything else as good as I can:
Cannot answer right now, because I cannot reproduce.
Cannot answer right now, because I cannot reproduce.
Not applicable,
Not applicable, login shell is bash. |
I see. Thank you for all your answers. If this issue is related to dhall-lang/dhall-haskell#2362 or #169 (comment) mentioned above, maybe the problem only arises in |
@matthiasbeyer Have you faced the same problem after that? |
Yes, and it seems to be a |
Thank you for the information. I'm wondering what would be the solution for this issue. I here assume that the root cause is the same as the problem mentioned in #169 (comment). If that is the case, as I mentioned there, I'd like to request If there is a strong reason that the current behavior of nix shell cannot be changed, I might need to think about a workaround. In that case, could you check the results of Q8, Q8a, and Q9 inside |
I finally came around to answer the questions you mentioned: Q8: $ echo "$BASH"
/nix/store/x88ivkf7rmrhd5x3cvyv5vh3zqqdnhsk-bash-interactive-5.2-p15/bin/bash
$ readlink /proc/$$/exe
/nix/store/x88ivkf7rmrhd5x3cvyv5vh3zqqdnhsk-bash-interactive-5.2-p15/bin/bash Q8a: not applicable Q9: $ type -a bash
bash ist /nix/store/q1c2flcykgr4wwg5a6h450hxbk4ch589-bash-5.2-p15/bin/bash
bash ist /run/current-system/sw/bin/bash |
Thanks!
$ type compgen
$ "$BASH" -c 'type compgen'
$ "$BASH" -c 'comgpen -W "test{1..3}"'
$ bash -c 'type compgen'
$ bash -c 'compgen -W "test{1..3}"'
$ /run/current-system/sw/bin/bash -c 'type compgen'
$ /run/current-system/sw/bin/bash -c 'compgen -W "test{1..3}"' |
Here we go (sorry for the german locale 😆 ):
|
Thanks. Hmm, it seems the error message is produced by another process called as
$ ble-detach $ stty sane; $ git annex copy [TAB] Could you press TAB in the above position marked as |
Thanks! Then, I guess it's unrelated to ble.sh.
$ exec {BASH_XTRACEFD}> debug.txt
$ set -x
$ git annex copy bash [TAB]
$ set +x Then, could you share the content of debug.txt? You can attach a text file by dropping the file in GitHub's textbox. |
ble version: 0.4.0-devel3+1a5c451c
Bash version: 5.2.15(1)-release (x86_64-pc-linux-gnu)
I am not 100% positive that this is actually an issue with blesh, but it never happened before I installed blesh, so this is where I think posting this issue is the best way to start:
The error you see happened while typing, no
TAB
was hit or something like that, just simple typing.I am not sure what to do to debug this, though.
The text was updated successfully, but these errors were encountered: