You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 15, 2021. It is now read-only.
Frame-workflow uses select-frame-set-input-focus for selecting a frame by default. This function works poorly on EXWM with multiple monitors. It seems to display the frame always on the first monitor, at least in my environment. This issue may be solved by using a different function to switch frames, but even exwm-workspace-switch seems to work in a similar way. Maybe I have to implement a new function to select a frame on EXWM.
The text was updated successfully, but these errors were encountered:
I have recently added frame-workflow-exwm.el module which includes frame-workflow-exwm-swap-workspaces command. It swaps two visible workspaces, and if there are only two monitors, it doesn't require any user input. EXWM has a built-in command named exwm-workspace-swap, but it lets you select two workspaces by numbers from any workspaces including hidden ones, which is not easy to use for me.
Workspace switching on EXWM got easier by combining the following methods:
Display a list of EXWM workspaces on lemonbar with my custom config
Use an EXWM built-in exwm-workspace-switch command to switch to a hidden workspace.
Use frame-workflow-exwm-swap-workspaces to swap positions of two visible workspaces.
Use exwm-window-go to switch between visible workspaces.
Frame-workflow uses
select-frame-set-input-focus
for selecting a frame by default. This function works poorly on EXWM with multiple monitors. It seems to display the frame always on the first monitor, at least in my environment. This issue may be solved by using a different function to switch frames, but evenexwm-workspace-switch
seems to work in a similar way. Maybe I have to implement a new function to select a frame on EXWM.The text was updated successfully, but these errors were encountered: