Closed dmilith closed 1 year ago
split:pane() stopped working?
Also
wezterm.on('mux-startup', function()
local tab, pane, window = mux.spawn_window {}
pane:split { direction = 'Top' }
end),
doesn't seem to be triggered at all
Debug overlay says:
00:02:12.004 ERROR wezterm_gui > while processing gui-startup event: bad argument #2 to `MuxPane.split`: error converting Lua table to userdata (expected userdata of type mux_lua::pane::SplitPane)
stack traceback:
[C]: in local 'poll'
[string "?"]:5: in method 'split'
[string "/Users/dmilith/.config/wezterm/wezterm.lua"]:304: in function <[string "/Users/dmilith/.config/wezterm/wezterm.lua"]:293>
when I try the more elaborate example from https://wezfurlong.org/wezterm/config/lua/gui-events/gui-startup.html
For now, the workaround I've found is to just use first_pane:split()
(no curly braces). Then it works (well, kinda - since no options can be specified).
This should be resolved now in main
.
It typically takes about an hour before commits are available as nightly builds for all platforms. Linux builds are the fastest to build and are often available within about 20 minutes. Windows and macOS builds take a bit longer.
Please take a few moments to try out the fix and let me know how that works out. You can find the nightly downloads for your system in the wezterm installation docs.
If you prefer to use packages provided by your distribution or package manager of choice and don't want to replace that with a nightly download, keep in mind that you can download portable packages (eg: a .dmg
file on macOS, a .zip
file on Windows and an .AppImage
file on Linux) that can be run without permanently installing or replacing an existing package, and can then simply be deleted once you no longer need them.
If you are eager and can build from source then you may be able to try this out more quickly.
Works like a charm in the new build! thanks! <3
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.
What Operating System(s) are you seeing this problem on?
macOS
Which Wayland compositor or X11 Window manager(s) are you using?
No response
WezTerm version
20230713-081419-f73f7180
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
I have this in my configuration:
But after the update, only the first pane is created (that one with sccache).
To Reproduce
Just use my configuration
Configuration
Expected Behavior
No response
Logs
No response
Anything else?
No response