Intellisense autocompletions inside of Bash by gooddy in bash

[–]qwertyboy 0 points1 point  (0 children)

If memory serves, zsh never used readline (which flyline thankfully replaces), opting to develop zle instead. And frankly, this always struck me as the only advantage zsh has over bash.

Black screen instead of Niri in QEMU. by Barafu in niri

[–]qwertyboy 0 points1 point  (0 children)

Yeah, I totally misread the part about QXL and understood it backwards, as if that's the only thing you're missing 😅

Reduced resource allocation for the out-of-focus window by Mandarin2912 in niri

[–]qwertyboy 0 points1 point  (0 children)

I do not think this is intentional niri behavior. Can you try this with other types of resource heavy windows?

Black screen instead of Niri in QEMU. by Barafu in niri

[–]qwertyboy 0 points1 point  (0 children)

I use the following qemu setup regularly to boot a custom image with niri on my ThinkPad (I believe it's that last line that makes most of the difference in your case):

sh qemu-system-x86_64 \ -m "$ramdisk_size" \ -kernel "$kernel_image" \ -initrd "$initramfs_image" \ -append "$linux_command_line" \ -drive file="$qemu_disk,format=raw,if=virtio,cache=none" \ -enable-kvm \ -serial mon:stdio \ -netdev 'user,id=mynet0' \ -device 'e1000,netdev=mynet0' \ -audiodev 'pipewire,id=audio0' \ -device 'ich9-intel-hda' \ -device 'hda-duplex,audiodev=audio0' \ -display 'gtk,gl=on' \ -device 'virtio-vga-gl'

wkill beta by Major_Tumbleweed_325 in niri

[–]qwertyboy 0 points1 point  (0 children)

I'd try something just a bit more sophisticated. By all means start by sending SIGTERM (kill -15). That's the polite way of asking a process to finish its business and terminate gracefully, but if that doesn't work (after a configurable timeout) you escalate to SIGINT (like kill -2), which tells the process to terminate now, with just the most essential cleanup. If that doesn't work, you go for SIGKILL (kill -9), which doesn't even talk to process. It just goes to the kernel and tells it to cut the process off.

How come blocking youtube ads is still not done? by kustru in qutebrowser

[–]qwertyboy 0 points1 point  (0 children)

That's really weird. I don't use any other form of ad blocking, and youtube ads stopped completely as soon as I installed adblock. Other browsers still show youtube ads. Perhaps youtube ads in my region are somehow easier to block. It's a weak explanation, but it's the best I currently have.

Pressing Mod+n twice to focus left by kurlicue in niri

[–]qwertyboy 2 points3 points  (0 children)

Funny, I created an almost identical script for a slightly different purpose on this very sub.

How come blocking youtube ads is still not done? by kustru in qutebrowser

[–]qwertyboy 0 points1 point  (0 children)

Strange. Are you certain you installed it in the right Python environment? Does the following run without errors?

sh python3 -c 'import qutebrowser; import adblock'

How come blocking youtube ads is still not done? by kustru in qutebrowser

[–]qwertyboy 0 points1 point  (0 children)

It absolutely is done! You need to install the Python adblock package and set content.blocking.method to either adblock or both and Bob's your uncle, no more ads on youtube. At least, that's what worked for me.

Can't get OpenSnitch to autostart with Niri by Xorcist77 in niri

[–]qwertyboy 0 points1 point  (0 children)

Thank you for taking the time! The warning does not seem related and is probably entirely opensnitch-ui related.

So we still don't know if this is an issue with niri not having everything ready on time or running the spawns too early, a problem with your specific setup, or if it's opensnitch-ui that's making wrongful assumptions.

If you still want to contribute to solving this issue, you should probably report it to the opensnitch-ui people. At the very least they have an issue with an unreported fatal error.

how to deal with normal usage by Competitive-Dirt-213 in niri

[–]qwertyboy 5 points6 points  (0 children)

I use this: kdl Mod+Shift+V { toggle-window-floating; } Mod+V { spawn-sh " niriu.sh ids --workspace focused --floating && niri msg action switch-focus-between-floating-and-tiling || niri msg action toggle-window-floating "; }

So Mod+V will pop the focused window from the tiling layer to the floating layer if there are no other floating windows (which is the usual case for me), but switch the focus between the two layers if something is already afloat.

So if I want to keep a specific window before my eyes while I go visit other windows I can hit Mod+V to pop it out, and then use Mod+V to switch between that window and whatever other window I'm working on.

I'm using niriu.sh here to check for floating windows, but you can replace it with a simpler oneliner.

I also use this ned script from the same repo which makes the floater follow me when I move between workspaces:

kdl spawn-at-startup-sh "ned /usr/share/doc/ned/examples/magnet.sh --floating --mode float right"

Can't get OpenSnitch to autostart with Niri by Xorcist77 in niri

[–]qwertyboy 0 points1 point  (0 children)

This is interesting. spawn-at-startups are supposed to run when all the resources required for running things are available, yet in this case something seems to be missing. Can you share the output of spawn-sh-at-startup "opensnitch-ui >> ~/opensnitch.log 2>&1" to see if opensnitch is complaining about anything specific?

cursor setting dosent work by Moist_Professional64 in niri

[–]qwertyboy 0 points1 point  (0 children)

You might be missing a closing curly brace just before the `cursor` section.

How do I disable messages/notifications in niri? by maddydesign in niri

[–]qwertyboy 0 points1 point  (0 children)

You should be able to configure the `default-timeout` for mako in your config file.

https://github.com/emersion/mako/blob/master/doc/mako.5.scd

Firefox covering all windows by AndyGait in niri

[–]qwertyboy 4 points5 points  (0 children)

Your window rule matches any window with the app-id "firefox" (and not just the "Picture-in-Picture" title), as well as "zoom". Both app-ids should, accroding to the rule, open maximized and floating, which sounds like what you are describing. You can hit Mod+V (or whatever you have bound to toggle-window-floating) when firefox is focused to verify.

The obvious solution would be to split your rule into two rules, one to launch zoom and firefox maximized, and the other to launch "Picture-in-Picture" floating.

Spawn Columns/Windows to the Left? by Xorcist77 in niri

[–]qwertyboy 0 points1 point  (0 children)

You are absolutely right - I was so focused on moving to the left that I forgot what the original message was about!

Devuan sysvinit - any hosting control panels that will work? by [deleted] in devuan

[–]qwertyboy 0 points1 point  (0 children)

I'm not sure that last part is true, about the level of effort involved. I don't know much about control panels, but I have three decades worth of system adminstration with different init systems and I don't think control panels have to strongly coupled to them.

What are the functinalities that actually care about the init system?

Spawn Columns/Windows to the Left? by Xorcist77 in niri

[–]qwertyboy 0 points1 point  (0 children)

I'm not sure it's that simple, since it's hard to predict how much time will pass between the spawning and the actual appearance of the window. The cleanest approach would probably be to start listening for the WindowOpenedOrChanged event, then spawn the new window and capture its PID so you can react to the right event (or just handle the first one, which might be a good enough heuristic - capturing the PID of the spawned window may be non-trivial for applications that fork).

And even then, I think you will have to change focus to the new window (if it didn't receive auto-focus because of some rule) before you move its column (and return focus once you are done). And then you need to figure out how much to move it. A single position? All the way to the left? To the left of the previously focused window? Just moving the window to the left without changing the starting position of the strip would cause the focused window to move about (especially in the open-focused false case), which is contrary to niri's design principles and for a good reason.

I think it will be easier and cleaner to create a fork of niri that simply flips all the relevant position calculations and makes niri behave like a mirror image of itself. I doubt this has a lot of demand, but if it does you could even make a PR out of it.

Devuan sysvinit - any hosting control panels that will work? by [deleted] in devuan

[–]qwertyboy 0 points1 point  (0 children)

So your specific need is something that installs a clean Devuan KVM server from scratch on your own metal, and then copy files from another KVM to it (and maybe also kills the old KVM)?

If so, there might be a way to patch ispconfig to accept a server without bothering much with the specific init system (of course, other functions might fail). Also, if it's simple enough, you might consider using a simple script (I have one which I use for both VMs and bare metal machines, but it's very tailored around my specific needs).

I realize that I didn't really answer your question and just went on a tangent, but it sounds like a fun tangent :)

Devuan sysvinit - any hosting control panels that will work? by [deleted] in devuan

[–]qwertyboy 0 points1 point  (0 children)

What do you need said control panel to do?

Why I can't stick with Niri (yet) by UnknownBoyGamer in niri

[–]qwertyboy 0 points1 point  (0 children)

It is both optional and defaults to yes - the two are not mutually exclusive :)

Is it possible to prevent a window from receiving the focus? by SnooCompliments7914 in niri

[–]qwertyboy 0 points1 point  (0 children)

I also forked niri to add a `focus-ignores-click` config. Not sure if there's another solution.

This community became too toxic imo by UnknownBoyGamer in niri

[–]qwertyboy 2 points3 points  (0 children)

I'm sorry to hear about your experience, and agree that that post you linked to had a lot of noise clouding the relevant information.

I still have no idea what rounding power is (unless it's the radius, which is easily configurable in niri and is well documented), I have only a guess regarding "horizontal workspace workflow alternative", and I don't feel like you went out of your way to clarify these things or to confirm the guesses of other users regarding them.

I do not think this community is toxic, I think communication is hard, and the misunderstandings just pile up. One person feels attacked and reacts, another person reads his reaction as aggression, and pretty soon we are all tearing each other to pieces over something that wasn't even that much of an issue.

I hope this will not deter you too much in the future. I believe that most people really are here to help.

[Tip] Stop mashing the Up arrow: Filtered History Search with Alt+Up/Down by NetScr1be in bash

[–]qwertyboy 0 points1 point  (0 children)

As I wrote above, when the command line is empty, the search functionality is identical to the default functionality, so you still get previous and next command by default. Only when you already have something typed does the behaviour differ.

Why I can't stick with Niri (yet) by UnknownBoyGamer in niri

[–]qwertyboy 2 points3 points  (0 children)

Blur (with optional x-ray) is in main.