#xcompose — Public Fediverse posts

Aww yiss. Finally worked out how to get xcompose to work, despite the old-school manpage that doesn't really tell you how to do the basic config.
As well as being able to easily type em dashes—like a god-damn ell ell em—and degree° symbols and … what are they called … ellipsises, it actually does multi-character strings, like my email address. I'd previously been using espanso or autokey, but wasn't a fan of either.
For anyone playing along at home on Sway, in my `.config/sway/config` file I set the compose key to the right alt key (ralt) with
`input "type:keyboard" {
xkb_options compose:ralt
}`
I set the substitutions in `~/.XCompose`
So for example I can auto-type my personal email withthe sequence `ralt @ p` and my work with `ralt @ w`
`
<Multi_key> <@> <p> : "[email protected]" # email personal
<Multi_key> <@> <w> : "[email protected]" # email work
`

This will probably work for other window managers like i3.
#XCompose #Sway #Linux

Aww yiss. Finally worked out how to get xcompose to work, despite the old-school manpage that doesn't really tell you how to do the basic config.
As well as being able to easily type em dashes—like a god-damn ell ell em—and degree° symbols and … what are they called … ellipsises, it actually does multi-character strings, like my email address. I'd previously been using espanso or autokey, but wasn't a fan of either.
For anyone playing along at home on Sway, in my `.config/sway/config` file I set the compose key to the right alt key (ralt) with
`input "type:keyboard" {
xkb_options compose:ralt
}`
I set the substitutions in `~/.XCompose`
So for example I can auto-type my personal email withthe sequence `ralt @ p` and my work with `ralt @ w`
`
<Multi_key> <@> <p> : "[email protected]" # email personal
<Multi_key> <@> <w> : "[email protected]" # email work
`

This will probably work for other window managers like i3.
#XCompose #Sway #Linux

I encountered this scenario while editing my #XCompose file (https://www.vimgolf.com/challenges/9v006a58d48e00000000080a) and decided to upload it to #VimGolf to see just how slow I was. Feel free to have a go!

@stib I've since checked out #SwayWM, and I can say that while indeed there's less resistance involved in migrating from #i3WM than in the case of #Hyprland, I also found that in general the configuration process for both i3 and Sway is less intuitive than for Hyprland. Also, Sway still does not correctly load #XCompose keybinds the way #X11 does. This is generally excusable since that's not really in the scope for what we ought to expect any #Wayland compositor to do.

On the matter of Hyprland's toxic community, I don't know much about it besides what's available on Drew's blog (https://drewdevault.com/blog/Hyprland-toxicity/), and in Vaxry's response (https://blog.vaxry.net/articles/2023-hyprlandsCommunity). The general impression I get from this interaction is that @drew is probably right in saying that Hyprland has a toxic community, but Vaxry's response raises some un‐challenged objections which are not entirely unreasonable. I also get the impression from Vaxry's own blog that they're probably too blithe when it comes to moderation, which may or may not be due to some underlying motivations.

All in all, I don't feel I know enough about this to make a complete judgement. For now I think I'll stick to i3, only because I get to keep my compose sequences.

@stib I've since checked out #SwayWM, and I can say that while indeed there's less resistance involved in migrating from #i3WM than in the case of #Hyprland, I also found that in general the configuration process for both i3 and Sway is less intuitive than for Hyprland. Also, Sway still does not correctly load #XCompose keybinds the way #X11 does. This is generally excusable since that's not really in the scope for what we ought to expect any #Wayland compositor to do.

On the matter of Hyprland's toxic community, I don't know much about it besides what's available on Drew's blog (https://drewdevault.com/blog/Hyprland-toxicity/), and in Vaxry's response (https://blog.vaxry.net/articles/2023-hyprlandsCommunity). The general impression I get from this interaction is that @drew is probably right in saying that Hyprland has a toxic community, but Vaxry's response raises some un‐challenged objections which are not entirely unreasonable. I also get the impression from Vaxry's own blog that they're probably too blithe when it comes to moderation, which may or may not be due to some underlying motivations.

All in all, I don't feel I know enough about this to make a complete judgement. For now I think I'll stick to i3, only because I get to keep my compose sequences.

I've finally decided to try #Wayland, and as someone who was using #i3wm ‘for the performance’ I'm happy to say that #Hyprland seems to perform comparably while providing a much nicer experience. The one hang‐up I have now is that some applications are no longer respecting my #XCompose file, which I have built to my needs over some time now. I'm wondering if anyone knows of a way to force‐feed composed keys to Wayland applications?

I've finally decided to try #Wayland, and as someone who was using #i3wm ‘for the performance’ I'm happy to say that #Hyprland seems to perform comparably while providing a much nicer experience. The one hang‐up I have now is that some applications are no longer respecting my #XCompose file, which I have built to my needs over some time now. I'm wondering if anyone knows of a way to force‐feed composed keys to Wayland applications?