ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
rasterman has quit [Quit: Gettin' stinky!]
lsd|2 has joined #wayland
i509vcb has joined #wayland
<i509vcb>
Is there some intended way to limit the number of objects a client could create?
Company has joined #wayland
glennk has quit [Ping timeout: 480 seconds]
<danieldg>
I would assume that a simple count would be one part of a resource-counting system that would eventually result in a fatal error on exhaustion (because there's no protocol for nicely informing the client of this, to my knowledge). That feels very compositor-specific.
<i509vcb>
Well if the client creates too many objects I could always just kill it
<danieldg>
right
<danieldg>
I don't think you have any other choices
PopLamina has quit [Remote host closed the connection]
kts has joined #wayland
glennk has joined #wayland
mart has quit [Remote host closed the connection]
mart has joined #wayland
Nefsen402 has quit [Remote host closed the connection]
bl4ckb0ne has quit [Remote host closed the connection]
emersion has quit [Remote host closed the connection]
Nefsen402 has joined #wayland
emersion has joined #wayland
bl4ckb0ne has joined #wayland
psykose has quit [Remote host closed the connection]
psykose has joined #wayland
Company has quit [Quit: Leaving]
systwi has joined #wayland
<haasn>
is there a wayland clipboard manager that supports images / non-text?
<haasn>
by "clipboard manager" I mean something that will keep my clipboards synchronized
<haasn>
I currently use `wl-paste -pw wl-copy` but it has two issues: 1. supports text only, and 2. only synchronizes in one direction, I want both
<kennylevinsen>
haasn: for the first part, `man 1 wl-clipboard`, look for --type.
<pq>
cli tools to access the clipboard are kind of not supposed to work to begin with...
<haasn>
kennylevinsen: that only works if I want to force a specific type, no? but I want to sometimes copy text and at other times copy images
<psykose>
the issue is that when you copy 'an image' in firefox, it might advertise a lot of types
<kennylevinsen>
haasn: you're not forcing a type, you're specifying which of the numerous offered types to pick
<psykose>
so you would copy a bunch of the same image in different formats if it just pulled them all
<kennylevinsen>
there are dedicated clipboard management tools (wlroots at least has a protocol for that), but I'm not personally familiar with them.
<haasn>
well, it seems that `wl-paste -t image -pw wl-copy` doesn't break when copying text
<haasn>
so I guess I can use that to work around the most common case of this issue
<haasn>
although it will probably still break on files and the like
<emersion>
pq, (1) there are OSC extensions for clipboard access (2) this is a clipboard manager use-case
<pq>
OSC? like a terminal emulator? then you have a window, so that's fine.
<emersion>
CLI tools can access the clipboard via escape sequences
<emersion>
the terminal emulator then relays this to Wayland/X11
<pq>
but you need a terminal window to actually relay those, right?
<emersion>
sure
<haasn>
fwiw I am copying from one GUI app to another GUI app
<emersion>
it's good for CLI text editors for instance
<pq>
so, there is a window associated to it, which makes it fine
<emersion>
but for background CLI tools, it's a clipboard manager use-case, so it's only natural that it uses something else (privileged protocol)
<pq>
privileged protocol is fine, I didn't realise they used that
<emersion>
wl-clipboard does that, yeah
<emersion>
it only uses hacks on GNOME
<pq>
wl-paste and wl-copy though?
<emersion>
part of wl-clipboard
<pq>
oh, ok
<davidre>
plasma also uses wlr-data-control
<davidre>
and supports images just fine which was the originial quesiton
<davidre>
s/quesiton/question/
<emersion>
s/GNOME/GNOME and Weston/, i suppose
<pq>
yeah, Weston has... not really a solution for authenticating clients
caveman has quit [Ping timeout: 480 seconds]
<haasn>
wait, primary selection and the regular clipboard are implemented with completely different protocols?
<haasn>
yeah seems it's via wl_data_device and zwp_primary_selection_device_v1
<haasn>
and then there's also wlr-data-control..
<haasn>
and gkt-primary-selection ?
<haasn>
why so many different clipboard protocols?
<davidre>
wlr-data-control is for clipboard manager s
<haasn>
and how can I get rid of them all and have just a single clipboard?
<davidre>
gtk- is non standard and was standardized into primary-selection (please correct me if I am wrong)
<davidre>
wl_data_device handles the clipboard
<davidre>
and primary_selection the primary_selection
<haasn>
darn
<davidre>
the thing you get when selecting text and pasting by middle click usually
<haasn>
that really stymies my plan, I was hoping it would be a simple hack patch to redirect the primary selection to the clipboard (or vice versa)
<haasn>
but if they're completely different protocols internally that plan is gone
<davidre>
If you are the clipboard manager you can do that
<davidre>
* do that with wlr-data-control quite staightfoward
<davidre>
And if you want to synchronize both for your app, set them to be the same it's also not that hard
junaid has joined #wayland
<davidre>
depending on which level you are operating, toolkit, wrapper, raw generated code
<haasn>
I am the end user who is suffering from this design, coming from X where things just worked (tm)
<emersion>
it's unfortunate that primary-selection needs to be a completely separate protocol
<emersion>
it would've been nicer to update the core protocol to be more modular
<davidre>
on plasma you can just enable synchronize clipboard and primary selection :)
<haasn>
good for plasma users :/
<haasn>
maybe the plasma clipboard manager can be ripped out and ran stand-alone
<haasn>
but probably not as I imagine it is part of the compositor itself
<davidre>
It is not
<davidre>
it uses wlr-data-control but it's part of the shell somehwat and cannot run standalone
<emersion>
it would indeed be nice to have a good standalone clipboard manager
<emersion>
i've seen too many that just hack together CLI tools
<psykose>
personally i disabled primary so that is synced enough :P
caveman has joined #wayland
caveman has quit [Remote host closed the connection]
caveman has joined #wayland
tzimmermann has quit [Quit: Leaving]
<haasn>
people seem to be recommending copyq
<haasn>
I'll give it a spin
junaid has quit [Remote host closed the connection]
silverpower has quit [Ping timeout: 480 seconds]
silverpower has joined #wayland
mart has quit [Remote host closed the connection]
mart has joined #wayland
Narrat has joined #wayland
junaid has joined #wayland
Guest2701 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest2765
mblenc1 has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
mblenc1 has quit [Ping timeout: 480 seconds]
privacy has quit [Quit: Leaving]
kts has quit [Ping timeout: 480 seconds]
junaid has quit [Remote host closed the connection]
Guest2765 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest2776
mart has quit [Quit: Konversation terminated!]
nmeum has joined #wayland
<nmeum>
hi! I am a bit confused regarding the distinction between xdg-output-unstable-v1, wlr-output-management-unstable-v1 and wl_output. I would just like to be notified when a new output/monitor is hotplugged, what do I best use for this purpose?
rv1sr has quit []
floof58 has quit [Ping timeout: 480 seconds]
<vyivel>
nmeum: checking for new wl_output globals would probably be the best option
<nmeum>
so everytime a new monitor is hotplugged a global event on the wl_registery is emitted for the wl_output interface?
<vyivel>
yep
<nmeum>
hm, somehow I only see a global event for the monitors on startup but maybe that's just a bug in my code
floof58 has joined #wayland
mvlad has quit [Remote host closed the connection]
mblenc has joined #wayland
mblenc1 has joined #wayland
mblenc has quit [Ping timeout: 480 seconds]
yang_ is now known as yang
<danieldg>
nmeum: you can run with WAYLAND_DEBUG=1 to see when you get the events
AJ_Z0 has quit [Quit: I have to return some videotapes]
AJ_Z0 has joined #wayland
Leopold has joined #wayland
Narrat has quit []
vyivel has quit [Ping timeout: 480 seconds]
CME_ has joined #wayland
CME has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
vyivel has joined #wayland
larunbe has joined #wayland
alarumbe has quit [Ping timeout: 480 seconds]
daz has joined #wayland
daz has quit [autokilled: This host may be infected. Mail support@oftc.net with questions. BOPM (2024-03-14 23:43:56)]