ibus VS flameshot

1.5.29-rc2 was tagged on 9 Nov 2023 [1] and in did not contain "N_("CJK Unified Ideographs Extension I")," in src/ibusunicodegen.h [2].

Commit 228f0a77b2047ade54e132bab69c0c03f0f41aae from 28 Feb 2023 introduced this change instead. It's the same person who tagged 1.5.29-rc2 and committed 228f0a77b2047ade54e132bab69c0c03f0f41aae which is typically an indication the maintainer tar'd their checked out git folder and accidentally included changes not get committed.

[1] https://github.com/ibus/ibus/releases/tag/1.5.29-rc2

[2] https://github.com/ibus/ibus/blob/0ad8e77bd36545974ad8acd0a5...

[2] https://github.com/ibus/ibus/commit/228f0a77b2047ade54e132ba...

On https://github.com/ibus/ibus we can see gtk+ are probably only need for ibus-setup. I would like help to be sure i not miss any step.

I also know input methods work great in Ubuntu (Gnome Wayland) because Gnome supports ibus.

But the article is specifically about incompatibility of input methods among different DEs: Gnome, KDE, wlroots-based environments such as Sway and Hyprland.

After many years, ibus still doesn’t work with wlroots: https://github.com/ibus/ibus/issues/2182

The list of recommended IMEs on Sway are all WIP: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway#...

Most people use fcitx5 with Sway because fcitx5 and Sway both support input method unstable v2. But the article explains that v2 is still not universally supported among wayland DEs, and that’s why it’s problematic.

Have no idea what the daemon does practically, here is the GitHub page.

The F38 beta is currently affected by two (mostly gaming-related) issues that you should be aware of: - https://gitlab.gnome.org/GNOME/mutter/-/issues/2678 -> a lot of SDL-based games have their fullscreen mode broken. The issue is bisected. - https://github.com/ibus/ibus/issues/2480 -> Keyboard input sometimes gets stuck. Issue has already been identified and we're waiting for an ibus release.

Also, to add to what u/Pizza-Driver said, it seems that ibus is not yet interoperable with the protocol used by Wayland display servers based on wlroots.

I meant ctrl+., but it looks like ibus recently changed their emoji input shortcut back to super+., so the gtk emoji picker should be available via ctrl+. again without requiring changes: https://github.com/ibus/ibus/commit/1520c39d0d6036da725fcecd932883be3f3d3575

Looks like it was changed here: https://github.com/ibus/ibus/commit/1520c39d0d6036da725fcecd932883be3f3d3575

For your screenshots simply use Flameshot: https://flameshot.org

First, conceptually this is what I mean: think about when using a good screen-capture/annotation tool like flameshot: you select a region of the screen, and "magic" you can "edit" it, "in situ". No, what I'm talking about wouldn't share any of the same technical underpinnings with the way flameshot works, it would be the live monitor output, not a raster dump of the screen made to look like it's live. And the annotating would be done on a different screen. But as a user, this is pretty similar.

Flameshot is a free and open-source screenshot tool for Linux that allows users to take screenshots of an area, a window or the full screen. It then provides an editor where users can modify the screenshots by drawing on them, adding text, highlighting areas, blurring parts and more. Users can save the screenshots in common image formats like PNG and JPEG, and upload them directly to image hosting sites like Imgur.

I would recommend Flameshot, available on Linux, Windows and Mac.

This https://github.com/flameshot-org/flameshot/issues/1529 mat or may not be an issue for you with Flameshot, but it may be for others. It's solvable if it is an issue by using mandatory access control such as AppArmor or conditional build. Just FYI.

Flameshot viene con todo eso.

[3] https://github.com/flameshot-org/flameshot/issues/2848