I am having usabilitiy problems with sway edition. The screenlock/sleep interferes frequently and I want to regulate this behaviour myself. It is not a big deal when sway lock jumps in every 10 minutes or so. However, this is annoying at times; e.g. when I watch videos either in my browser or on the video player or when I read on my laptop.
I have a temporary fix by setting swayidle to kick in after 3 hours or inactivity in the system wide configuration files. However, I am seeking to have a better solution. I know there is Caffeine in the repositories; however, it seems to be using python2, which I don’t want to install and I do not want caffeine to even autostart as python 2 is dated/out of development.
Is there another way I can fix this? If I can completely disable automatic sleep/screenlocking and make it triggered only when I chooose “Lock” from the shutdown menu, I will be ok with this too; instead of using Caffeine like software.
Adjusting applications in a way to prevent the lock screen may not work the best; say, you adjusted firefox with that behaviour. But there may be users preferring Chromium or another browser; so, they would still have the annoyance again.
Personally, I am not a fan of automatic screen locking and turning of monitor in a laptop, although I understand its rationale. I was doing this manually whenever I need to by using Caffeine extension in my old Gnome system. Caffeine was set to on by default in my old system.
I hope this could be fixed/adjusted in Manjaro Sway.
I flashed the image and tested it briefly. Waybar didn’t launch; so, I logged into a system without a panel. Wofi seems to be working; but terminal application problem with wofi seems to be persisting; I still can’t confirm that waybar module for presentation mode is working.
I have updated my system this morning with the stable updates and my system feels stable for my workflow.
I guess I will likely stay with sway. The other editions (XFCE, Kde and i3) were all problematic.
Yes, I downloaded and flashed the new image; this time waybar showed up. I can confirm I see the idle indicator.
I also tested wofi against terminal based applications like ranger, htop, neovim etc. I can confirm it is working too.
I have two issues; I am not sure if any of them could be fixed as they seem to depend on developers of the corresponding software:
Neovim: I launch Neovim using wofi; there is the welcome screen; I close it using :q!. Then I launch Neovim using wofi again. Neovim launches on quarter of the display space provided by termite, which is odd. Additionally, the welcome screen of Neovim does not show up this time. Can this be fixed? If not, would another text editor be under consideration? I am ok using simple text editors like nano or gtk3 based geany or vim/emacs.
Idle indicator: I activate the idle indicator, then I reboot and idle indicator does not preserve the status. So, I have to enable it again. I understand that this is likely an issue with sway; so I guess it is ok to leave it like this. Caffeine was giving me the choice to make my choice persistent across boots. This is a minor problem and I can adapt accordingly.
Overall, I think the image is good. I didn’t make a long test because I flashed into a test card; however, it seems very usable.
Hmmm that might depend on changes to termite I guess… not sure if this is already being addressed. Something I noticed though: when you force a refresh of the terminal window it usually updates itself…
You can try the following:
if the terminal is active press ALT+Shift+Space (this should make the terminal window with neovim inside a floating one)
press ALT+Shift+Space again (to disable the floating) and the neovim should now use the whole space inside the terminal window
Tried it a couple of times here with much success.
Ok, thank you for the tip. I will use it as a workaround.
I think something might be wrong with the way neovim is launching. I would expect to see the welcome screen of neovim everytime I close it, then launch it. Or launch a new instance. The way neovim/vim passes to the buffer without welcome screen is only when neovim/vim is already open and you launch a new instance. At least this has been my experience with gvim, which is gtk3 based.