[vim/vim] feat: support for wayland ext and wlr data control protocols (PR #17097)

180 views
Skip to first unread message

Foxe Chen

unread,
Apr 11, 2025, 10:12:54 PMApr 11
to vim/vim, Subscribed

Should fix #5157. There are still some things that I want to mention:

  1. Not confident on how to implement the tests for Wayland? Looking at the existing tests for the X11 clipboard functionality, it seems like it uses the existing server, but in Wayland, the compositor may not support all the protocols we need. Or should we just accept that and only run tests if the compositor supports it? Another method is creating a new wayland compositor process, but I'm not sure if that is better.
  2. The X11 code seems to have memory leaks, such as when xrestore is ran. I am not sure if this is already known and flagged as expected.
  3. Not sure if my implementation for the Wayland feature in the configure.ac file is the best.
  4. This PR is pretty big for a newbie like me, not sure if the way I implemented this feature is how you do it around here.

Overall, since Wayland uses the same model as X11 when dealing with selections/clipboard, the new code fit pretty smoothly. Unfortunately, this PR doesn't work for GNOME, since they don't provide a way for external clients to access the selection/clipboard. This is my first time developing with Wayland, so I hope my code is good enough :P

Thanks,


You can view, comment on, or merge this pull request online at:

  https://github.com/vim/vim/pull/17097

Commit Summary

  • 1c26845 implement support for ext and wlr data control protocols

File Changes

(52 files)

Patch Links:


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097@github.com>

Foxe Chen

unread,
Apr 11, 2025, 10:23:07 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/1c26845757c965679d083ebeae84ec762c35369f/after/d18817c7f407aabcd0a3cdfa7d9a81afcb5a50df@github.com>

Foxe Chen

unread,
Apr 11, 2025, 10:29:12 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/d18817c7f407aabcd0a3cdfa7d9a81afcb5a50df/after/2f68eef2b395b99fc6b32f9d4cdc7502dbe395e5@github.com>

Foxe Chen

unread,
Apr 11, 2025, 10:43:47 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/2f68eef2b395b99fc6b32f9d4cdc7502dbe395e5/after/ad9759865b262c2a8662d14bf29f4faa20cf4c8e@github.com>

Foxe Chen

unread,
Apr 11, 2025, 10:49:43 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/ad9759865b262c2a8662d14bf29f4faa20cf4c8e/after/9de565a422218222ca0c0deef43f788f20c836cb@github.com>

Foxe Chen

unread,
Apr 11, 2025, 10:54:47 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/9de565a422218222ca0c0deef43f788f20c836cb/after/d809b5b1d26a88a1f15005e4e06ad99139f7e7f5@github.com>

Foxe Chen

unread,
Apr 11, 2025, 10:56:28 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/d809b5b1d26a88a1f15005e4e06ad99139f7e7f5/after/f9fac09cc73124fdabcd61b5ac822c0190bb68ce@github.com>

Foxe Chen

unread,
Apr 11, 2025, 10:59:00 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/f9fac09cc73124fdabcd61b5ac822c0190bb68ce/after/502afc4be9c54cfbcb265c6c92f0fd2bb4dd382f@github.com>

Foxe Chen

unread,
Apr 11, 2025, 11:08:47 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/502afc4be9c54cfbcb265c6c92f0fd2bb4dd382f/after/4032f212c22505fdd91b89909b2ccbf1f54f9507@github.com>

Foxe Chen

unread,
Apr 11, 2025, 11:23:09 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/4032f212c22505fdd91b89909b2ccbf1f54f9507/after/5f18d5b96f2154a01b616b54a23e4e1621b8f658@github.com>

Foxe Chen

unread,
Apr 11, 2025, 11:33:44 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/5f18d5b96f2154a01b616b54a23e4e1621b8f658/after/fe72c495c33778e9082d350e653074c77ce14e75@github.com>

Foxe Chen

unread,
Apr 11, 2025, 11:50:12 PMApr 11
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/fe72c495c33778e9082d350e653074c77ce14e75/after/3ae5e0742cf7588a5f2769f7b684f98d24b8993c@github.com>

Foxe Chen

unread,
Apr 12, 2025, 12:06:25 AMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/3ae5e0742cf7588a5f2769f7b684f98d24b8993c/after/12ee25e0761e3bb043cfb0d652c5c3c686752166@github.com>

Foxe Chen

unread,
Apr 12, 2025, 12:19:42 AMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/12ee25e0761e3bb043cfb0d652c5c3c686752166/after/16c31f2f3df3af1baac7fd28d880f5dd2379912e@github.com>

Foxe Chen

unread,
Apr 12, 2025, 12:31:48 AMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/16c31f2f3df3af1baac7fd28d880f5dd2379912e/after/145887f1b32e8856faccaca320a8842658455a5d@github.com>

Foxe Chen

unread,
Apr 12, 2025, 12:37:05 AMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/145887f1b32e8856faccaca320a8842658455a5d/after/3c24e931420798ca390fc8d86c79c1da9e35710f@github.com>

Christian Brabandt

unread,
Apr 12, 2025, 12:28:17 PMApr 12
to vim/vim, Subscribed

No worries, the CI test errors were unrelated and should have been fixed in master. Can you please rebase on top of master?


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2798895751@github.com>

chrisbra left a comment (vim/vim#17097)

No worries, the CI test errors were unrelated and should have been fixed in master. Can you please rebase on top of master?


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2798895751@github.com>

Foxe Chen

unread,
Apr 12, 2025, 1:00:41 PMApr 12
to vim/vim, Push

@64-bitman pushed 2 commits.

  • ea3af3d implement support for ext and wlr data control protocols
  • 8ae28ec fix stuff

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/3c24e931420798ca390fc8d86c79c1da9e35710f/after/8ae28ece922629f0472ac4878ee245c1105d7ed1@github.com>

Foxe Chen

unread,
Apr 12, 2025, 2:16:48 PMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/8ae28ece922629f0472ac4878ee245c1105d7ed1/after/b098c7d78793c255619d7eb11295cd4f2be1404a@github.com>

Foxe Chen

unread,
Apr 12, 2025, 2:20:07 PMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/b098c7d78793c255619d7eb11295cd4f2be1404a/after/14078eb5786f5658ddbb407864585070b42fedd4@github.com>

Foxe Chen

unread,
Apr 12, 2025, 10:53:44 PMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/14078eb5786f5658ddbb407864585070b42fedd4/after/015b6c3a71405aff923e962c3fcde076a9a6a75b@github.com>

Foxe Chen

unread,
Apr 12, 2025, 11:01:19 PMApr 12
to vim/vim, Subscribed

I think just starting a new Wayland compositor process within the Vim test instance would be the best way for the tests. So Niri will be the best fit since it supports both data control protocols.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2799563864@github.com>

64-bitman left a comment (vim/vim#17097)

I think just starting a new Wayland compositor process within the Vim test instance would be the best way for the tests. So Niri will be the best fit since it supports both data control protocols.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2799563864@github.com>

Foxe Chen

unread,
Apr 12, 2025, 11:11:16 PMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/015b6c3a71405aff923e962c3fcde076a9a6a75b/after/6356b4803163834ad654a39797d08252ccaa643a@github.com>

Foxe Chen

unread,
Apr 12, 2025, 11:27:28 PMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 10a388a free up stuff used by previous method after restoreclip

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/6356b4803163834ad654a39797d08252ccaa643a/after/10a388ae019885a031c964af831c8c1c61d1572a@github.com>

Foxe Chen

unread,
Apr 12, 2025, 11:33:35 PMApr 12
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 8940aba free up stuff used by previous method after restoreclip

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/10a388ae019885a031c964af831c8c1c61d1572a/after/8940ababf688a65f598865a3cf57baf2f51d31c5@github.com>

Foxe Chen

unread,
Apr 13, 2025, 12:26:41 AMApr 13
to vim/vim, Push

@64-bitman pushed 1 commit.

  • e7c8a3f free up stuff used by previous method after restoreclip

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/8940ababf688a65f598865a3cf57baf2f51d31c5/after/e7c8a3fa5e135860210115bd4998bf316494a0c4@github.com>

Foxe Chen

unread,
Apr 13, 2025, 12:50:33 AMApr 13
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/e7c8a3fa5e135860210115bd4998bf316494a0c4/after/76c1a1338a1f4c9a5c9a341f6517fe7c85374be3@github.com>

Foxe Chen

unread,
Apr 13, 2025, 1:08:30 AMApr 13
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/76c1a1338a1f4c9a5c9a341f6517fe7c85374be3/after/22c30ca94611bb24c31af9727acae227a810789f@github.com>

Foxe Chen

unread,
Apr 13, 2025, 1:17:38 AMApr 13
to vim/vim, Subscribed

@chrisbra Would it be possible for the CI tests to have a Wayland compositor installed? Current tests use Niri, but requires a really new version (v25.02), not sure if that is in the repos yet.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2799681418@github.com>

64-bitman left a comment (vim/vim#17097)

@chrisbra Would it be possible for the CI tests to have a Wayland compositor installed? Current tests use Niri, but requires a really new version (v25.02), not sure if that is in the repos yet.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2799681418@github.com>

Christian Brabandt

unread,
Apr 13, 2025, 12:15:40 PMApr 13
to vim/vim, Subscribed

Should be fine to add, but probably depends on how much effort it is to install Niri (v25.02).


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2800014584@github.com>

chrisbra left a comment (vim/vim#17097)

Should be fine to add, but probably depends on how much effort it is to install Niri (v25.02).


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2800014584@github.com>

Foxe Chen

unread,
Apr 15, 2025, 1:31:49 PMApr 15
to vim/vim, Push

@64-bitman pushed 17 commits.

  • ddefa19 runtime(new-tutor): update tutor and correct comandline completion
  • 02e46b9 patch 9.1.1297: Ctrl-D scrolling can get stuck
  • 3adfb1d patch 9.1.1298: define_function() is too long
  • e4e3286 runtime(gleam): update Maintainer and filetype options
  • d90fa1c runtime(doc): update options.txt and clarify 'wildmode' further
  • fc2ede2 CI: install xcode 16.3 on macos-15 runner
  • c0c5181 patch 9.1.1299: filetype: mbsyncrc files are not recognized
  • ee77927 runtime(doc): update enum helptext
  • 1cd11d5 patch 9.1.1300: wrong detection of -inf
  • 86bafe8 patch 9.1.1301: completion: cannot configure completion functions with 'complete'
  • c78b2f4 patch 9.1.1302: Coverity warns about using uninitialized value
  • a050695 patch 9.1.1303: missing out-of-memory check in linematch.c
  • 8280735 runtime(netrw): upstream snapshot of v180
  • e5a44b3 patch 9.1.1304: filetype: some man files are not recognized
  • 6c2b9ff patch 9.1.1305: completion menu active after switching windows/tabs
  • a5816c4 patch 9.1.1306: completion menu rendering can be improved
  • 4c9661f patch 9.1.1307: make syntax does not reliably detect different flavors


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/22c30ca94611bb24c31af9727acae227a810789f/after/4c9661f9fd9100d194a334098340c3da31d4ba2d@github.com>

Foxe Chen

unread,
Apr 15, 2025, 1:32:54 PMApr 15
to vim/vim, Push

@64-bitman pushed 0 commits.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/4c9661f9fd9100d194a334098340c3da31d4ba2d/after/22c30ca94611bb24c31af9727acae227a810789f@github.com>

Foxe Chen

unread,
Apr 16, 2025, 11:34:38 PMApr 16
to vim/vim, Push

@64-bitman pushed 7 commits.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/9fe8461c18a9546d186739dc84cb08aeeafe7d2a/after/3bd63be416c830375763b10c1c600b0e501bfda3@github.com>

Foxe Chen

unread,
Apr 17, 2025, 7:18:47 PMApr 17
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 089c855 fix seg fault when $WAYLAND_DISPLAY doesn't exist

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/3bd63be416c830375763b10c1c600b0e501bfda3/after/089c855fc1ea1f370476ff8008506d8962e8e602@github.com>

Foxe Chen

unread,
Apr 18, 2025, 2:43:17 PMApr 18
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/089c855fc1ea1f370476ff8008506d8962e8e602/after/7d23021450612a042e8afee485a47b4aec3d57bd@github.com>

Foxe Chen

unread,
Apr 18, 2025, 2:44:08 PMApr 18
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/7d23021450612a042e8afee485a47b4aec3d57bd/after/88785a218bcfa82d184eafd6f84665f6e0062743@github.com>

Foxe Chen

unread,
Apr 18, 2025, 4:40:51 PMApr 18
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 4578d4b Make libwayland log handler use ch_log

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/853db45e9905ae784da6554c01e49fe42cbd282b/after/4578d4b3aae1573065f0b6e6a4e300a3daa0c75e@github.com>

Foxe Chen

unread,
Apr 18, 2025, 4:55:26 PMApr 18
to vim/vim, Push

@64-bitman pushed 1 commit.

  • ffb72f1 Make libwayland log handler use ch_log

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/4578d4b3aae1573065f0b6e6a4e300a3daa0c75e/after/ffb72f133c6cb518a7815499b0e0953a34b8c81a@github.com>

Foxe Chen

unread,
Apr 18, 2025, 5:02:49 PMApr 18
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 178dc02 Make libwayland log handler use ch_log

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/ffb72f133c6cb518a7815499b0e0953a34b8c81a/after/178dc0249aebb9a8f568800c68074172bd09f3b8@github.com>

Foxe Chen

unread,
Apr 18, 2025, 5:04:48 PMApr 18
to vim/vim, Subscribed

@64-bitman commented on this pull request.


In src/os_unix.c:

> +#endif
+}
+
+
+/*
+ * Redirect libwayland logging to use ch_log instead.
+ */
+static void vwl_log_handler(const char *fmt, va_list args) {
+    size_t len = STRLEN(fmt) + STRLEN("LIBWAYLAND: ") + 1;
+    char *format = alloc(len);
+
+    if (format == NULL)
+	return;
+    // Subtract one to remove newline that libwayland puts
+    vim_snprintf(format, len - 1, "LIBWAYLAND: %s", fmt);
+    ch_vlog(NULL, format, args);

Looks fine to me.


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/review/2779417694@github.com>

Foxe Chen

unread,
Apr 18, 2025, 7:16:27 PMApr 18
to vim/vim, Subscribed

Would the CI test changes have to be included in a separate commit so it can be put to use for this PR?


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2816337119@github.com>

64-bitman left a comment (vim/vim#17097)

Would the CI test changes have to be included in a separate commit so it can be put to use for this PR?


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2816337119@github.com>

Foxe Chen

unread,
Apr 18, 2025, 7:16:48 PMApr 18
to vim/vim, Subscribed

Should be fine to add, but probably depends on how much effort it is to install Niri (v25.02).

Would the CI test changes have to be included in a separate commit so it can be put to use for this PR?


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2816337325@github.com>

64-bitman left a comment (vim/vim#17097)

Should be fine to add, but probably depends on how much effort it is to install Niri (v25.02).

Would the CI test changes have to be included in a separate commit so it can be put to use for this PR?


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2816337325@github.com>

Christian Brabandt

unread,
Apr 19, 2025, 6:04:36 AMApr 19
to vim/vim, Subscribed

Would the CI test changes have to be included in a separate PR so it can be put to use for this PR?

We don't necessarily have to include it as part of this PR. A separate PR could be used for the tests. As long as we try to add tests of course :) Thanks!


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2816639265@github.com>

chrisbra left a comment (vim/vim#17097)

Would the CI test changes have to be included in a separate PR so it can be put to use for this PR?

We don't necessarily have to include it as part of this PR. A separate PR could be used for the tests. As long as we try to add tests of course :) Thanks!


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2816639265@github.com>

Foxe Chen

unread,
Apr 19, 2025, 8:14:43 PMApr 19
to vim/vim, Subscribed

@chrisbra What would be your opinion on this?

Thing is with GNOME is that it needs something like a focused window to work, which terminal vim obviously doesn't work. wl-clipboard gets around this by focus-stealing (creating an invisible window and doing all the stuff it needs to before closing it). This introduces weird quirks though: bugaevc/wl-clipboard#90, bugaevc/wl-clipboard#91, bugaevc/wl-clipboard#31, bugaevc/wl-clipboard#12. Unless these are only specific to wl-clipboard, which I think is highly unlikely, this is a pretty hacky way, not sure if it belongs in Vim.

I wouldn't mind implementing the focus stealing hack that wl-clipboard does. Thanks.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2816915838@github.com>

64-bitman left a comment (vim/vim#17097)

@chrisbra What would be your opinion on this?

Thing is with GNOME is that it needs something like a focused window to work, which terminal vim obviously doesn't work. wl-clipboard gets around this by focus-stealing (creating an invisible window and doing all the stuff it needs to before closing it). This introduces weird quirks though: bugaevc/wl-clipboard#90, bugaevc/wl-clipboard#91, bugaevc/wl-clipboard#31, bugaevc/wl-clipboard#12. Unless these are only specific to wl-clipboard, which I think is highly unlikely, this is a pretty hacky way, not sure if it belongs in Vim.

I wouldn't mind implementing the focus stealing hack that wl-clipboard does. Thanks.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2816915838@github.com>

Christian Brabandt

unread,
Apr 20, 2025, 4:25:03 AMApr 20
to vim/vim, Subscribed

Well, it sounds like a big hack, but if this is what users expect and you wouldn't mind implementing it, than that is probably what we need to do. Thanks for working on that!


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2817059745@github.com>

chrisbra left a comment (vim/vim#17097)

Well, it sounds like a big hack, but if this is what users expect and you wouldn't mind implementing it, than that is probably what we need to do. Thanks for working on that!


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2817059745@github.com>

Foxe Chen

unread,
Apr 20, 2025, 2:39:55 PMApr 20
to vim/vim, Push

@64-bitman pushed 10 commits.

  • 4c51218 implement support for ext and wlr data control protocols
  • 8583c21 fix stuff
  • 3137f46 update docs
  • 5a27c7f fix segfault
  • a7c7551 update syntax files
  • 41756c5 free up stuff used by previous method after restoreclip
  • 033ee35 Add tests
  • 1791f5e fix seg fault when $WAYLAND_DISPLAY doesn't exist
  • 977828b fix warnings
  • 2eb3299 Make libwayland log handler use ch_log


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/178dc0249aebb9a8f568800c68074172bd09f3b8/after/2eb3299d3507b7f0fffb9f2eaf2205a6b16f898b@github.com>

Maxim Kim

unread,
Apr 21, 2025, 8:18:02 PMApr 21
to vim/vim, Subscribed

I wouldn't mind implementing the focus stealing hack that wl-clipboard does. Thanks.

Would it be the same hack for gui vim?


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2819755611@github.com>

habamax left a comment (vim/vim#17097)

I wouldn't mind implementing the focus stealing hack that wl-clipboard does. Thanks.

Would it be the same hack for gui vim?


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2819755611@github.com>

Foxe Chen

unread,
Apr 21, 2025, 10:27:46 PMApr 21
to vim/vim, Subscribed

I wouldn't mind implementing the focus stealing hack that wl-clipboard does. Thanks.

Would it be the same hack for gui vim?

With gui vim it has an actual window that the compositor can know if its focused or not, so it doesn't need any focus stealing hacks. This PR is only relevant for terminal vim


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2819896860@github.com>

64-bitman left a comment (vim/vim#17097)

I wouldn't mind implementing the focus stealing hack that wl-clipboard does. Thanks.

Would it be the same hack for gui vim?

With gui vim it has an actual window that the compositor can know if its focused or not, so it doesn't need any focus stealing hacks. This PR is only relevant for terminal vim


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2819896860@github.com>

Maxim Kim

unread,
Apr 21, 2025, 10:40:07 PMApr 21
to vim/vim, Subscribed

With gui vim it has an actual window that the compositor can know if its focused or not, so it doesn't need any focus stealing hacks. This PR is only relevant for terminal vim, right now I'm rewriting the wayland code since the current design is clunky.

Well, yes. Sorry, my actual question should have been, would gui vim support clipboard in Wayland? And it looks like no as this PR is only for terminal vim.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2819910904@github.com>

habamax left a comment (vim/vim#17097)

With gui vim it has an actual window that the compositor can know if its focused or not, so it doesn't need any focus stealing hacks. This PR is only relevant for terminal vim, right now I'm rewriting the wayland code since the current design is clunky.

Well, yes. Sorry, my actual question should have been, would gui vim support clipboard in Wayland? And it looks like no as this PR is only for terminal vim.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2819910904@github.com>

Maxim Kim

unread,
Apr 21, 2025, 10:43:26 PMApr 21
to vim/vim, Subscribed

I was hoping that wlr and ext data control protocols would also "fix" gui vim clipboard in Wayland (KDE, sway).


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2819914066@github.com>

habamax left a comment (vim/vim#17097)

I was hoping that wlr and ext data control protocols would also "fix" gui vim clipboard in Wayland (KDE, sway).


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2819914066@github.com>

Foxe Chen

unread,
Apr 22, 2025, 12:00:54 AMApr 22
to vim/vim, Subscribed

I was hoping that wlr and ext data control protocols would also "fix" gui vim clipboard in Wayland (KDE, sway).

Shouldn't the gtk library handle the clipboard and stuff?


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2820000530@github.com>

64-bitman left a comment (vim/vim#17097)

I was hoping that wlr and ext data control protocols would also "fix" gui vim clipboard in Wayland (KDE, sway).

Shouldn't the gtk library handle the clipboard and stuff?


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2820000530@github.com>

Maxim Kim

unread,
Apr 22, 2025, 12:14:41 AMApr 22
to vim/vim, Subscribed

I was hoping that wlr and ext data control protocols would also "fix" gui vim clipboard in Wayland (KDE, sway).

Shouldn't the gtk library handle the clipboard and stuff?

It probably should, but vim with GVIM_ENABLE_WAYLAND doesn't work with clipbord in pure wayland environment as far as I remember.


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2820015624@github.com>

habamax left a comment (vim/vim#17097)

I was hoping that wlr and ext data control protocols would also "fix" gui vim clipboard in Wayland (KDE, sway).

Shouldn't the gtk library handle the clipboard and stuff?

It probably should, but vim with GVIM_ENABLE_WAYLAND doesn't work with clipbord in pure wayland environment as far as I remember.


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2820015624@github.com>

Maxim Kim

unread,
Apr 22, 2025, 12:15:56 AMApr 22
to vim/vim, Subscribed

Indeed, https://github.com/vim/vim/blob/31b78cce6e6412cada49ca994f6665ef4acec792/src/gui_gtk_x11.c#L1736


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2820016767@github.com>

habamax left a comment (vim/vim#17097)

Indeed, https://github.com/vim/vim/blob/31b78cce6e6412cada49ca994f6665ef4acec792/src/gui_gtk_x11.c#L1736


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2820016767@github.com>

Foxe Chen

unread,
Apr 22, 2025, 12:19:42 AMApr 22
to vim/vim, Subscribed

Thats unfortunate. I don't think it's a good idea to handle the wayland selection directly when using gui vim, the gui library should handle that. Vim does this (only uses the x11 library for setting the selection when not in gui mode)


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2820020390@github.com>

64-bitman left a comment (vim/vim#17097)

Thats unfortunate. I don't think it's a good idea to handle the wayland selection directly when using gui vim, the gui library should handle that. Vim does this (only uses the x11 library for setting the selection when not in gui mode)


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/c2820020390@github.com>

Foxe Chen

unread,
Apr 27, 2025, 7:07:27 PMApr 27
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 05dae38 Merge branch 'master' into wayland_clipboard


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/2eb3299d3507b7f0fffb9f2eaf2205a6b16f898b/after/05dae38668eba86c83e542368b46cd6177aa0704@github.com>

Foxe Chen

unread,
Apr 27, 2025, 7:08:40 PMApr 27
to vim/vim, Push

@64-bitman pushed 0 commits.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/05dae38668eba86c83e542368b46cd6177aa0704/after/2eb3299d3507b7f0fffb9f2eaf2205a6b16f898b@github.com>

Foxe Chen

unread,
Apr 27, 2025, 7:13:20 PMApr 27
to vim/vim, Push

@64-bitman pushed 1 commit.

  • b9db387 Make libwayland log handler use ch_log

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/2eb3299d3507b7f0fffb9f2eaf2205a6b16f898b/after/b9db387f40feb9662bc9587b4cea7a30e9863a86@github.com>

Foxe Chen

unread,
Apr 30, 2025, 4:45:03 PMApr 30
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/a754b26af30fdb535ef2de0ae53172f9f58b4ab2/after/f4d127b921ed040fc2135275104f75e9057a2556@github.com>

Foxe Chen

unread,
Apr 30, 2025, 4:46:40 PMApr 30
to vim/vim, Push

@64-bitman pushed 0 commits.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/f4d127b921ed040fc2135275104f75e9057a2556/after/a754b26af30fdb535ef2de0ae53172f9f58b4ab2@github.com>

Foxe Chen

unread,
May 3, 2025, 1:51:13 AMMay 3
to vim/vim, Push

@64-bitman pushed 9 commits.

  • 3be269a implement support for ext and wlr data control protocols
  • d6fb4dd fix stuff
  • f25f78f update docs
  • 96b5f02 fix segfault
  • 0c11d49 free up stuff used by previous method after restoreclip
  • af23767 Add tests
  • c415f33 fix seg fault when $WAYLAND_DISPLAY doesn't exist
  • ff1a6b0 fix warnings
  • 860ff79 Make libwayland log handler use ch_log

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/a754b26af30fdb535ef2de0ae53172f9f58b4ab2/after/860ff79b11e8e4ba65bdce9e2a56ce475e3fb09c@github.com>

Foxe Chen

unread,
May 5, 2025, 11:20:56 PMMay 5
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/860ff79b11e8e4ba65bdce9e2a56ce475e3fb09c/after/bb6abee21107a026288d002b55aba9c8ca4d47cb@github.com>

Foxe Chen

unread,
May 5, 2025, 11:22:15 PMMay 5
to vim/vim, Push

@64-bitman pushed 0 commits.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/bb6abee21107a026288d002b55aba9c8ca4d47cb/after/860ff79b11e8e4ba65bdce9e2a56ce475e3fb09c@github.com>

Foxe Chen

unread,
May 6, 2025, 12:54:36 AMMay 6
to vim/vim, Push

@64-bitman pushed 9 commits.

  • 81cfe0c implement support for ext and wlr data control protocols
  • dd9402e fix stuff
  • 90787ca update docs
  • 0cb05e7 fix segfault
  • b72211a free up stuff used by previous method after restoreclip
  • 49bdf6d Add tests
  • 3f7b870 fix seg fault when $WAYLAND_DISPLAY doesn't exist
  • cabc1a8 fix warnings
  • 0c8f7f7 Make libwayland log handler use ch_log

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/860ff79b11e8e4ba65bdce9e2a56ce475e3fb09c/after/0c8f7f7d7c7da2be91bd0b45f8d56d91b2ffabc1@github.com>

Foxe Chen

unread,
May 9, 2025, 1:14:49 AMMay 9
to vim/vim, Push

@64-bitman pushed 1 commit.

  • f11dfa7 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/0c8f7f7d7c7da2be91bd0b45f8d56d91b2ffabc1/after/f11dfa738070ae20a6ae3fe2e1ddcce5b84fd20e@github.com>

Foxe Chen

unread,
May 9, 2025, 1:14:52 AMMay 9
to vim/vim, Push

@64-bitman pushed 10 commits.

  • f74da59 implement support for ext and wlr data control protocols
  • 56b8c33 fix stuff
  • d5ff884 update docs
  • 8d4b2fa fix segfault
  • 4a88c64 free up stuff used by previous method after restoreclip
  • 1bbea32 Add tests
  • 5cca27b fix seg fault when $WAYLAND_DISPLAY doesn't exist
  • 4a83b22 fix warnings
  • 30f902f Make libwayland log handler use ch_log
  • 8aeee7c refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/f11dfa738070ae20a6ae3fe2e1ddcce5b84fd20e/after/8aeee7ce9b10a9d4b39d92bfa6a54bc1a6801d87@github.com>

Foxe Chen

unread,
May 9, 2025, 1:17:13 AMMay 9
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 4e02159 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/8aeee7ce9b10a9d4b39d92bfa6a54bc1a6801d87/after/4e02159aca9c616e03d4f4e8cf7957d5fd0cc707@github.com>

Foxe Chen

unread,
May 10, 2025, 2:37:29 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • ba4bd33 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/4e02159aca9c616e03d4f4e8cf7957d5fd0cc707/after/ba4bd336c0cc150b923bb34b7541c077982344e0@github.com>

Foxe Chen

unread,
May 10, 2025, 3:55:03 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • bed298b refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/ba4bd336c0cc150b923bb34b7541c077982344e0/after/bed298b7dc42c64853a25697083ebb3a94b76cf3@github.com>

Foxe Chen

unread,
May 10, 2025, 3:57:34 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 424cb51 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/bed298b7dc42c64853a25697083ebb3a94b76cf3/after/424cb511995e1fd6a529a9701ece08adeeaf8894@github.com>

Foxe Chen

unread,
May 10, 2025, 4:01:01 PMMay 10
to vim/vim, Subscribed

@64-bitman commented on this pull request.


In src/wayland.c:

> +}
+
+/*
+ * Redirect libwayland logging to use ch_log + semsg instead.
+ */
+    static void
+vwl_log_handler(const char *fmt, va_list args)
+{
+    size_t len = STRLEN(fmt) + STRLEN("LIBWAYLAND: ") + 1;
+    char *format = alloc(len);
+
+    if (format == NULL)
+	return;
+    // Subtract one to remove newline that libwayland puts
+    vim_snprintf(format, len - 1, "libwayland internal error: %s", fmt);
+    ch_vlog(NULL, format, args);

irrelevant unless libwayland is malicious


Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/review/2831056081@github.com>

Foxe Chen

unread,
May 10, 2025, 4:01:19 PMMay 10
to vim/vim, Subscribed

@64-bitman commented on this pull request.


In src/wayland.c:

> +
+/*
+ * Redirect libwayland logging to use ch_log + semsg instead.
+ */
+    static void
+vwl_log_handler(const char *fmt, va_list args)
+{
+    size_t len = STRLEN(fmt) + STRLEN("LIBWAYLAND: ") + 1;
+    char *format = alloc(len);
+
+    if (format == NULL)
+	return;
+    // Subtract one to remove newline that libwayland puts
+    vim_snprintf(format, len - 1, "libwayland internal error: %s", fmt);
+    ch_vlog(NULL, format, args);
+    semsg(format, args);

Irrelevant unless libwayland is malicious


Reply to this email directly, view it on GitHub, or unsubscribe.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/review/2831056121@github.com>

Foxe Chen

unread,
May 10, 2025, 4:14:12 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 5ccd351 refactor wayland code (in progress)


View it on GitHub or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/424cb511995e1fd6a529a9701ece08adeeaf8894/after/5ccd351768d9e202c5d1c819a4e459ce99e5eed9@github.com>

Foxe Chen

unread,
May 10, 2025, 9:58:09 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • f3bb1e7 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/5ccd351768d9e202c5d1c819a4e459ce99e5eed9/after/f3bb1e7627398faba6d334318cb5c8b9d3540717@github.com>

Foxe Chen

unread,
May 10, 2025, 10:18:01 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • aeb0213 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/f3bb1e7627398faba6d334318cb5c8b9d3540717/after/aeb0213df5c33c8d4a70eb186d8d60a950aca063@github.com>

Foxe Chen

unread,
May 10, 2025, 10:21:58 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • fa4f631 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/aeb0213df5c33c8d4a70eb186d8d60a950aca063/after/fa4f6317e4f4a4d7427759c984116a03468f5847@github.com>

Foxe Chen

unread,
May 10, 2025, 10:50:16 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 5eb7d63 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/153bfc0f99eb4ebac527e048ddea896616332f3f/after/5eb7d63165e47fb41c461b201691b510e8e7037d@github.com>

Foxe Chen

unread,
May 10, 2025, 11:28:22 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 94731a6 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/5eb7d63165e47fb41c461b201691b510e8e7037d/after/94731a629c327fa0090bdd720b692d67e1a2cff0@github.com>

Foxe Chen

unread,
May 10, 2025, 11:34:13 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 174ac81 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/94731a629c327fa0090bdd720b692d67e1a2cff0/after/174ac81873fc0993ec1fe49e1f4fd903a207d6ea@github.com>

Foxe Chen

unread,
May 10, 2025, 11:41:47 PMMay 10
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 9ec0d91 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/174ac81873fc0993ec1fe49e1f4fd903a207d6ea/after/9ec0d9133cd9717ed9147a4c2c397a3cc61819b7@github.com>

Foxe Chen

unread,
May 11, 2025, 12:45:14 AMMay 11
to vim/vim, Push

@64-bitman pushed 1 commit.

  • f6db10e refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/9ec0d9133cd9717ed9147a4c2c397a3cc61819b7/after/f6db10e7862b4486e29df8a0b85d6f995d0321c0@github.com>

Foxe Chen

unread,
May 11, 2025, 12:48:02 AMMay 11
to vim/vim, Push

@64-bitman pushed 1 commit.

  • f1b2ef7 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/f6db10e7862b4486e29df8a0b85d6f995d0321c0/after/f1b2ef7f21cb8a056928baa3a7c3737d83890b0c@github.com>

Foxe Chen

unread,
May 11, 2025, 1:04:25 PMMay 11
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 8c95aba refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/f1b2ef7f21cb8a056928baa3a7c3737d83890b0c/after/8c95aba4f806ed8d8fb26add96209fd7980e0854@github.com>

Foxe Chen

unread,
May 11, 2025, 1:05:35 PMMay 11
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 85d0b41 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/8c95aba4f806ed8d8fb26add96209fd7980e0854/after/85d0b415d68ab443747625cc0017d18156e875be@github.com>

Foxe Chen

unread,
May 11, 2025, 1:09:36 PMMay 11
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 7d0823f refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/85d0b415d68ab443747625cc0017d18156e875be/after/7d0823fb8e659a9c03bd3727e6d2de677dd53da3@github.com>

Foxe Chen

unread,
May 11, 2025, 1:57:59 PMMay 11
to vim/vim, Push

@64-bitman pushed 1 commit.

  • f9cc9b1 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/7d0823fb8e659a9c03bd3727e6d2de677dd53da3/after/f9cc9b14bb4904df663d9016e0b72dd16ac79ab4@github.com>

Foxe Chen

unread,
May 12, 2025, 12:42:10 AMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

  • 3ead17f refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/f9cc9b14bb4904df663d9016e0b72dd16ac79ab4/after/3ead17fe2c8cab1fe0bf99a97e7e423266c4db1e@github.com>

Foxe Chen

unread,
May 12, 2025, 12:50:42 AMMay 12
to vim/vim, Push

@64-bitman pushed 10 commits.

  • b534310 implement support for ext and wlr data control protocols
  • 4aa49f3 fix stuff
  • 7fc15ab update docs
  • 2b5c407 fix segfault
  • 003ec90 free up stuff used by previous method after restoreclip
  • 6c4c5bb Add tests
  • d82c6fc fix seg fault when $WAYLAND_DISPLAY doesn't exist
  • 44a36e5 fix warnings
  • fa53e99 Make libwayland log handler use ch_log
  • 33710c2 refactor wayland code (in progress)

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/3ead17fe2c8cab1fe0bf99a97e7e423266c4db1e/after/33710c2ac8546523b4218c16fc5e157ec4cf0fb4@github.com>

Foxe Chen

unread,
May 12, 2025, 4:29:55 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/33710c2ac8546523b4218c16fc5e157ec4cf0fb4/after/1ba052b1e1c5dd38623b0c96a60b1520e4ddbdb1@github.com>

Foxe Chen

unread,
May 12, 2025, 4:40:59 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/c36cb54f0b8df68f6e8d7b6afe357a6f18dc741a/after/2a7666c4af501485f8fe9889f888d22f1baa7ed7@github.com>

Foxe Chen

unread,
May 12, 2025, 4:41:30 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/2a7666c4af501485f8fe9889f888d22f1baa7ed7/after/cd61491dc483f8c0e7f2f9f91c4f33195eb9da30@github.com>

Foxe Chen

unread,
May 12, 2025, 6:51:27 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/cd61491dc483f8c0e7f2f9f91c4f33195eb9da30/after/30b7b8f0cf5dae5be8ce5fd892bb95d2a0b58d31@github.com>

Foxe Chen

unread,
May 12, 2025, 8:17:20 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/30b7b8f0cf5dae5be8ce5fd892bb95d2a0b58d31/after/326212da2a91577aba7e0652e28f0b18f931d22f@github.com>

Foxe Chen

unread,
May 12, 2025, 8:23:00 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/326212da2a91577aba7e0652e28f0b18f931d22f/after/236c0e1fe23563fbd60b671a36ef555baff41efa@github.com>

Foxe Chen

unread,
May 12, 2025, 10:57:26 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/236c0e1fe23563fbd60b671a36ef555baff41efa/after/221d6ea34d11aa7997b76682482b5e4f17572dc9@github.com>

Foxe Chen

unread,
May 12, 2025, 11:13:45 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/221d6ea34d11aa7997b76682482b5e4f17572dc9/after/a2cc8503a243c3e04975d0b9ce301d038e5bd831@github.com>

Foxe Chen

unread,
May 12, 2025, 11:15:22 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/a2cc8503a243c3e04975d0b9ce301d038e5bd831/after/9c0c8c861aa8d2ff9380747ec672531fb8dfe0bc@github.com>

Foxe Chen

unread,
May 12, 2025, 11:16:57 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/9c0c8c861aa8d2ff9380747ec672531fb8dfe0bc/after/8ffa11f44f88bd98ce6537387bd393b55aaeefd8@github.com>

Foxe Chen

unread,
May 12, 2025, 11:28:56 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/8ffa11f44f88bd98ce6537387bd393b55aaeefd8/after/78dc1018bc55aece485ca12382784a46e2ebc6ed@github.com>

Foxe Chen

unread,
May 12, 2025, 11:33:53 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/78dc1018bc55aece485ca12382784a46e2ebc6ed/after/9ba110753e0b0a116b51c3bb6e065363448a9034@github.com>

Foxe Chen

unread,
May 12, 2025, 11:37:37 PMMay 12
to vim/vim, Push

@64-bitman pushed 1 commit.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/pull/17097/before/9ba110753e0b0a116b51c3bb6e065363448a9034/after/82d415be384c32835a7a6e90aa58dca84e43d4c1@github.com>

It is loading more messages.
0 new messages