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

Tabs moved with MoveTabRelative don't persist. #5339

Open
techdude opened this issue Apr 25, 2024 · 2 comments
Open

Tabs moved with MoveTabRelative don't persist. #5339

techdude opened this issue Apr 25, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@techdude
Copy link

What Operating System(s) are you seeing this problem on?

Windows

Which Wayland compositor or X11 Window manager(s) are you using?

No response

WezTerm version

20230712-072601-f4abf8fd

Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?

No, and I'll explain why below

Describe the bug

When moving tabs with Ctrl + Shift + PgUp/PgDown, they move. However, after exiting the client and restarting it, the tabs have returned to the original positions.

Note this setup is using a Windows client and Linux (RHEL) server.

To Reproduce

  • Open 4 tabs and put some content in each one so they can be easily identified. (for example, echo 1, etc)
  • Move the tabs around into some non-original order using Ctrl + Shift + PgUp and PgDown
  • Exit the client
  • Reopen the client.

Configuration

This is the entirety of my config file:

ocal wezterm = require 'wezterm'

local config = wezterm.config_builder()

config.scrollback_lines = 100000

return config

Expected Behavior

Expected tabs to retain their order when restored.

Actual Behavior:
Tabs return to the order in which they were opened

Logs

Only log line is:
16:54:34.100 ERROR wezterm_term::terminalstate::iterm > my pixel dimensions are wacky! 0x0

Anything else?

No response

@techdude techdude added the bug Something isn't working label Apr 25, 2024
@wez
Copy link
Owner

wez commented May 5, 2024

Please explain more about the client/server; are you using multiplexing?

@wez wez added the waiting-on-op Waiting for more information from the original poster label May 5, 2024
@techdude
Copy link
Author

There is only a single ssh_domain used on the client. The configuration file for the client is shown below (server is already provided).

-- Pull in the wezterm API
local wezterm = require 'wezterm'

-- This table will hold the configuration.
local config = {
  window_background_opacity = 0.9,
  ssh_domains = {
	{
      name = 'ssh1',
	  remote_address = '<server hostname>',
	  username = '<my username>',
	  local_echo_threshold_ms = 500,
	}
  },
  
  tab_bar_at_bottom = true,
  
  default_domain = 'ssh1',
}

-- and finally, return the configuration to wezterm
return config

@github-actions github-actions bot removed the waiting-on-op Waiting for more information from the original poster label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants