Wayland support?

Open
#17 4 comments 18 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, linux, node.js

Research direction

Start by reviewing the library's Linux code to understand its current X11 dependency and keyboard-layout behavior. The work is done when the Linux implementation supports Wayland without Xwayland while preserving the module's existing OS keyboard functionality.

Written by the indexing model from the issue text.

Description

enhancement

I was looking at whether I could get vscode running on wayland without xwayland (x11 support). It seems this library is required by vscode and uses X11 on linux. Could the linux code be ported to use something like xkbcommon (I'm not sure if this is the right replacement)? How hard do you think it'd be?

Dominant language
C++
Stars
152
Forks
43
Avg merge
19h 38m
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/node-native-keymap

All issues in microsoft/node-native-keymap

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.