antoyo
antoyo
Focusing an existing workspace would be better indeed. I'm not sure I understand why the workspace is lost, though. What do you mean by "lost workspace"? The workspace still exists....
Thanks for looking into this. Unfortunately, the problem is worse now: I get an empty workspace on both monitors. Plus, this issue now arises whether the focused workspace is on...
I'm still having some issues with that branch. This version will create an empty workspace when unplugging a monitor (no matter which workspace is focused). The original version (1.0) would...
There you go: [dvi_after_disconnect.txt](https://github.com/fogine/i3-workscreen/files/7557523/dvi_after_disconnect.txt) [dvi_before_disconnect.txt](https://github.com/fogine/i3-workscreen/files/7557524/dvi_before_disconnect.txt) [hdmi_after_disconnect.txt](https://github.com/fogine/i3-workscreen/files/7557525/hdmi_after_disconnect.txt) [hdmi_before_disconnect.txt](https://github.com/fogine/i3-workscreen/files/7557526/hdmi_before_disconnect.txt) [xrandr_after_disconnect.txt](https://github.com/fogine/i3-workscreen/files/7557527/xrandr_after_disconnect.txt) [xrandr_before_disconnect.txt](https://github.com/fogine/i3-workscreen/files/7557528/xrandr_before_disconnect.txt) I wonder if having the disconnected monitor being the primary one would cause an issue.
You're right, I do have the following for DVI after disconnect if I run the command "correctly": ``` { // workspace with 0 children "border": "normal", "floating": "auto_off", "fullscreen_mode": 1,...
> In the new branch I cannot recreate the behavior you described (no new workspace is created when I unplug one of the two monitors). Could you also post the...
Here's the output: ``` ========ACTIVE WORKSPACES==== {'DVI-D-1': '1'} ========VISIBLE WORKSPACES==== {'DVI-D-1': '2', 'HDMI-1': '1'} ========SWITCHING TO PREVISOUSLY VISIBLE WORKSPACE==== 2 ``` It doesn't seem to mention a workspace 10…
It says: ``` ========ACTIVE WORKSPACES==== {'DVI-D-1': '1'} ========VISIBLE WORKSPACES==== {'DVI-D-1': '2', 'HDMI-1': '1'} ========SWITCHING TO PREVISOUSLY VISIBLE WORKSPACE==== 2 ========FOCUSING WORKSPACE==== 2 ``` Removing the following line seems to fix...
The instructions are [there](https://github.com/rust-lang/rustc_codegen_gcc#how-to-build-a-cross-compiling-libgccjit), but as you can see, it's perhaps not as easy as it could be. Perhaps we could talk about how to make it easier. The first...
The only target I tried was one that wasn't supported by rustc (at the time). However, I guess a target that is Big-Endian and support 128-bit integers might be the...