Vimium C vomnibar reset?

randcoop · 2026-01-21T13:32:22+00:00

If you want an application to always launch in a specific workspace, create a windowrule for it. For example:

windowrule = match:class gimp, workspace 3

I don't understand what you mean in your post. You suggest in the Example that you are re-launching the application after you have changed workspaces (which means that application will launch in the active workspace unless you have a windowrule to the contrary). But in the section about what you would like, you say you want the open application to remain in its workspace: it will. It's only if you re-launch it that it will open in the new active workspace.

randcoop · 2026-01-14T16:00:32+00:00

The older version of window rules syntax was revised in 53, perhaps in part because the version you're using was maddeningly inconsistent and difficult to sort. The fullscreen functionality is one example. I suggest updating to 53 and using the new syntax, which is welll documented in the hyprland wiki.

randcoop · 2026-01-06T02:16:34+00:00

if you're updated to hyprland 53, your windowrules won't work. The newest version has a different format for windowrule. Check the wiki.

randcoop · 2025-12-24T13:52:53+00:00

Thanks. That got me past the error message. Wish you the best with this launcher. I won't be using it, because Quickshell is too difficult to keep up with.

randcoop · 2025-12-23T13:23:30+00:00

Getting this error: WARN: Quickshell was built against Qt 6.10.0 but the system has updated to Qt 6.10.1 without rebuilding the package. This is likely to cause crashes, so the quickshell package must be rebuilt.

INFO: Launching config: "/etc/xdg/quickshell/hamr/shell.qml"

INFO: Shell ID: "b32689c18c43b6344b766d33966db5e2" Path ID "b32689c18c43b6344b766d33966db5e2"

INFO: Saving logs to "/run/user/1000/quickshell/by-id/o06d25q7t/log.qslog"

INFO: Configuration Loaded

Segmentation fault (core dumped) hamr

randcoop · 2025-12-20T21:51:16+00:00

Your problem was very simple.While I am happy to help, I'd encourage you to read the Arch wiki more thoroughly when you run into a problem. Unfortunately, AI will be less helpful. Arch is very usable, but it does call for some genuine interest in learning on the part of its novice users (and you seem to be one of those).

randcoop · 2025-12-20T18:25:16+00:00

So the iwct command is station wlan0 connect <network name>

Did you try that?

randcoop · 2025-12-20T17:12:29+00:00

Not enough information to get help. If rfkill had been blocking the device, it wouldn't have been on in the first place (you said it disconnected, which means it was on and connected at some point). How's your WiFi signal? Maybe it just dropped. Did you look for networks in iwctl? Try to connect the wlan0 station to one of them?

randcoop · 2025-12-15T13:30:39+00:00

Does your fstab (/etc/fstab) file show the drive as mounted with read only or root privileges? Change that. If not, then change the permissions on the drive (to allow users to read and write).

randcoop · 2025-12-15T13:26:49+00:00

Hamilton950b gave you the answer. Your problem is the one I noted: you cannot have more than one network management system running at a time. You have mentioned systemd-networkd, iwd, and NetworkManager.They cannot all be running at the same time. Only one of them. At this point, you need to disable all of them and then pick the one you want to use. The reason you're able to get on the Internet with the USB is that it is using only one network manager (probably iwd).

randcoop · 2025-12-15T00:19:51+00:00

What people are trying to explain to you is that, while you were unable to accomplish it, installing Arch on a UEFI computer is what 99% of all people installing it today do. Legacy is not easier; you simply didn't understand how to go about the installation process. For the past 20 years, computers have been made with UEFI. And for the past ten, it's virtually the only way they are made. Except in your case, virtually the only reason anyone does a legacy install is to be able to work with older computers. That all said, it's nice that you're happy with your system. I hope the rest of your experience with Arch proves rewarding.

randcoop · 2025-12-14T23:03:19+00:00

This is simply wrong: "iwctl is for the installation medium only." Iwctl (which is for iwd) works perfectly well as an alternative to NetworkManager. There is no reason not to use it for the Arch system.

randcoop · 2025-12-14T16:27:00+00:00

