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

Feature/Documentation request: customizing remote shells #655

Open
mpedramfar opened this issue Feb 4, 2023 · 3 comments
Open

Feature/Documentation request: customizing remote shells #655

mpedramfar opened this issue Feb 4, 2023 · 3 comments

Comments

@mpedramfar
Copy link

When I open a buffer over ssh with tramp and open vterm there, the shell that's opened is not exactly identical to the shell I would get if I open vterm locally and then ssh. In particular, the prompt is different and the shell history file is overriden with tramp-histfile-override (#538).
I'm not familiar with tramp, so I can't say for sure if these are the only things that have been changed.

Would it be possible to have the option of opening a "normal" shell instead? If this can be done easily by changing some variables, it would be great to have it in README so that users could see the set of all options that they can configure for remote shells.
Thanks

@mpedramfar mpedramfar changed the title Feature request: Open a "normal" shell over ssh Feature/Documentation request: customizing remote shells Feb 6, 2023
@Bawaw
Copy link

Bawaw commented Jun 21, 2023

You can set the remote shell by setting the the vterm-tramp-shells variable.

E.g. if you want to use bash in your case:
(setq vterm-tramp-shells '(("ssh" "/bin/bash")))

@aramirezreyes
Copy link

I've been looking for this for a while, thanks! Where should I find this kind of documentation?

@Thaodan
Copy link

Thaodan commented Nov 12, 2023

You can set the remote shell by setting the the vterm-tramp-shells variable.

E.g. if you want to use bash in your case: (setq vterm-tramp-shells '(("ssh" "/bin/bash")))

I think this works quite good however it would be better if the login shell from the target host would be used on the remote.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants