Closed hahuang65 closed 2 years ago
From the logs it looks like there is an error in your config file; please share it!
@wez added! I think that EOF
issue should be fixed. I think there was an extra return {}
when I was testing the empty config.
FWIW, probably unrelated to this issue, I have some suggestions for your config that should be faster and more robust:
Instead of using that os.capture
function (or io.popen
) I recommend using wezterm.run_child_process() as it won't block the wezterm process while waiting for the program to finish its output.
Instead of local os_name = os.capture 'uname'
I suggest wezterm.target_triple
Instead of local hostname = os.capture 'cat /etc/hostname 2>/dev/null || hostname'
I recommend wezterm.hostname()
This should be fixed now in main
.
It typically takes about an hour before fixes 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.
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.
@wez works very well, thank you very much. Thanks to @Funami580 for their hard work as well. Appreciate it!
Thanks @Funami580!
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?
Linux Wayland
WezTerm version
wezterm 20220704-211225-67b96b9b
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
Pasting will not work in certain (most) windows. I'm not able to figure out reproduction steps on how to consistently get it to work, but restarting seems to make it such that the first
wezterm
will work with pasting, and subsequently no other windows will work with pasting..However, I have observed that windows that previously allowed pasting will stop working, and windows that previously didn't work will start working.
It's pretty random, but I would say, at any given time, no more than 2 windows will work with pasting, no matter how many I open.
To Reproduce
No response
Configuration
Without a
wezterm.lua
the problem does NOT occur.However, with an empty
wezterm.lua
(onlyreturn {}
in the contents), this will still occur.Removing the config file, any new windows I open will work... but reloading the existing one does not... but when I place the file back... that original window now can paste!
EDIT: Adding my config file
Expected Behavior
Pressing
Ctrl-Shift-v
should always paste what's in my clipboard.Logs
Anything else?
No response