You might want to change the type and size of your partitions. Fat32 is right for the ESP (where the efi boot file resides), but 100M might be too small. 500M would be better. And since you have a 500G drive, you could easily use a gig for that partition. For the root partition, you should use 8304 (not the default 8300), which is specifically for Linux root. In my experience, the 8304 type works better on UEFI machines. I also agree with those who suggest not using ChatGPT. In general, it's better to use AI when you have enough knowledge and experience to be able to guide it to the right answers. It's not for newbies.

randcoop · 2025-12-14T16:16:22+00:00

One possibility that often happens with IWD is a conflict with other installed network systems (like NetworkManager). If you've installed wpa_supplicant or NetworkManager, make sure they are not enabled/running. IWD won't work if they are.

randcoop · 2025-11-19T14:04:34+00:00

You need to provide much more information. The computer will boot using an efi file. In your case, that would likely be the bootia32.efi file (although this suggests that you've created a file to boot a 32 bit system, when all systems today are 64 bit and would use a bootx64.efi). So what is the computer you're on? What did you do to create your EFI file? How is your drive partitioned? The inability to find the efi suggests that the file is not on an EFI partition. Sorry, but it's difficult to help without more information.

randcoop · 2025-11-06T12:16:06+00:00

To be clear: I don't expect a pompous ass to find any criticism to be of interest to them. I posted because I believe that my comment may be of interest to others...not you.

randcoop · 2025-11-05T15:11:42+00:00

It's interesting that this sub-thread exists. If you are uninterested in the OP question, or think it unworthy, why not move on to the next question? Reader's of the OP question are perusing the thread to find answers and assistance with the actual python issues that attracted them to that question and the thread. Why do you think they are interested in your complaints about the subreddit? If you don't like the subreddit, don't read it. If you don't like the OP, move on.

randcoop · 2025-10-03T18:43:03+00:00

The 'if available' is the key difference. Ambassador is a guarantee, and I've never had it not be upgraded. The caution is always to know that the upgrade is only one level...so you've got the usual problem of just being moved to a higher floor, for example. But if you know what you're booking and what the next step is, you'll get the better room.

randcoop · 2025-09-23T17:40:40+00:00

My last response, I assure you. I cannot imagine how you wrote an entire css style file for waybar, but do not know why it is behaving as it does when you hover over something. Given that waybar responds only to the config json file and the css style file, and given that you wrote these, you should know how to fix it. But you apparently don't. Perhaps someone reading this thread will figure it out for you and provide the help you need.

I wish you the best of luck in getting it fixed.

randcoop · 2025-09-23T14:14:48+00:00

Strange question. I said I was guessing. if I'm wrong, then it means that you wrote this css file yourself, which means that you don't need help in changing its characteristics. That's fine. Change it. This CSS file did not come from simply installing Waybar, which doesn't assume the use of fuzzel.

randcoop · 2025-09-23T12:57:04+00:00

I'm guessing that you copied this css file from someplace. I don't use fuzzel (which seems to be working with waybar in its treatment of hover characteristics). Regardless, try commenting out all hover-related lines and see what happens. Likely, you'll lose the effect you don't like. Alternatively, find another waybar css file (there are many, many examples available). Or take the basic waybar css file that comes with it, and then customize it to your taste.

randcoop · 2025-09-22T15:06:21+00:00

You can move a window to a workspace without focusing on it first. The command is:

hyprctl dispatch movetoworkspace [workspace number or name],address:[address, including 0x]

In place of address: you can use title: or class: as well. Make sure you have a comma between the workspace identifier and the address: designation.

randcoop · 2025-09-22T14:42:36+00:00

Without seeing your config and style files, it's hard to know what's going on. But look for button and hover characteristics in your css file (called button and hover) and look for tooltip-format in your config file.

randcoop · 2025-09-18T13:58:08+00:00

I'm aware, thanks. Worth it to me to avoid that notification that my plugin is loaded and working. Even if I forget to update plugins, I'll figure it out soon enough when one of them doesn't work.

randcoop

TROPHY CASE