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

Super + Q keybinding problem #4436

Closed
og900aero opened this issue Oct 14, 2023 · 1 comment · Fixed by #4605
Closed

Super + Q keybinding problem #4436

og900aero opened this issue Oct 14, 2023 · 1 comment · Fixed by #4605
Labels
bug Something isn't working

Comments

@og900aero
Copy link

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

Linux X11

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

Dwm

WezTerm version

20231004-113117-11dec45f

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

When I run wezterm, and run lf file manager, then press Super + Q (dwm binding -> kill client), then window is closed by dwm, but at the same time, in the background, wezterm also issues a ctrl + d "command" for some reason, which also covers another command for me in lf file manager, and this causes quite a problem.

To Reproduce

  1. Run wezterm
  2. Run lf file manager
  3. Then close window bye Super + Q (in dwm)
  4. Then window is closed, and the background wezterm run ctrl + d keymap too

Configuration

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

-- This table will hold the configuration.
local config = {}

-- In newer versions of wezterm, use the config_builder which will
-- help provide clearer error messages
if wezterm.config_builder then
config = wezterm.config_builder()
end

-- This is where you actually apply your config choices
config.enable_wayland = false
config.default_cwd = "/home/Data/"
config.check_for_updates = true
config.show_update_window = true
config.check_for_updates_interval_seconds = 604800 -- weekly
config.scrollback_lines = 500
config.color_scheme = 'AdventureTime'
-- config.enable_tab_bar = false
config.hide_tab_bar_if_only_one_tab = true
-- config.font = wezterm.font('JetBrains Mono', { weight = 'Bold', italic = true })
config.font = wezterm.font('IosevkaTerm Nerd Font Mono', { weight = 'Bold', italic = true })
config.font_size = 15.0
config.line_height = 1.0
config.window_close_confirmation = 'NeverPrompt'
config.disable_default_key_bindings = true

wezterm.action.SpawnCommandInNewWindow {
label = 'List all the files!',
args = { 'ls', '-la' },
cwd = '/home/Data',
}

config.keys = {
{
key = 'P',
mods = 'CTRL',
action = wezterm.action.ActivateCommandPalette,
},
}

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

Expected Behavior

If I use the parameter config.disable_default_key_bindings = true, wezterm should do nothing for Super + Q keybinding.

Logs

16:28:21.421 WARN window::os::x11::connection > Unable to resolve appearance using xdg-desktop-portal: get_appearance.read_setting: Reading xdg-portal org.freedesktop.appearance color-scheme: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.portal.Desktop was not provided by any .service files

Anything else?

No response

@og900aero og900aero added the bug Something isn't working label Oct 14, 2023
@wez wez closed this as completed in #4605 Dec 1, 2023
Copy link

github-actions bot commented Jan 1, 2024

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 Jan 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant