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

Using wezterm connect my.sever causes wonky colors #748

Closed
jaredramirez opened this issue Apr 29, 2021 · 5 comments
Closed

Using wezterm connect my.sever causes wonky colors #748

jaredramirez opened this issue Apr 29, 2021 · 5 comments
Labels
bug Something isn't working fixed-in-nightly This is (or is assumed to be) fixed in the nightly builds. multiplexer waiting-on-op Waiting for more information from the original poster

Comments

@jaredramirez
Copy link

Describe the bug

When connecting to a server with wezterm connect my.server, the colors when launching the text editor kakoune are really wonky. Whenever connecting to the server with wezterm ssh user@host, the colors display correctly.

Environment (please complete the following information):

Local

  • OS: MacOS Big Sur
  • Version: wezterm 20210407-nightly

Remote

  • OS: NixOS
  • Version: wezterm 20210407-nightly

To Reproduce

Connect to a remote machine with wezterm connect, open kakoune, and use any colorscheme other than the default

Configuration

    ssh_domains = {
        {
            name = "home.server",
            remote_address = "...",
            username = "jared",
        }
    },

Expected behavior

I expect the colors to be unaltered & display normally.

Screenshots

When running kakoune in wezterm locally:
Screen Shot 2021-04-29 at 9 43 53 AM

When running kakoune on remote with wezterm connect home.server:
Screen Shot 2021-04-29 at 9 44 14 AM

When running kakoune on remote with wezterm ssh jared@...:
Screen Shot 2021-04-29 at 9 44 35 AM

Session Recording

Additional context

@jaredramirez jaredramirez added the bug Something isn't working label Apr 29, 2021
@wez
Copy link
Owner

wez commented Apr 29, 2021

Do you have the same colorscheme configured in both the server and the client wezterm configs?

@jaredramirez
Copy link
Author

Yup, using the same kakrc and nix config. My entire config is here if it's needed!

wez added a commit that referenced this issue May 30, 2021
@wez wez added the fixed-in-nightly This is (or is assumed to be) fixed in the nightly builds. label May 30, 2021
@wez
Copy link
Owner

wez commented May 30, 2021

Nightly builds now know how to pass the remote color palette to the client; you'll need to update both the client and the server side for this to work.
Please give it a try and let know how it goes!

@wez wez added the waiting-on-op Waiting for more information from the original poster label May 30, 2021
wez added a commit that referenced this issue May 30, 2021
@no-response
Copy link

no-response bot commented Jun 13, 2021

This issue has been automatically closed because there has been no response to the request for more information from the original author. With only the information that is currently in the issue, there isn't enough information to take further action. Please reach out if you have or find the answers we need so that we can investigate further.

@no-response no-response bot closed this as completed Jun 13, 2021
@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2023

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working fixed-in-nightly This is (or is assumed to be) fixed in the nightly builds. multiplexer waiting-on-op Waiting for more information from the original poster
Projects
None yet
Development

No branches or pull requests

2 participants