On Monday, 31 January 2022 04:49:59 CET chris wrote: > On Monday, 31 January 2022 04:43:34 CET chris wrote: > > On Monday, 31 January 2022 04:28:06 CET Ihor Radchenko wrote: > > > chris <inkbottle...@gmail.com> writes: > > > >> What will happen if you try (kill-new "something") in your Emacs > > > >> (preferably, emacs -Q)? Will "something" be present in your Wayland > > > >> clipboard? > > > > > > > > emacs -Q, then `M-: (kill-new "something")` > > > > Then `C-y` in `*scratch*`, string "something" is pasted. > > > > Then go to terminal (Konsole, specifically), `C-S-v`, string > > > > "something" > > > > is > > > > pasted, too. > > > > > > Got it. What about emacsclient -e "(kill-new \"test123\")"? > > > > `~/path-to-emacs/lib-src/emacsclient -e "(kill-new \"test123 > > \")"` > > > > Emacs side, `C-y` => "test123" > > > > Terminal side, `C-S-v` => no trace of the "test123" string. > > My, I missed one pivotal point: > Right after that operation, I cannot cut and paste straight away from > terminal to emacs. > If I copy and paste some string "test567" from terminal to Firefox or > whatever, it is working fine, but `C-y` in emacs is still "test123". >
Also, right now, emacs kill-ring is not very big, less than 10 items, so I can see all of them using `M-y`, and the most recent one, after several cut-and- paste operations none of them emacs related, is still "test123". And so now I do the converse operation and that works, and after that copying from terminal to emacs works again. Bottom line, it seems org-mode independent. > > (note that I don't have emacs system wide, only the emacs 29.0.50 build > > from source, so there can be no conflict between two emacs) > > > > > > Also, I understand your point, but the fact that the copying is > > > > working > > > > or > > > > not working, in that direction, specifically, after using `xdg-open > > > > "org- > > > > protocol://store-link?url=URL&title=TITLE"`, etc... > > > > Is really a detail in what is hindering the workflow there. > > > > > > It seems that you don't (: To clarify, I am not trying to find a > > > workaround for you yet, but trying to figure out if what you observe is > > > a Emacs bug, an Org mode bug, or not bug at all. > > > > Yeah, sorry about that. > > > > > Best, > > > Ihor
