-
I tried this, but still get the close confirmation on tab middle click. window_close_confirmation = 'NeverPrompt',
skip_close_confirmation_for_processes_named = { 'bash', 'sh', 'zsh', 'fish', 'tmux' },
keys = {
{
key = 'w', mods = 'CTRL|SHIFT', action = wezterm.action.CloseCurrentTab { confirm = false }
},
} It looks like |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
I'd like to understand more about why |
Beta Was this translation helpful? Give feedback.
-
Digging into this a bit more I found out that this is flatpak issue. Tried to grant every possible permission via Flatseal with no luck and switched to rpm package. Both rpm and appimage don't have this problem. I only picked Flatpak because wezterm isn't in Fedora repos thus it lacks auto-updates if installed other way. |
Beta Was this translation helpful? Give feedback.
-
It also seems like ssh and unix domains have a different behavior here than the local domain. I have this in my config, trying various things to skip the tab close confirmation (config.keys already exists when this code is run): config.window_close_confirmation = 'NeverPrompt'
table.insert(
config.keys,
{
key = 'w',
mods = 'SHIFT|CTRL',
action = wezterm.action.CloseCurrentTab { confirm = false },
}
)
wezterm.on('mux-is-process-stateful', function(_proc)
return false
end) ctrl-shift-W works as expected, with no confirmation. In the local domain, I can also close tabs without confirmation when using the "x" on the tab. In an ssh or unix domain however, using the "x" on the tab still shows the confirmation dialog. (I can file an issue if I'm not just overlooking something here.) |
Beta Was this translation helpful? Give feedback.
Digging into this a bit more I found out that this is flatpak issue. Tried to grant every possible permission via Flatseal with no luck and switched to rpm package. Both rpm and appimage don't have this problem. I only picked Flatpak because wezterm isn't in Fedora repos thus it lacks auto-updates if installed other way.