Skip to content

Instantly share code, notes, and snippets.

@paul-d-ray
Last active February 8, 2026 01:15
Show Gist options
  • Select an option

  • Save paul-d-ray/02240650f140f0e24e6d63bfa045d1c6 to your computer and use it in GitHub Desktop.

Select an option

Save paul-d-ray/02240650f140f0e24e6d63bfa045d1c6 to your computer and use it in GitHub Desktop.
Wezterm running on Windows using Nushell Issues

Here are a few issues I have with Wezterm

I am running Wezterm on Windows.

  • Nusheell has a few issues with Wezterm. I have to disable the OSC133.

    $env.config.shell_integration.osc133 = false

  • Using Nushell in Wezterm, the clear command (and also Ctrl-L), chop off part of the scrollback.

  • Wezterm does not remember and use the last window position.

  • Wezterm does not have a setting for a sound (i.e. bell or alarm) I found a way to add a command in the config to call an extral program to play a sound. I use the alarm sound for the timer function I created.

      wezterm.on("bell", function(window, pane)
      wezterm.run_child_process({
        "C:\\Users\\Paul_Ray\\scoop\\apps\\nircmd\\current\\nircmd.exe", 
        "mediaplay", 
        "2000", 
        "C:\\Program Files\\Tclock\\waves\\Alarm.wav"
      })
      end)
    

Notes:

OSC 133 is a terminal hinting / semantic marker used mainly by advanced terminals (like iTerm2, WezTerm, kitty, VS Code terminal, etc.) to mark shell boundaries and command states.

It helps the terminal understand things like: when a prompt starts when a command starts when a command ends whether a command succeeded or failed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment