Skip to content
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

Terminus not showing text #439

Open
IvoryJam opened this issue Oct 9, 2024 · 7 comments
Open

Terminus not showing text #439

IvoryJam opened this issue Oct 9, 2024 · 7 comments

Comments

@IvoryJam
Copy link

IvoryJam commented Oct 9, 2024

When opening Terminus, it doesn't show any text, but only in the Gnome DE. In KDE it works just fine.

I've found that when I do the ctrl-l keyboard shortcut, it does show the prompt but no stdout it looks like (but sometimes it does but drops the first line). The commands do run though, but I can only see what I type if I do ctrl-l first or if I backspace once.

Also if I preface the command with any other command, I can get the full stdout (still no prompt unless I do ctrl-l though) e.g. echo; ls shows the output of ls

Screencast.from.2024-10-09.13-36-53.mp4
@IvoryJam
Copy link
Author

Forgot to mention I'm on 4180

@IvoryJam
Copy link
Author

Found the debug and set it to true, ran echo hi

sent: e
receieved: e
add 0 line(s) to scroll back history
screen is dirty: [0]
updating lines takes 0.0030944347381591797s
mode: [7, 25], cursor: 17.0
sent: c
receieved: c
add 0 line(s) to scroll back history
screen is dirty: [0]
updating lines takes 0.0024759769439697266s
mode: [7, 25], cursor: 18.0
sent: h
receieved: h
add 0 line(s) to scroll back history
screen is dirty: [0]
updating lines takes 0.0018696784973144531s
mode: [7, 25], cursor: 19.0
sent: o
receieved: o
add 0 line(s) to scroll back history
screen is dirty: [0]
updating lines takes 0.002549409866333008s
mode: [7, 25], cursor: 20.0
sent:  
receieved:  
add 0 line(s) to scroll back history
screen is dirty: [0]
updating lines takes 0.00183868408203125s
mode: [7, 25], cursor: 21.0
sent: h
receieved: h
add 0 line(s) to scroll back history
screen is dirty: [0]
updating lines takes 0.001888275146484375s
mode: [7, 25], cursor: 22.0
sent: i
receieved: i
add 0 line(s) to scroll back history
screen is dirty: [0]
updating lines takes 0.0025022029876708984s
mode: [7, 25], cursor: 23.0
sent: 
receieved: 
<0x1b>[?2004l
<0x1b>]133;C<0x1b>\
<0x1b>]777;preexec<0x1b>\hi
<0x1b>]0;user_name@fedora:~/sublime_issue<0x1b>\<0x1b>]777;notify;Command completed;echo hi<0x1b>\<0x1b>]777;precmd<0x1b>\<0x1b>]7;file://fedora/home/user_name/sublime_issue<0x1b>\<0x1b>[?2004h<0x1b>[01;32m➜<0x1b>[01;37m sublime_issue<0x1b>[01;32m<0x1b>[00m<0x1b>[0;31m<0x1b>[00m 
updating lines takes 0.00027370452880859375s
mode: [7, 25], cursor: 0.2

@giampaolo
Copy link

I have the same problem. I only see the output of commands, but nothing when I type, nor I see the shell prefix.
You said you solved it. How?

@IvoryJam
Copy link
Author

IvoryJam commented Nov 7, 2024

It works in KDE, I also found if I launch it through the desktop file instead of the command subl then it works kind of. Maybe something with the TTY inside of Gnome?

@davidheryanto
Copy link

Having the exact same issue.

Sublime Text version 4180
Using Fedora 40, bash version 5.2.26

Not sure which of the above are causing the issue, but I notice if I change Terminus setting and set the terminal to sh instead of bash, it seems to work properly.

  1. First, go the Terminus setting file
    image

  2. Change the shell_configs from bash to sh
    image

  3. When using sh, it will normally not load your bash configuration ~/.bashrc, and the shell prompt becomes boring like just sh > . So I set the PS1 environment variable as well.

{
    // the default config, either a single config name or a platform
    // specific dict
    "default_config": {
        "linux": "Bash",    // login shell
        "osx": null,      // login shell
        "windows": "Command Prompt"
    },
    // a list of available shells to execute
    "shell_configs": [
        {
            "name": "Bash",
            "cmd": ["sh"],
            "env": {
                "PS1": "\\[\\e[38;5;141m\\]\\u@\\h \\[\\e[38;5;247m\\]\\W\\[\\e[0m\\]\\$ "
            },
            "enable": true,
            "platforms": ["linux", "osx"]
        }
.....

@giampaolo
Copy link

Apparently I can solve the problem if I remove the -l option:

    "shell_configs": [
        {
            "name": "Bash",
-            "cmd": ["bash", "-i", "-l"],
+            "cmd": ["bash", "-i"],
            "env": {},
            "enable": true,
            "platforms": ["linux", "osx"]
        },
    ]

@IvoryJam
Copy link
Author

I tried to do the same thing and still got the error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants