on-monitor-detected callback

[derrik-fleming]

Not sure how feasible this is as a feature, but for those who want to execute a callback when a secondary display is detected a callback or condition for the existing callbacks could be useful. These are just two things that came to mind immediately when trying to solve this. I'm open to suggestions if this is a solved problem using the provided configuration, or otherwise. I think it'd be easily achievable using the CLI commands in a shell script but I'd appreciate a way for handling it within the config if possible.

I like the idea of binding applications to workspaces with mnemonic names, my browser lives on workspace b, terminal emulator on t, etc. I set up the window detection callbacks for the apps that I care about to move them to the desired workspaces. This works great when I don't have my external monitor connected. However, my main external monitor is a ultra-wide and more than capable of having 2 or 3 applications side-by-side.

I want to bind applications to workspaces and I want separate bindings depending on whether or not specific external monitor(s) is connected. I also want to be able to execute commands when I connect my external monitor.

[fcaraujo]

++

I was about to suggest something similar and found this proposal. : )

I'm trying to run a command when the list of monitors changes (connecting/disconnection my 2nd monitor); in my case I want to trigger an event on my sketchybar as an example.

We could call it exec-on-monitor-change to follow the patter of the existing exec-on-workspace-change.

@nikitabobko I'm happy to jump on and learn how to contribute to the project if you or other maintainers are keen on having this in place, I'd just need some directions.

[nikitabobko]

The issue doesn't mention use cases

I'm trying to run a command when the list of monitors changes (connecting/disconnection my 2nd monitor); in my case I want to trigger an event on my sketchybar as an example.

Why do you add AeroSpace in the mix? Shouldn't it be handled purely by sketchybar?

We could call it exec-on-monitor-change to follow the patter of the existing exec-on-workspace-change.

I don't like exec-on-workspace-change callback, it's inconsistent with everything else. I hope that eventually exec-on-workspace-change will be replaced with: on-workspace-change = 'exec-and-forget ...'. But design questions of #278 and #351 has to be figured first

[derrik-fleming]

The issue doesn't mention use cases

@nikitabobko I've edited the original comment to include more details about my specific desires and use case.

[stschaef]

Building off of the original feature request

I'm looking for functionality that would allow aerospace to assign workspaces to take display precedence when an external monitor is connected. For instance, I'd like display my b, m, and c on each display by default when I connect to my external monitors at work, but aerospace will display workspaces 1, 2, and 3. A display callback could let me focus these upon connection

I also have a different monitor at home, and I'd like to configure some default tiling to trigger when that display is connected.

[fcaraujo]

@nikitabobko trying to oversimplify the use case(s): it's achieving the same or similar things you'd be able to do through exec-on-workspace-change.
I want to trigger X when I switch workspace => I want to trigger Y when I connect/disconnect a different monitor.

Integration with Sketchybar was just a silly example. : )
However, thinking about it, I could expand: I can have a single item on my bar, and when I switch workspaces it changes its label to the workspace id; let's call it "A" and "B".
Now let's say I have "B" automatically assigned to go into my secondary monitor.
So when I connect the 2nd monitor, I want to change the label item to "A | X" (and IMHO Sketchybar has no responsibility to know that, same as switching workspaces basically).

I know naming things is polemical, and it was a dummy suggestion; I'm not too fussed about it and just really interested in the capability itself (by the way, personaly I like and follow on-something when I'm developing - similarly to what you already stated anyway).

Keep up the great work mate and thanks for your attention.

[timharris777]

I was looking for this as well and came across this feature request. +1

It would be extremely useful for me to be able to exec a command when aerospace detects that a new monitor has been added or removed. Yabai currently offers this with the following:

yabai -m signal --add event=display_added action="command you want to run"
yabai -m signal --add event=display_removed action="command you want to run"