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

OSC52 popup is too frequent #497

Open
sscott33 opened this issue Jun 22, 2023 · 4 comments
Open

OSC52 popup is too frequent #497

sscott33 opened this issue Jun 22, 2023 · 4 comments

Comments

@sscott33
Copy link

I am delighted to see OSC52 support in KiTTY, but needing to answer a prompt (the "Allow OSC52 clipboard sync?" popup) every time I make a selection in Tmux is rather annoying -- especially since I must answer the prompt to continue using the terminal. It would be nice to have a checkbox that says "don't ask me again" or "always allow OSC52 clipboard sync." Or maybe this is best configured in session settings.

I'll leave the solution up to you, but I don't think it is reasonable to continually answer this prompt when using this feature.

@dyfrgi
Copy link

dyfrgi commented Aug 17, 2023

@unxed As the author of the OSC52 feature, would you be willing to pick this bug up?

@mgrant0 mgrant0 mentioned this issue Sep 15, 2023
@unxed
Copy link
Contributor

unxed commented Sep 24, 2023

The code now checks for existence of environment variable OSC52ALLOWED. If it is set to any non-empty value, user will not be asked for confirmation any more.

How to set variable permanently:
#495 (comment)

@YAMLcase
Copy link

I discovered a workaround until the bug gets fixed.

  • Open settings for the default config
  • go to Windows > Behavior
  • at the bottom, "Warn before OSC52 clipboard sync" is unchecked. Check it.
  • Save default settings
  • uncheck "Warn before OSC52 clipboard sync"
  • Save default settings again

My guess without digging through code, the config file/registry doesn't have this field/key so KiTTY is probably assuming "enabled" and it takes toggling the option to get it written to config.

@unxed
Copy link
Contributor

unxed commented Mar 10, 2024

I can probably get to it in a couple of weeks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants