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
Description:
Shell layer shell buffer doesn't obey location property when the default shell is 'shell
Reproduction guide:
Start Emacs
run <SPC '>
Observed behaviour:
Starting the shell buffer by pressin <SPC '> brings it up at the top of the frame, or in an already created split window. Not the bottom as requested by setting 'shell-default-position to 'bottom
Expected behaviour:
Shell buffer should appear at the bottom. Note, this works if I set 'shell-default-shell to 'ansi-term; but I prefer using 'shell.
Sounds like either #7691 (upstream bug in shell-pop, reproducible in stock Emacs) or #8171 (some clash between window-purpose and shell-pop). @MRFaria can you verify that your problem either reproduces with stock Emacs, or disappears if you disable purpose-mode?
Disabling purpose-mode doesn't do anything, but it looks like the issue still happens in stock emacs.
I installed shell-pop through marmalade: M-: (add-to-list 'package-archives '("marmalade" . "http://marmalade-repo.org/packages/")) M-x package-refresh-contents M-x package-install [RET] shell-pop
Then I customised shell-pop to appear on the bottom: M-: (require 'shell-pop) M-x customize-set-variable [RET] shell-pop-window-position [RET] bottom
Then, when running shell-pop it appears on the top of the frame anyway
Description:
Shell layer shell buffer doesn't obey location property when the default shell is 'shell
Reproduction guide:
Observed behaviour:
Starting the shell buffer by pressin <SPC '> brings it up at the top of the frame, or in an already created split window. Not the bottom as requested by setting 'shell-default-position to 'bottom
Expected behaviour:
Shell buffer should appear at the bottom. Note, this works if I set 'shell-default-shell to 'ansi-term; but I prefer using 'shell.
System Info:
The text was updated successfully, but these errors were encountered: