-
Notifications
You must be signed in to change notification settings - Fork 172
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
BASH 4.2 vs. Jeditterm 3.36 and newer #275
Comments
I finally found the exception:
Something has changed regarding |
Ok, problem understood: Although I think, just not using the |
vokoscreenNG-2024-01-17_23-54-00.mp4The problem with the |
@manticore-projects Thanks for reporting. Yes, Regarding the the freeze, you can try to debug it yourself or capture the whole terminal session output and provide it here. Shell output can be captured using script command. For example, if bash is installed to
|
Greetings!
We have JediTerm up and running in general, but face a problem with a particular combination of JediTerm and Bash:
I understand that this lacks a lot of information and I see it as a placeholder for further investigation.
Although I have been facing this problem on 4 different servers now. Some recent development broke older shells.
I will still test against latest JediTerm 3.40 (but you changed so many things again, which i still need to adopt).
Update: I compiled BASH 4.2.53 and BASH 4.4.18 on my own computer and it runs flawlessly with JeditTerm 3.36.
The text was updated successfully, but these errors were encountered: