romikb Posted September 17, 2019 Report Share Posted September 17, 2019 I have a server on 1.4 upgraded from 1.3 Bash completion not working when I connect by ssh to server. It is because bash option "progcomp" is unset (but should be setted by default). If a run a new bash shell from existing (type bash or mc) the completion is working in new shell. On 1.3 a have no this issue. Link to comment Share on other sites More sharing options...
0 bcowan Posted September 17, 2019 Report Share Posted September 17, 2019 I just checked on a fresh container of 1.4 and on my main machine as normal user and root. shopt shows progcomp on in all cases Link to comment Share on other sites More sharing options...
0 romikb Posted September 17, 2019 Author Report Share Posted September 17, 2019 I found the source of issue - it is the /etc/profile: # turn off progammable completion in bash by default: shopt -u progcomp 17 minutes ago, bcowan said: I just checked on a fresh container of 1.4 and on my main machine as normal user and root. shopt shows progcomp on in all cases I think that containers are nested bash shells. My containers also has no issues but main system have. Link to comment Share on other sites More sharing options...
0 bitterbitbasher Posted September 17, 2019 Report Share Posted September 17, 2019 I also have a problem with bash, but in my case seems that the shopt options doesn't work well. For example, the shopt -s nocaseglob doesn't work at all. Link to comment Share on other sites More sharing options...
Question
romikb
I have a server on 1.4 upgraded from 1.3
Bash completion not working when I connect by ssh to server. It is because bash option "progcomp" is unset (but should be setted by default).
If a run a new bash shell from existing (type bash or mc) the completion is working in new shell.
On 1.3 a have no this issue.
Link to comment
Share on other sites
3 answers to this question
Recommended Posts