[i3run] Will not windows move to empty workspace

vn-ki commented

2018-09-20 14:28:15 +00:00

(Migrated from github.com)

I have this binding in my i3 config

bindsym $mod+Ctrl+f exec i3run -s -i "thunar" -e "thunar"

Suppose I move to an empty workspace, and the keys, it will open thunar for the first time correctly.
I press the keys again, it will hide thunar.
If I press again, I will be switched to nearest lower workspace and thunar will be shown.

This happens with empty workspaces only.

I have this binding in my i3 config ```i3 bindsym $mod+Ctrl+f exec i3run -s -i "thunar" -e "thunar" ``` Suppose I move to an empty workspace, and the keys, it will open thunar for the first time correctly. I press the keys again, it will hide thunar. If I press again, I will be switched to nearest lower workspace and thunar will be shown. This happens with empty workspaces only.

budRich commented

2018-09-20 16:28:36 +00:00

(Migrated from github.com)

Thank @vn-ki for an excellent report, I will investigate this. I think it's an easy fix.

budRich commented

2018-09-20 17:27:38 +00:00

(Migrated from github.com)

This issues should be fixed in the latest release (#33 ).

vn-ki commented

2018-09-21 14:56:16 +00:00

(Migrated from github.com)

Now it is behaving weirdly.

Whenever I press my keybindings (and I am in workspace 1, 2, or 3) it will take to workspace 4 and put thunar there.
If I am in a workspace 4 or above, it works without any problems. (even if workspace is empty)

Now it is behaving weirdly. Whenever I press my keybindings (and I am in workspace 1, 2, or 3) it will take to workspace 4 and put thunar there. If I am in a workspace 4 or above, it works without any problems. (even if workspace is empty)

budRich commented

2018-09-21 15:27:53 +00:00

(Migrated from github.com)

that sounds really strange, i will take a look. I only tested quickly on workspace 1 and 2.
Also, what are the names of your wokspaces? could you paste the output of:

i3-msg -t get_workspaces

that sounds really strange, i will take a look. I only tested quickly on workspace 1 and 2. Also, what are the names of your wokspaces? could you paste the output of: `i3-msg -t get_workspaces`

budRich commented

2018-09-21 15:38:40 +00:00

(Migrated from github.com)

i managed to reproduce this now, doesn't seem to have anything to do with workspace names, but the output could still be useful..

vn-ki commented

2018-09-21 15:50:03 +00:00

(Migrated from github.com)

$  i3-msg -t get_workspaces


[{'focused': True,
  'name': '1',
  'num': 1,
  'output': 'eDP1',
  'rect': {'height': 741, 'width': 1366, 'x': 0, 'y': 27},
  'urgent': False,
  'visible': True},
 {'focused': False,
  'name': '3',
  'num': 3,
  'output': 'eDP1',
  'rect': {'height': 741, 'width': 1366, 'x': 0, 'y': 27},
  'urgent': False,
  'visible': False},
 {'focused': False,
  'name': '4',
  'num': 4,
  'output': 'eDP1',
  'rect': {'height': 741, 'width': 1366, 'x': 0, 'y': 27},
  'urgent': False,
  'visible': False}]

Also, thanks for your quick responses.

``` $ i3-msg -t get_workspaces [{'focused': True, 'name': '1', 'num': 1, 'output': 'eDP1', 'rect': {'height': 741, 'width': 1366, 'x': 0, 'y': 27}, 'urgent': False, 'visible': True}, {'focused': False, 'name': '3', 'num': 3, 'output': 'eDP1', 'rect': {'height': 741, 'width': 1366, 'x': 0, 'y': 27}, 'urgent': False, 'visible': False}, {'focused': False, 'name': '4', 'num': 4, 'output': 'eDP1', 'rect': {'height': 741, 'width': 1366, 'x': 0, 'y': 27}, 'urgent': False, 'visible': False}] ``` Also, thanks for your quick responses.

budRich commented

2018-09-21 16:33:39 +00:00

(Migrated from github.com)

great. I think i have fixed it now. Yesterday when I applied the first fix, i added a new method to identify workspaces, and it currently coexist with the old one and there where some missmatching. But it should be fixed now, please try the latest release.

I will refactor and clean up the code of i3list for the next release.

great. I think i have fixed it now. Yesterday when I applied the first fix, i added a new method to identify workspaces, and it currently coexist with the old one and there where some missmatching. But it should be fixed now, please try the latest release. I will refactor and clean up the code of `i3list` for the next release.

vn-ki commented

2018-09-21 16:49:31 +00:00

(Migrated from github.com)

It's working perfectly now. Thanks.

On Fri, Sep 21, 2018, 10:03 PM Nils Kvist notifications@github.com wrote:

great. I think i have fixed it now. Yesterday when I applied the first
fix, i added a new method to identify workspaces, and it currently coexist
with the old one and there where some missmatching. But it should be fixed
now, please try the latest release.

I will refactor and clean up the code of i3list for the next release.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/budlabs/i3ass/issues/32#issuecomment-423596588, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aee-EA_nHBJDpvpYkZyXLdC6fWYtNlE2ks5udRTjgaJpZM4WyQHW
.

It's working perfectly now. Thanks. On Fri, Sep 21, 2018, 10:03 PM Nils Kvist <notifications@github.com> wrote: > great. I think i have fixed it now. Yesterday when I applied the first > fix, i added a new method to identify workspaces, and it currently coexist > with the old one and there where some missmatching. But it should be fixed > now, please try the latest release. > > I will refactor and clean up the code of i3list for the next release. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/budlabs/i3ass/issues/32#issuecomment-423596588>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/Aee-EA_nHBJDpvpYkZyXLdC6fWYtNlE2ks5udRTjgaJpZM4WyQHW> > . >

🎉 1

Rows
Columns

[i3run] Will not windows move to empty workspace #32