On Thu, Apr 24, 2025 at 11:21:58PM -0700, Anjandev Momi wrote:
> On Tue Apr 22, 2025 at 1:43 PM PDT, Maarten van Gompel wrote:
> > On Tue Apr 22, 2025 at 9:38 PM CEST, Aren wrote:
> > > On Sat, Apr 19, 2025 at 04:22:54PM -0700, Anjandev Momi wrote:
> > >> There are devices that use the same device name but different form
> > >> factor. For example, a raspberry pi may have a touch screen or may be in
> > >> a blackberry form factor.
> > >> 
> > >> Remove this prompt cause it is annoying for users
> > >
> > > I think there's still some cases where the user experience will be worse
> > > if there isn't a device profile. The one that comes to mind is using the
> > > volume keys to scroll in the menus is significantly slower if
> > > SXMO_VOLUME_BUTTON isn't set.

On Sun, Apr 13, 2025 at 10:03:04PM +1000, hazardchem wrote:
> This resolves: https://todo.sr.ht/~mil/sxmo-tickets/621
> 
> Signed-off-by: hazardchem <hazardchem@disroot.org>
> ---
> 
> v2 - fixed issue if root window was focused then it will unfocus new window
> 
>  scripts/core/sxmo_dmenu.sh | 13 ++++++++++++-
>  1 file changed, 12 insertions(+), 1 deletion(-)
> 
> diff --git a/scripts/core/sxmo_dmenu.sh b/scripts/core/sxmo_dmenu.sh
> index 689aa546..e4f674b0 100755
> --- a/scripts/core/sxmo_dmenu.sh

On Sat, Apr 19, 2025 at 04:22:54PM -0700, Anjandev Momi wrote:
> There are devices that use the same device name but different form
> factor. For example, a raspberry pi may have a touch screen or may be in
> a blackberry form factor.
> 
> Remove this prompt cause it is annoying for users

I think there's still some cases where the user experience will be worse
if there isn't a device profile. The one that comes to mind is using the
volume keys to scroll in the menus is significantly slower if
SXMO_VOLUME_BUTTON isn't set.

I was going to suggest that we clean those up first, but some quick
grepping suggests that's the worst one, along with SXMO_VIBRATE_{DEV,STRENGTH}.

Marking as applied

On Mon, Apr 21, 2025 at 02:28:59PM +0200, Maarten van Gompel wrote:
> On Sun Apr 20, 2025 at 9:57 PM CEST, Anjandev Momi wrote:
> > Lets make sure we dont accidentally ship broken docs and have to redo
> > the release. Moreover, we should catch failing html docs in this repo
> > becuase sxmo.org relies on it.
> 
> Great idea, applied!
> 
> -- 
> 
> Maarten van Gompel (proycon)
> 

On Wed, Apr 09, 2025 at 09:03:48AM +0200, Vojtěch Káně wrote:
> Dear sxmo community,
> I've been using sxmo on my Poco F1 for many months without issues. I am
> currently running pmOS 24.12. At login time, I am however greeted with
> 
> > WARNING: deviceprofile file not found for xiaomi,beryllium-ebbg. Most
> > device functions will not work. Please read:
> > https://sxmo.org/deviceprofile
> 
> I don't know how it is that my phone works just fine (except for audio
> input, but that's unrelated?), but I suspect that the warning occurs,
> because the device is normally called just "xiaomi,beryllium". The "ebbg" is
> a specific display variant and AFAICT does not affect the buttons at all.
> 

Merged, thanks

To git.sr.ht:~mil/sxmo-utils
   4f4e13bb..001bd62e  001bd62e -> master

I'm excited to get river support, from the river source code I've read
it's very well implemented, and it's goals (modularity and simplicity)
seem to align well with sxmo.

From a read through, I noticed a number of nits, but overall this looks
good. My vote would be to merge this just after we release 1.18 to
ensure we have ample time for testing.

I've squashed these patches to review, from a quick skim it looked like
there were a handful of issues in the first one, which are fixed in the
second, and I don't want to get distracted by them.

On Wed, Mar 19, 2025 at 11:15:19PM +0100, Maarten van Gompel wrote:
> From: Willow Barraco <contact@willowbarraco.fr>

Apparently I'm really struggling with remembering to include the applied
header today.

Looks good, merged

To git.sr.ht:~mil/sxmo-utils
   ef18ab1f..4f4e13bb  4f4e13bb -> master

On Wed, Mar 19, 2025 at 10:57:25PM +0100, Maarten van Gompel wrote:
> ---
>  .../sxmo_deviceprofile_lenovo,thinkpad-x13s.sh              | 6 ++++++
>  1 file changed, 6 insertions(+)
>  create mode 100755 scripts/deviceprofiles/sxmo_deviceprofile_lenovo,thinkpad-x13s.sh
> 
> diff --git a/scripts/deviceprofiles/sxmo_deviceprofile_lenovo,thinkpad-x13s.sh b/scripts/deviceprofiles/sxmo_deviceprofile_lenovo,thinkpad-x13s.sh
> new file mode 100755
> index 0000000..e019d99

I wish we could move this logic into whichever menu we happen to be
using, and have it detect it based on the screen size (would also
help with not overlapping the keyboard).

Besides that, looks good, merged.

To git.sr.ht:~mil/sxmo-utils
   db914f6c..ef18ab1f  ef18ab1f -> master

On Wed, Mar 19, 2025 at 10:56:07PM +0100, Maarten van Gompel wrote:
> can be set to 0 on desktop/laptop system to disable wofi adapting
> to small screens in landscape mode
> ---
>  docs/sxmo.7.scd                                     |  6 ++++++