Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make shell-default-term-shell affect multi-term #5818

Closed
darkfeline opened this issue Apr 17, 2016 · 4 comments
Closed

Make shell-default-term-shell affect multi-term #5818

darkfeline opened this issue Apr 17, 2016 · 4 comments

Comments

@darkfeline
Copy link
Contributor

Currently shell-default-term-shell only affects the default shell in term and ansi-term, not multi-term (which is determined by shell-file-name). I think it would be more consistent to make multi-term affected by shell-default-term-shell as well.

This is especially apparent if one is using a dumb shell for shell-file-name and a smarter one for *-term.

@moritzschaefer
Copy link
Contributor

moritzschaefer commented Oct 10, 2018

Calling
(setq shell-file-name "/bin/bash")
in user-init (and/or user-config) also doesn't change my shell (default is zsh) as suggested in
https://emacs.stackexchange.com/questions/28647/how-do-i-change-the-default-shell-for-shell-command?newreg=7645bedc8728440697192caa5b4634ce

@d12frosted
Copy link
Collaborator

I never used multi-term nor I have it installed on my machine. But after looking at its source code (I hope I found the right one) I think you can try setting the value of multi-term-program. E.g.

(setq multi-term-program "/bin/bash")

You can also try using Emacs describe functionality to find this variable. Either C-h v or SPC h d v and type multi-term to see what variables it exposes.

@d12frosted
Copy link
Collaborator

Ok, I have just tried it and it works.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Mailing list
  
Other
Development

No branches or pull requests

6 participants