31–40 of 102 posts
Writing a pure X11 application in 2024 is an interesting choice, given the recent push to Wayland. Nevertheless, it looks like a pretty cool tool!
The recent push to Wayland in 2024 is an interesting choice, given how productive and usable X11 is.
Earlier quoted context omitted.
i enter the five emojis i ever need to use by pressing +u and then typing the emoji word. i think i can use skin color thumbs up just fine. but yeah, no search. but also no extra windows. when i asked i assumed compose + something like an IME could solve both with the search/window being optional.
Xcompose only offers sequences started with the "compose" key (whatever it is mapped to) and resulting in a single X key-symbol, so to type an emoji needing multiple uniciode codepoints that way, you'd have to enter multiple "compose sequences". Whatever you describe here is not simple Xcompose. AFAIK, GTK offers entering unicode codepoints in a similar way ... Of course you can do a lot of things with "input methods…
Not correct. For example, on my usual keyboard layouts¹, I use sequences starting with and for superscripts and subscripts.
> and resulting in a single X key-symbol
Also not correct. I certainly have a few non-single-keysim entries in my .Xcompose, e.g. ↦ ℝ².
¹ https://github.com/datatravelandexperiments/kps-keyboard-lay...
Made me think of the emoji physical keyboard from Tom Scott https://youtu.be/3AtBE9BOvvk
Unicode sucks. There is a glyph for a hammer, for a screwdriver, but not a soldering iron. During COVID, people were using a golf club as a substitute for a cotton swab. We now have generative AI that can make any desired emoticon you can dream of, except you can't use it because of Unicode.
Ya let's integrate gpu-accelerated emoji generation into unicode and require it everwhere, we can call it UTF-8B and standardize on 8GiB per character until that turns out not to be enough.
Earlier quoted context omitted.
Not sure you really mean the compose mechanism provided by Xlib (and xkbcommon etc ...)? If so, this wouldn't work for all these emojis that are represented by grapheme clusters, ZWJ-sequences or are just "qualified". The result of a compose sequence is limited to a single "key symbol", which can only encode a single unicode codepoint. Even for those emojis consisting of a singe codepoint, it would really miss the po…
> The result of a compose sequence is limited to a single "key symbol", which can only encode a single unicode codepoint. Not true even if some broken toolkits impose that limitation.
Still, in practice, it will only work with some applications...
On Gnome there is the "Characters" application which is pretty handy. I do want to make a few improvement to search, but otherwise it's pretty good. You copy the unicode character to the clipboard and can then paste it wherever you need.
If you run Gnome it's probably already installed. If not: https://gitlab.gnome.org/GNOME/gnome-characters
Unicode sucks. There is a glyph for a hammer, for a screwdriver, but not a soldering iron. During COVID, people were using a golf club as a substitute for a cotton swab. We now have generative AI that can make any desired emoticon you can dream of, except you can't use it because of Unicode.
The worst part is Unicode breaking existing documents by retroactively converting some common symbols emoji-default, despite supposed stability guarantees.
The second worst part is the emoji combining sequences becoming an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.
as long as i need to run nvidia with multiple monitors, i'll hang on to x11.
We're in 2024Q3, things have improved. Nvidia helped out. (X)Wayland/KDE/Qt/GNOME bugs were fixed. Apart from that, use X11 as long as you wish! I'm just glad we can finally improve the open source desktop-environment infrastructure to match those of Windows and macOS: we've been stuck for too long.
Unicode sucks. There is a glyph for a hammer, for a screwdriver, but not a soldering iron. During COVID, people were using a golf club as a substitute for a cotton swab. We now have generative AI that can make any desired emoticon you can dream of, except you can't use it because of Unicode.
Unicode is OK (flawed but OK), emoji in Unicode suck. The worst part is Unicode breaking existing documents by retroactively converting some common symbols emoji-default, despite supposed stability guarantees. The second worst part is the emoji combining sequences becoming an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.
That was the main reason for me to pull in harfbuzz. At least it "just resolves" those sequences to glyph indices.
Writing a pure X11 application in 2024 is an interesting choice, given the recent push to Wayland. Nevertheless, it looks like a pretty cool tool!
The recent push to Wayland in 2024 is an interesting choice, given how productive and usable X11 is.