#248 Mechanism for autostarting arbitrary group of apps 3 months ago

Comment by ~craftyguy on ~mil/sxmo-tickets

XDG autostart spec: https://specifications.freedesktop.org/autostart-spec/autostart-spec-latest.html

I found some implementations of this that might be good to use here:

xdg-autostart (very few dependencies, but written in vala.....): https://github.com/fabriceT/xdg-autostart

i3-autostart (written in go...): https://github.com/cking/i3-autostart

Fluxbox xdg autostart app (might be too specific to fb?): https://github.com/paultag/fbautostart

xdg-autostart-launcher (claims no external dependencies, written in C++): https://github.com/sandsmark/xdg-autostart-launcher

dex (python...): https://github.com/jceb/dex

Rather than writing a new tool for this, maybe one of these would work? (or something else I haven't found in the ~30min I searched around)

#248 Mechanism for autostarting arbitrary group of apps 3 months ago

Ticket created by ~craftyguy on ~mil/sxmo-tickets

It looks like all of the things that sxmo needs to run on startup are launched in sxmo_xinit.sh, which is fine for the sxmo essentials.

However, some devices (librem 5) need some extra apps running (e.g. wys for routing call audio). In other UIs in pmOS, we put a .desktop link to those in /etc/xdg/autostart, and those UIs honor the xdg autostart spec. Has there been any thought about having a utility in sxmo that would autostart things according to the xdg autostart spec too, so that distros (like pmOS) that install apps that some devices need to be running on startup could do that without having to make changes to sxmo_xinit.sh each time?

#240 Rethink how we lock SXMO 3 months ago

Comment by ~craftyguy on ~mil/sxmo-tickets

I just packaged ~iv's mobile slock (for Alpine Linux) here: https://gitlab.alpinelinux.org/craftyguy/aports/-/commits/sxmo_screenlock

#243 No battery level in status bar on Nexus 5 3 months ago

Comment by ~craftyguy on ~mil/sxmo-tickets

Great, so you can add a new script in the sxmo-utils repo under scripts/deviceprofile/hammerheadqcom.sh, that can set something like BATTERY_DEVICE=/sys/class/power_supply/foo/status (use real path, obviously :P). Then in sxmo_statusbar.sh use that value if that var is set, else default to the glob (to preserve existing behavior).

Though at some point it might make more sense to do away with default values for these things and just have a profile for every device, including the Pinephone? (a bigger question to the sxmo maintainers/folks)

#400 Editing the subject in the composer causes the contents of the whole tab to redraw 4 months ago

Comment by ~craftyguy on ~sircmpwn/aerc2

I also ran into this on my laptop, the lag was something like ~200ms between characters being printed in 'subject' as I typed them. Applying the workaround mentioned above resolved the issue, but I don't know whether there are implications with doing this. I didn't notice any downside in the limited testing I've done with this change so far.

diff --git a/commands/account/compose.go b/commands/account/compose.go
index b33acf5..f0e2c19 100644
--- a/commands/account/compose.go
+++ b/commands/account/compose.go
@@ -44,7 +44,6 @@ func (Compose) Execute(aerc *widgets.Aerc, args []string) error {
                } else {
                        tab.Name = subject
                }
-               tab.Content.Invalidate()
        })
        go composer.AppendContents(strings.NewReader(body))
        return nil

#6 Changing password store path requires application restart 4 months ago

bug added by ~craftyguy on ~craftyguy/caerbannog

#8 No icon on GNOME 4 months ago

bug added by ~craftyguy on ~craftyguy/caerbannog

#5 Replace libnotify with in-app notification 4 months ago

Comment by ~craftyguy on ~craftyguy/caerbannog

Implemented in 47df61e1e970c227473abc5367e5c75b3b8d6dfd

REPORTED RESOLVED FIXED

#7 Password isn't sometimes cleared from clipboard 4 months ago

Comment by ~craftyguy on ~craftyguy/caerbannog

Hmm, I think that perhaps it should be cleared when the user exists the app then?

So clear clipboard either 1) after X timeout, or 2) on app close, whichever comes first.

#5 Replace libnotify with in-app notification 4 months ago

enhancement added by ~craftyguy on ~craftyguy/caerbannog