kitty shows PARSE ERROR popup when closing terminal launched from Obsidian

[OriLiMu]

Description

I'm launching kitty terminal from Obsidian (note-taking app, shell-command plugin) to edit files with the following command:

kitty -e nvim +{{caret_position:line}} {{file_path:absolute}}

Where {{caret_position:line}} and {{file_path:absolute}} are Obsidian template variables that get replaced with the actual line number and absolute file path.

Issue: When I close the kitty window, an error popup appears showing PARSE ERROR, indicating that kitty received unsupported escape sequences.

The error popup blocks the screen and interferes with my workflow.

Attempted Solutions

I've tried the following methods to disable the error popup, but none worked:

1. Added to ~/.config/kitty/kitty.conf:

   notify_on_cmd_finish never
   

2. Using command-line parameter:

   kitty -o notify_on_cmd_finish=never -e nvim ...

3. Disabling shell integration:

   kitty -o shell_integration=no -e nvim ...

None of these prevented the error popup from appearing.

Questions

1. Is there a way to completely disable kitty's error popup notifications?
2. Is this PARSE ERROR caused by escape sequences from nvim?
3. Are there any other recommended configurations to avoid this issue?

Environment

• OS: Linux (Manjaro 6.6.119-1-MANJARO)
• Kitty version: 0.45.0
• Neovim version: v0.11.5

Issue Link

Submit to: Kitty GitHub Issues

[kovidgoyal]

There is no PARSE ERROR popup in kitty. PARSE ERROR is written to the stderr of the kitty process, if you dont want to see it redirect stderr to /dev/null when launching kitty.