It's actually quite neat. It is a three part archesta:

1. i3 key binding, say, Super-l that triggers a script of mine.
2. The script itself rofi-menu takes a single argument, a text "menu file" that describes the menu. Say, my-layouts.menu
3. The menu file is super simple. It looks like this:

Menu Title
[shortcut] # <exit | stay> # <label> # <command>
[shortcut] # <exit | stay> # <label> # <command>
[shortcut] # <exit | stay> # <label> # <command>
...

The script parses this file and generates the menu.

• shortcut is the key binding that will immediately trigger the menu item.
• exit | stay defines whether the menu closes after the option is actioned (sometimes you wanna keep the menu open)
• label is what you see in the menu
• command is... well, the command

One more thing, if your hostname is "my_machine", and the menu file that you gave to my script is "my-layout.menu", then the script will actually prefer to use "my-layout.my_machine.menu" if it exists. So you can share your config across multiple machines and have them pick the appropriate menus depending on where it is ran.

A menu example could be:

Layouts
l # stay # Rotate Layout # i3-msg toggle all
f # exit # Toggre Floating # i3-msg floating toggle

So to change i3 layouts, I type:

• Super-l (opens menu)
• l rotate layout (rows, cols, tabs, stack) and keep the menu open. If I keep hitting l it will keep rotating.
• Esc to close the menu.

To toggle the window floating:

• Super-l (opens menu)
• f to toggle floating. The menu closes immediately after.

If you are interested, I can share the script with you :)

It's good for what it's good for: avoiding carpal tunnel.

Are you consistently using a keyboard for 4+ hours a day? I mean typing, not just mouse & the occasional tap. Then Dvorak is vastly superior to qwerty. If not, not really worth it.

It was a huge pain for 2+ months for me to rewire my muscle memory to use it, but it was worth it for me. 15 years of typing a lot almost every day, never had so much as a twinge.

It doesn't help with speed. Typing speeds between qwerty and Dvorak are the same, once you factor in user experience and which one they're more used to.

Personally, I really like it. I've never been a fast typer, but I feel like I'm faster with it. The layout just makes sense to me. There was a significant learning curve though, it took me a while to get used to it

I don't know, I use neo2, but qwerty is bad

Honestly as a Dvorak user, I wouldn't switch if you can already touch type on qwerty. Unless you have to type a lot and are having issues maybe.

If you want to learn though it makes a lot of sense to just learn Dvorak instead. It's easier and less likely to cause issues later.

No I'm not lol I use GUI desktop, I do like the terminal for navigating the file system, running code, and installing apps though

so i guess everybody is doing if via flakes now but can't we just continue with the configuration.nix and home.nix split?

huh. i have the left monitor desktop customized to my liking, my wife has the right one customized to her liking. we have shortcuts on each screen to make it the primary monitor depending on who's using it.

but thats just a single open app in the top frame? btop i believe

edit -- oop after i zoomed in so i could see the gaps i realise its 3 apps. btop, htop (redundant) and yazi or ranger or superfile.

woudlnt the real implication be that the top panel is using a window manager and the bottom one is using a mint alternative?

If you look at the bottom right, which is running htop, there is a process list which shows that it is ytop.

A top/htop/btop style application.

No longer maintained though.