~begs

Saint Petersburg, Russia

https://begs.srht.site/

Just hacking around


#294 switch to doas instead of sudo a month ago

Comment by ~begs on ~mil/sxmo-tickets

Does this also go well with the other distributions people might run Sxmo on?

Yes, it's available on both Arch and Debian: https://repology.org/project/opendoas/versions

#377 Alarm clock script a month ago

Comment by ~begs on ~mil/sxmo-tickets

It's Unix, you can just do sleep 12h && aplay /dev/urandom

#339 SWMO - Wayland Version of SXMO 2 months ago

Comment by ~begs on ~mil/sxmo-tickets

Btw, I'd suggest sircmpwn's visurf as a Wayland-native lightweight browser alternative. We may try to integrate it into Sxmo when it is released.

#294 switch to doas instead of sudo 2 months ago

Comment by ~begs on ~mil/sxmo-tickets

OpenDoas with doas.d is already in Alpine repos.

I'm for migrating to doas (at least by default, but I see no reasons to keep sudo support in Sxmo, it's anyway not seen by user directly), because it fits our (and every real human's) needs better.

#351 Handling phone-specific sway configuration 2 months ago

Comment by ~begs on ~mil/sxmo-tickets

We Will Duplicate Those For Other Devices

Thanks for clarifying, that's what I wanted to hear.

Not sure it's the best way, but it seems OK for now.

my proposal of creating sxmo-devices repo with "device dedicated shit" is still valid

#351 Handling phone-specific sway configuration 2 months ago

Comment by ~begs on ~mil/sxmo-tickets

This basic default configuration works only for pinephone.

  • It uses pinephone-specific output name, so only DSI-1 gets proper scaling and wallpaper.
  • It uses pinephone-specific input names when setting up delays.
  • It uses pinephone-specific input names for inputhandler bindings, so they don't work for other devices.

It's defunct by default on any device that isn't pinephone, and there is no other way to fix that than editing it directly, so just including it in user config won't do anything useful if user's device isn't pinephone.

I'm sorry that I couldn't explain my point.

#351 Handling phone-specific sway configuration 2 months ago

Comment by ~begs on ~mil/sxmo-tickets

If we handle only pinephone, then at least hardware keys and proper scaling won't work on any other device without manual configuration. I think it's unoptimal to left people writing same configuration from scratch each time. And to my knowledge there is no way to do it in device-independent way (there could be one if we had input type:key).

So I see two ways:

  • device-specific configs packaged in distribution's device package
  • device-specific configs in a separate git repo (I'm willing to maintain it if needed)

#351 Handling phone-specific sway configuration 3 months ago

Comment by ~begs on ~mil/sxmo-tickets

Oh, now I got it. But while having a one single config for all input devices of all phones seems nice, it won't work with output - DSI-1 is a common name and therefore overriding i.e. scaling factor would be impossible. And also that way it's impossible to do bindsym --input-device, as we don't know actual input devices used.

#339 SWMO - Wayland Version of SXMO 3 months ago

Comment by ~begs on ~mil/sxmo-tickets

Sway/wlroots have recently dropped logind in favor of much simplier seatd, so seatd is prefered.

#351 Handling phone-specific sway configuration 3 months ago

Comment by ~begs on ~mil/sxmo-tickets

This way Sxmo would be unusable out of box on any device other than PinePhone, so I disagree. I think it'd make sense to split any (even pinephone) phone-specific configuration (button timeouts, scaling, etc) to device-specific configs and ship them with sxmo-utils along with a fallback config that will try to autodetect hardware just to make Sxmo at least usable.

I'll be implementing it soon.