Hello,

I believe that the xterm has seen the resource change.  I found a tool 'xgetres' to see the resource, and it says:
$ ./xgetres "XTerm*disallowedWindowOps"
20,21,SetXprop

This agrees with appres:
$ appres XTerm | grep disallowed
XTerm*disallowedWindowOps:      20,21,SetXprop

Checking AllowWindowOps in the xterm menu makes no difference.  According to xsel (-p, -s, -b), selecting text within tmux never writes to any X selection. Selecting text outside of tmux writes the primary selection.




On 4/11/24 01:36, Nicholas Marriott wrote:
Are you sure xterm has seen the resource change? What if you load the file manually with xrdb? If you open the xterm menu and tick "Allow Window Ops" does it work?

Are you sure it is copying to the selection you expect? You can check by installing xsel on the local host and running xsel -b/xsel -p and see if you see what you copied.




On Thu, 11 Apr 2024 at 08:00, Kyle Markley <k...@arbyte.us> wrote:

    Hello,

    I have only been using tmux for a couple weeks, but I am loving
    it.  I want to keep similar configurations at home and at work,
    but one of those environments is giving me clipboard trouble.

    I have followed the wiki clipboard instructions
    (https://github.com/tmux/tmux/wiki/Clipboard) to synchronize with
    the system clipboard using the OSC 52 method.  At work, on a Linux
    system, it's working great. But at home, on OpenBSD 7.5, it isn't.

    In both environments my terminal is xterm, I have set-clipboard
    set to external, the Ms capability is set, and I'm setting
    XTerm*disallowedWindowOps as required. But uniquely on the OpenBSD
    system, I cannot copy from inside tmux and paste outside tmux, or
    vice versa.  What is my next step to debug this?
-- You received this message because you are subscribed to the Google
    Groups "tmux-users" group.
    To unsubscribe from this group and stop receiving emails from it,
    send an email to tmux-users+unsubscr...@googlegroups.com.
    To view this discussion on the web, visit
    
https://groups.google.com/d/msgid/tmux-users/60dffb50-7020-4cdf-b36e-8722f40606fdn%40googlegroups.com
    
<https://groups.google.com/d/msgid/tmux-users/60dffb50-7020-4cdf-b36e-8722f40606fdn%40googlegroups.com?utm_medium=email&utm_source=footer>.

--
You received this message because you are subscribed to a topic in the Google Groups "tmux-users" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/tmux-users/kLeXXgfE9eA/unsubscribe. To unsubscribe from this group and all its topics, send an email to tmux-users+unsubscr...@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/tmux-users/CAEdLfcEptqODjsriktD%3DgDKjE4xDedU13Nr8WyOER_OAf233kw%40mail.gmail.com <https://groups.google.com/d/msgid/tmux-users/CAEdLfcEptqODjsriktD%3DgDKjE4xDedU13Nr8WyOER_OAf233kw%40mail.gmail.com?utm_medium=email&utm_source=footer>.


--
Kyle Markley

--
You received this message because you are subscribed to the Google Groups 
"tmux-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to tmux-users+unsubscr...@googlegroups.com.
To view this discussion on the web, visit 
https://groups.google.com/d/msgid/tmux-users/bfc6342e-3217-4f2e-8d4f-96a9eccc00d3%40arbyte.us.

Reply via email to