Fig errors for kitty shell integrations

[andrewcdowning]

Checks

• I ran q doctor in the affected command line session and it didn't resolve my issue
• I ran q restart and it didn't resolve my issue
• I searched the discussions in this repo and there are no duplicates of my issue

Expected behaviour

Terminal to start in timely manner without 4 to 6 second delay.

Actual behaviour

Kitty terminal is slow starting when CLI completions - autocomplete option enabled. Integrations for kitty installed with q integrations install input-method command. While investigating slowdown I found the following error repeated in kitty's app log during startup of new session.

[PARSE+ERROR]+Ignoring+OSC+697%2C+typically+used+by+Fig+for+shell+integration 

Steps to reproduce

Use latest version of Kitty term
Use latest version of Q

In Q enable shell auto completions

In terminal run kitty command

Environment

[q-details]
version = "1.4.6"
hash = "bd280c3d07adab595bbd62de5ab841eb0567f094"
date = "2024-11-15T20:16:24.896916Z (4d ago)"
variant = "full"

[system-info]
os = "macOS 14.7.1 (23H222)"
chip = "Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz"
total-cores = 6
memory = "16.00 GB"

[environment]
cwd = "/Users/USER"
cli-path = "/Users/USER"
os = "Mac"
shell-path = "/bin/zsh"
shell-version = "5.9"
terminal = "Kitty"
install-method = "unknown"

[env-vars]
PATH = "/Users/USER/.asdf/shims:/usr/local/opt/asdf/libexec/bin:/usr/local/bin:/usr/local/sbin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/usr/local/go/bin:/Users/USER/.atuin/bin:/Applications/kitty.app/Contents/MacOS:/Users/USER/.cargo/bin:/Users/USER/.toolbox/bin:/Users/USER/.local/bin"
SHELL = "/bin/zsh"
TERM = "xterm-kitty"
__CFBundleIdentifier = "net.kovidgoyal.kitty"

[brandonskiser]

That error message by kitty should be unrelated to startup time, it's something we emit to every pseudoterminal, not just kitty.

The startup delay seems to be inconsistent across new terminal sessions, sometimes it takes 4-6 seconds and other times it's 100-200ms. It doesn't always take that long for you right?

Having better startup profiling is something we should add to qterm.

[andrewcdowning]

Hi, this was consistent across sessions until I removed auto completions. Now that this is turned off the startup time for new sessions is back to normal consistently.

[brandonskiser]

Have you also tested startup time in other terminals? Just having the autocomplete setting shouldn't consistently add that large of a slowdown, it's likely something else like update checking or telemetry that's blocking when it otherwise shouldn't. I'll need to look into profiling where exactly this could be happening though