Open scriptori opened 2 months ago
I'm wondering if this is a case where we need to implement natives for apple silicon for the few bits of CDT that need it.
Actually we implemented that a while ago in 13cdd8ada77f94e69b92e8da90548e554ac81c8e - I had forgotten.
So something else must be going on.
I'll need access to an Mac machine to try to identify - unless I can get some additional details to understand why this is failing.
@jonahgraham @scriptori - it may not be macos related; I have a similar problem under Linux x86_64 with /bin/bash, /bin/zsh. #831
@scriptori : Can you try [WORKING] fish/ksh/tcsh/sh (you may have to install from homebrew). Also [NOT_WORKING] bash, as another data point.
OMG: finally someone else has the same problem as me (albeit on a different OS)
I can reproduce this on Linux(x86_64, Fedora 40, Wayland/X11) with shells (non-working) zsh, bash Working shells: fish / tcsh / sh / ksh / csh
This is not a recent issue: back in 2020~Fedora 33
At that time shell command tmux with bash as child process worked; but now tmux -> bash shows the UI issue.
I'll close #831 shortly as a duplicate of this if @scriptori can successfully run with fish/ksh/tcsh/sh
On Linux(Fedora 40/x86_64) it is due to shell customisation: https://github.com/eclipse-cdt/cdt/issues/831#issuecomment-2178760849 - not sure what exactly breaks yet
@space88man I am going to try it tomorrow. Thanks for looking into this.
@space88man I am going to try it tomorrow. Thanks for looking into this.
BTW my issue #831 has been fixed by updating TM Terminal components into 2024-06 using the p2 repo that @jonahgraham posted: https://github.com/eclipse-cdt/cdt/issues/831#issuecomment-2179668008
Describe the bug I've installed TM Terminal from Eclipse Marketplace on my MacBook Apple M1 Pro running Sonoma 14.4.1. My environment is configured to use /bin/zsh. However, when I try to type anything, the terminal does not show what I type! But when I hit enter, the command works. However, it still does not help me that I can't see what I'm typing because I could have plenty of typos and whatnot, and it's such an impediment.
To Reproduce Steps to reproduce the behavior:
Expected behavior A prompt like "[~]$ " should be displayed, and the command should appear as it is typed.
Screenshots
Version Information (please complete the following information):
Additional context