This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-07
Channels
- # admin-announcements (3)
- # beginners (133)
- # boot (123)
- # capetown (2)
- # cider (21)
- # cljs-dev (1)
- # cljsrn (2)
- # clojure (32)
- # clojure-czech (1)
- # clojure-russia (2)
- # clojure-spec (72)
- # clojurescript (4)
- # datomic (28)
- # emacs (19)
- # funcool (1)
- # hoplon (10)
- # jobs-rus (1)
- # onyx (1)
- # other-languages (3)
- # protorepl (3)
- # re-frame (10)
- # reagent (76)
- # ring (2)
- # rum (2)
- # spirituality-ethics (61)
- # test-check (2)
- # testing (1)
- # untangled (3)
any reason pop-to-buffer
would be creating a new frame in my emacs?
and what would be the solution to stop it from doing that?
I don’t want new frames to be created, preferably just split windows
That doesn’t sound like default functionality. Are you using a pre-configured setup like Spacemacs or Prelude?
I’m using macOS Sierra
and emacs master 🙂
I don’t really know how to repro it, it really only happens in certain cases
yeah, it’s the public beta
specifically in haskell interactive mode
If the window to show BUFFER is not on the selected
frame, raise that window's frame and give it input focus.
It sounds like the buffer is on a different frame to start with, and pop-to-buffer
is just respecting that.
actually the problem seems to be switch-to-buffer-other-window