Comment by ~kohn on ~mil/sxmo-tickets
Getting value
shared
that indicates that interface is set to tethering mode.$ nmcli -f ipv4.method con 'USB Networking' shared
Getting value
activated
that indicates that tethering is activated.$ nmcli -f GENERAL.STATE con 'USB Networking' activated
Also
$ nmcli con 'USB Networking' | grep ipv4.method | awk '{print $2}' shared
Ticket created by ~kohn on ~mil/sxmo-tickets
I've seen report #1941 and figured to have an indication in the statusbar as to whether an SSH session is currently active and how many connections there are.
Commands:
users
andwho
. Example:who | wc -l
.
Comment by ~kohn on ~mil/sxmo-tickets
I didn't take care for X11. I should add this code:
case $XDG_SESSION_TYPE in x11) # I didn't find the X11 command # https://git.sr.ht/~mil/sxmo-utils/tree/master/item/scripts/deviceprofiles/README.md # Maybe i3-msg -t get_outputs? wayland) # swaymsg -t get_inputs esac
Would there be a way of detecting keypresses in order to get the volume buttons right etc., if someone wrote an interactive script?
An interactive script is a good idea! I think an interactive script is possible using
xev
.
Comment by ~kohn on ~mil/sxmo-tickets
Note: The current instructions for SXMO don't work for me, unless executing the above
nmcli
commands.
Ticket created by ~kohn on ~mil/sxmo-tickets
After the doubt has been resolved and instructions are set, I suggest to add a toggle menu item to enable and disable USB Tethering.
- Toggle Menu item (toggle)
- Status bar to indicate that Tethering is activated
$ nmcli c modify '83bd1823-feca-4c2b-9205-4b83dc792e1f' ipv4.method shared $ nmcli d reapply usb0
$ nmcli c modify '83bd1823-feca-4c2b-9205-4b83dc792e1f' ipv4.method manual $ nmcli d reapply usb0
Comment by ~kohn on ~mil/sxmo-tickets
And, of course, SXMO is soon expected to be portable to other OSs other than Alpine Linux.
In any case, it would be nice if there's a simple way to relocate to
/usr/share/sxmo/
.I suggest to close this ticket, as raising this discussion is enough.
You, the developers will decide what to do with this.
Comment by ~kohn on ~mil/sxmo-tickets
This is really a utility script.
What would be the proper place for it?
Perhaps we should upload it to pmOS or SXMO documentation.
Comment by ~kohn on ~mil/sxmo-tickets
sxmo itself is already mostly written in POSIX shell script, introducing a config file format introduces more complexity.
Thanks. I didn't know this.
I didn't understand your second comment.
Comment by ~kohn on ~mil/sxmo-tickets
noneofyourbusiness, please help me. I'm a not a professional.
aren, even though devices are more powerful now, I'm not in favor of a daemon, unless it terminate itself once it gets an indication that hardware keys are working.
I'm not an expert.
Comment by ~kohn on ~mil/sxmo-tickets
Desktop files, maybe?
I'm not comfortable havnig such type of files, which I consider as configuration files, inside
/usr/bin/
, and it seems weird to me.Make something else, or even keep the Bash files, but don't locate it under
/usr/bin/
, but rather under/usr/share/sxmo/deviceprofile/
.I'm not an expert.