Skip to content
This repository has been archived by the owner on Apr 24, 2020. It is now read-only.

SSH session #253

Closed
miguelcarax opened this issue Apr 24, 2016 · 3 comments
Closed

SSH session #253

miguelcarax opened this issue Apr 24, 2016 · 3 comments

Comments

@miguelcarax
Copy link

miguelcarax commented Apr 24, 2016

Could be possible to keep the theme appearance within a ssh session? just changing the user and host names. Thanks!

@dritter
Copy link
Member

dritter commented Apr 25, 2016

There is no easy way powerlevel9k (or any other ZSH-theme) could provide this.

IMHO the only valid way is to install ZSH on the other machine, set your user account there to use this shell, and install powerlevel9k there.. Using a dotfiles repo would allow you to share your powerlevel9k-copy across machines.

I've seen People hacking their SSH to copy a whole bunch of files to the remote machine, when the log in there. But that is really hackish, and error prone (like you would have to check if ZSH is installed and used; copy powerlevel9k over; copy your config, etc).

@wadkar
Copy link
Contributor

wadkar commented Apr 27, 2016

if its a machine you regularly ssh into, its much better to install zsh and pull your config files (you track them in a repo, don't you?)

@bhilburn
Copy link
Member

Yeah, this isn't really something that shell settings, of any form, could solve. What you really need to do is replicate your workflow on the machine you are working on.

To suggest an alternate method, if it works for you, if you are doing development remotely you could simply mount the remote directories with sshfs and then use your local workflow for your toolchains. This is a workflow I commonly use to write code on other machines, and it works really well.

Closing out this bug as it's not something we can really fix, but feel free to continue posting alternative solutions! =)

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

No branches or pull requests

4 participants