sshrc

Not OP, but a fan of Warp. > I - and I get the impression that's true for many developers - learned early to minimize the custom config. I get the exact opposite impression. My understanding is that as developers become more experienced, they tune their setup more, and have more and more persisted customizations. I consider sshrc[1] a critical part of my workflow for this reason. > But why would one need that? Is your environment that random? Most shells by default will occasionally spew out "garbage" text into the terminal like ^[[A. If you know why this happens it's possible to fix, but it's definitely a pain. Personally I consider it very important that all the places that I input text work consistently (e.g. move cursor by word, move cursor to end of line) and Warp providing that is a huge selling point to me. [1] https://github.com/d

You may be thinking of https://github.com/danrabinowitz/sshrc?

> Also, as mentioned below, this is for temporary environments where you read more than you edit. It might be more convenient to just do a one-time setup of something like "bring your .bashrc, .vimrc, etc. with you when you ssh" [0] (previously discussed on HN [1]). Personally, I've got a shell script that I just scp over and execute to set up my dotfiles (in a git repo) if they aren't already present on a host, but that may not be an option for some (although I guess I could use sshrc to do that too). -- [0]: https://github.com/danrabinowitz/sshrc (note: clone of the original repo, which now 404s). [1]: https://news.ycombinator.com/item?id=8343469