open results buffer in other window about deadgrep HOT 7 CLOSED

OK, I think we have consensus on changing the logic to switch-to-buffer-other-window. Both seem natural to me, and the reasons you mention (popwin, pop-up-frames) seem sufficiently compelling to change default behaviour.

I've rolled the version number: I tagged the previous commit as 0.8, and added a note in CHANGELOG.md about this change in 0.9. If this breaks anyone's workflow, let me know.

from deadgrep.

I think using switch-to-buffer-other-window and find-file-other-window by default is the right choice, since they respect the pop-up-frames variable and do the expected thing for folks who configured it. If the current default behaviour of clobbering windows is desired, maybe put it behind a configuration flag?

FWIW, I am not saying the current behaviour is bad, I just think using the mentioned default makes deadgrep behave more intuitive and predicable in light of the broader Emacs ecosystem (i.e., as in expecting a replacement for rgrep.)

from deadgrep.

changing (switch-to-buffer) to (switch-to-buffer-other-window) seems to do the right thing for me, but changing one hard-coded behaviour with another doesn't seem the right approach. ;)

from deadgrep.

Have you tried deadgrep-visit-result-other-window, which is bound to o?

from deadgrep.

i am aware of that command, but it's for jumping to results. i want the deadgrep buffer itself to open elsewhere.

sorry if i was not clear.

from deadgrep.

yeah, popwin seems to be unable to control the deadgrep window , I guess it's because what @eugeneia says. Kind of a large usability issue for me. (I solved it by matching against deadgrep-mode instead of buffer name regexp, still have to apply the switch-to-buffer-other-window change though)

from deadgrep.

thanks, @Wilfred. i guess this could even be made customizable since people seem to have different preferences.

from deadgrep.