Not too long ago (maybe with my Sequoia improve, however probably earlier than) I’ve seen that purposes that you simply’d anticipate to come back to the foreground not do. For instance: after I open an Emacs window from my Warp terminal, the Emacs window used to come back to the foreground. Now it would not. Second instance: if Courageous is within the foreground and I take advantage of my scorching nook to activate Mission Management, click on on another window (I’ve seen this with Preview), Courageous stays within the foreground.
Is there a brand new setting I am lacking, or what?
Edit: some new info from extra experimentation:
- If I begin with my Warp window within the foreground and begin up a brand new Emacs session (i.e. begin the appliance) from the command line, Warp retains the foreground. But when Emacs is already working and I add one other file to the window (by way of “emacs foo”) from the command line, Emacs correctly involves the foreground.
- If I begin with my Courageous window within the foreground and go to Mission Management utilizing a scorching nook, clicking on a Preview window causes that window to come back to the foreground, and Courageous instantly grabs focus again. But when I do the identical, and click on on a Skim or Emacs window, issues behave correctly.
I discover this all extraordinarily odd and complicated.