I like the current UI design. It's so simple with large buttons, so I'd have to put a little thought on how to present the new options without cluttering it.

As i said in my email I have other things occupying my time, so this will have to wait until I find the time.

But just in case you missed it:

https://codeberg.org/phranz/pactions

I wanted to know if you could make jwmkit_logout, to have these options built in to it:

disable crtl-alt-backspace
disable sysrq
disable vt-switching
lockscreen

you already have these:

logout, suspend, shutdown, poweroff

But I wondered if you could make those possible.

Also, if you don't want to make that a default, even if you could make that optional, that would be awesome.

This script I referenced uses yad. 

Or if this all sounds too complicated, can you modify that script to make it work in Hyperbola with any type of shell, not just bash, not require sudo, etc...

Where do I report issues? (along with possible fixes)

https://www.gnuinos.org/mirror/daedalus/

Some contributions of my own are the dynamic menu and the logout dialog. The images also ship with a customized SpaceFM file manager containing the Trash plugin as well as Hopman integration. No dbus.

Yes the issue with the time templates was a silly mistake. It shows the difference a single character can make when coding. in this case it was matter of lowercase vs uppercase.

For those who don't know what we are talking about.  The suggested templates for the tray clock used months instead of minutes.  This meant the minutes were only correct once per hour as they only change once a day. An embarrassing mistake, but one that was easy to make.

I have made embarrassing mistakes too,

something as simple as leaving apostrophes, like this:

MODULES="i915"

https://wiki.hyperbola.info/doku.php?id … el_modules

Was enough to make my system unbootable.

That frustrated me one hundred + times almost before I sought help to learn that was the problem.

Something so small can cause huge headaches eh?

For those who don't know what we are talking about.  The suggested templates for the tray clock used months instead of minutes.  This meant the minutes were only correct once per hour as they only change once a day. An embarrassing mistake, but one that was easy to make.

20231223 Merry Christmas

Support for new JWM features and a few necessary fixes - mostly things broken by Debian 12.

• support for suspend and hibernation

• jwmkit_keys supports Task#

• jwmkit_desktops supports backandforth

• jwmkit_appearance supports showkill and showclient

• jwmkit_groups supports nomaxtitle

• Bugfix - Battery menu

• Bugfix - incomplete time zone data

• Bugfix - sndio mixer

• Bugfix - Tray clock templates used month instead of minutes

You also have done some interesting changes on my behalf which pleased me even more.

zapper wrote:

@jwmkit what about cpu resources for jwmkit on daedalus vs chimaera

Wow!, I don't know how I missed your post.  It's been more than a month. I hope you didn't think I was ignoring you. Sorry.

I understand the concern of CPU usage.  Not only for performance, but battery life. I did not compare CPU usage of Daedalus with previous releases. Although I always keep an eye on HTOP,, and I can tell you CPU usage seemed pretty low, and I don't think it should be a concern.

Of course CPU usage is just like RAM usage.  Any noticeable difference is usually the result of additional services and software you install/configure.

No worries, I do the same thing... btw, probably. I mean as long as you don't use something like awesome, or a desktop environment, even Lumina i might add is considered in this! But yeah, if you don't use a bloated window manager or any desktop environments, you shouldn't have any significant battery life issues from the desktop appearance alone.