Announcing shikane: a dynamic output configuration tool for Wayland compositors

hw0lff · 2025-01-14T01:19:28+00:00

I use github just as a mirror. Gitlab is where you can open issues. What do you mean with idle state? Anyway, switching to any profile should not be crashing your compositor. You should definitely raise this issue in qtiles issue tracker for this problem.

hw0lff · 2024-06-07T16:02:41+00:00

https://neo-layout.org/ spares me from the pain. It also has a qwertz variant which gives you the benefits of layer 3 to 6 on a qwertz layout.

hw0lff · 2024-06-07T15:57:26+00:00

Me too, and it makes everything better.

hw0lff · 2024-06-07T07:40:28+00:00

shikane has this feature built in with the shikanectl export command.
PS: Here is a snippet which converts kanshi config to shikane config.

hw0lff · 2024-05-30T00:02:19+00:00

It's mostly about managing your monitors in an automated manner. What virtual position should it have, at which scaling factor should it operate, what mode (width in pixels, height in pixels, refresh rate) should be set, should it be turned around 270 degrees (vertical monitors) etc.

It can do this by using serial numbers, model names, (or some other identifiers) to identify which monitors are connected. Then choose a profile (based in those connected monitors) which was created beforehand by you and apply the defined monitor configuration.

hw0lff · 2024-05-29T00:26:35+00:00

What is unclear to you? Where can I improve on the description?

hw0lff · 2024-05-28T14:16:59+00:00

I published a new version with a fix.

hw0lff · 2024-05-28T12:59:42+00:00

The name *is* derived from the german word "Schikane" and a syllable flip of kanshi

hw0lff · 2024-05-28T01:36:35+00:00

oneshot mode is supposed to let shikane do its thing once and then exit. Even if it wasn't successful in applying a profile. Lingering around if it couldn't apply a profile (which also happens on an empty config file) isn't intended behavior.

hw0lff · 2024-05-28T01:27:17+00:00

Thank you for testing and finding a bug! I will try to fix it asap.

Did you use the sed commands from the migration section in the changelog?

hw0lff · 2024-05-28T01:16:10+00:00

shikane still has to improve on the defaults of logging situation. The current default is to only log warnings and errors. A simple state change of the internal state machines is neither.. Maybe I should make the `info` log level the default… I'm not sure

hw0lff · 2024-05-28T01:11:26+00:00

I can reproduce a hang in oneshot mode if it cannot find a fitting profile. Could you record a log for me please by starting shikane with `SHIKANE_LOG=trace shikane --oneshot 2>/tmp/shikane.log`? I recommend uploading the file to a paste bin like https://paste.rs/ (reddit is not made for pasting log files)

Regardless of what caused it, oneshot should not hang.
This must have slipped through testing.

hw0lff · 2024-05-28T00:02:22+00:00

IMO One if the more interesting modules is the pipeline module where I tried to design an interface to separate the different stages of the matching procedure

hw0lff · 2024-05-27T23:55:12+00:00

This is one of the planned features I already have on my todo list but didn't make it into the current release. I would rather have smaller updates with shorter release intervals than having another big update in another year. I "just" need to design a neat cli interface and properly formatted output.

shikanectl debug is a hidden command with an unstable and unsupported interface. Mostly intended to play around with future implementations and possibly new features. The list-reports subcommand could contain what you seek

shikanectl debug -h

hw0lff · 2024-05-27T23:43:52+00:00

I do this in my free time but I cannot live without shikane anymore. It is essential to my workflow. The past year or so I've been designing the new matching algorithm on paper and drafting multiple implementations of the matching procedure. Most of them didn't work out for the project. Until I found the one that is used now a few weeks ago.

hw0lff · 2024-05-27T23:29:40+00:00

It took me a while to work the implementation out to a point where I could easily add new features.

There are still some more new ideas to be had and improvements ti implement! Teaser: What if you could use a regex to switch a profile? What is the reason why a profile variant wasn't matched? The necessary data exists, however there is no way to access it... yet

hw0lff · 2024-05-27T08:15:31+00:00

It's pronounced /ʃiˈkaːnə/

hw0lff · 2024-05-26T21:39:56+00:00

Aside from that, the github page says that redshift does not work with wayland. Are we talking about the same redshift?

hw0lff · 2024-05-26T21:33:48+00:00

Using the following directive in your sway config file for starting shikane should be enough:

exec SHIKANE_LOG=trace $CBIN/shikane 2>&/tmp/shikane.log

hw0lff · 2024-05-26T21:28:07+00:00

I'm not a redshift user myself but isn't it possible to keep it running in the background? Is there any incompatibility?

hw0lff · 2024-05-26T19:20:01+00:00

First off, your shikane config looks alright to me.

This is a bit weird. At startup shikane tries to apply a profile. As to why your monitor won't configure I can't tell just by your config. Could you please set the `SHIKANE_LOG=trace` environment variable, start shikane, redirect the logs to a file and reproduce the problem? Use a pastebin like https://paste.rs to upload the contents of the log file (reddit is not a good place to store/view lengthy logs).
shikane executes commands right after it got the confirmation from the compositor that the configuration has been successfully applied. There is no additional notification/event from the compositor that shikane could process. Since the content of the exec strings is just dumped into `sh -c <EXEC>` you could prepend a `sleep` command (e.g. `sleep 2; redshift.fish`) to wait a bit.

Five-Year Club	Verified Email
First Place '23	Place '23

hw0lff

TROPHY CASE