nushell: Keybindings do not seem to work

Describe the bug I’ve tried to create new keybindings by creating the keybindings.yml file by the side of config.toml The file does seem to be processed in some form because if I make a typo, nushell will give me some errors the next time I launch it.

To Reproduce Steps to reproduce the behavior:

  1. create keybindings.yml file with these contents:
- key:
    Char: H
  modifiers:
    CTRL:
  binding:
    Kill:
      BackwardChar: 1
  1. launch nushell
  2. type in something and try to delete chars with ctrl-h; it will do nothing

Expected behavior I expected that ctrl-h would behave like backspace instead of doing nothing. The same goes for other bindings I tried to make like ctrl-m to behave like return. Even a simple rebind just the letter h to delete does nothing.

Configuration (please complete the following information):

Run version | pivot and paste the output to show OS, features, etc.

> version | pivot
  #         Column0                                            Column1
────────────────────────────────────────────────────────────────────────────────────────────────────────────
   0   version              0.33.0
   1   short_commit         55cab9eb
   2   commit_hash          55cab9eb4ff4ee3ee73efc6f8973901b2a91c921
   3   commit_date          2021-06-22 05:22:33
   4   build_os             windows-x86_64
   5   rust_version         rustc 1.53.0 (53cb7b09b 2021-06-17)
   6   rust_channel         stable-x86_64-pc-windows-msvc (default)
   7   cargo_version        cargo 1.53.0 (4369396ce 2021-04-27)
   8   pkg_version          0.33.0
   9   build_time           2021-06-22 05:42:52
  10   build_rust_channel   release
  11   features             clipboard-cli, ctrlc, default, ptree, rustyline, term, trash, uuid, which, zip
  12   installed_plugins

Add any other context about the problem here. I thing it’s relevant to mention that:

  • I’m on Windows
  • the bug happens when I run nushell from the Windows Terminal, cmd, and even ‘standalone’ (win-r then type ‘nu’ and run)
  • I’ve installed it using scoop

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15

Most upvoted comments

Just wanted to let you know that today I installed nushell again and everything seems to work as intended. I didn’t know when those fixes were merged into nushell, so that’s why I didn’t test it earlier. nice job!