Error handling for X11

Open
#316 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
desktop

Research direction

Start by tracing the XOpenIM call and the other X11 methods whose failure reasons are currently unavailable. Done means exposing useful error information for these failures, including the reported XOpenIM case, so users can diagnose the cause of a panic.

Written by the indexing model from the issue text.

Description

C - in progress D - hard DS - x11 P - normal S - enhancement

Right now, it's impossible to see failure reasons for a lot of X11 methods. For instance, Alacritty has been getting some reports of panics on XOpenIM failed, and without error info, this is difficult to debug.

Dominant language
Rust
Stars
6.2k
Forks
1.3k
Avg merge
2d 19h
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

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 rust-windowing/winit

All issues in rust-windowing/winit

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.