3 ms·
Tried an alternate shell for a while, ran into the basic problem that the moment I SSH'd somewhere else it was gone, and my instincts for how to get things done
by XorNot 6y ago
Tried an alternate shell for a while, ran into the basic problem that the moment I SSH'd somewhere else it was gone, and my instincts for how to get things done expediently were degrading.
If I was going to use an alternate shell, it's got to have some solution for this problem that's transparent - something I can load into any sh/bash environment to get it running remotely.
- pletnes 6y agoThis is one reason I like zsh - they are extremely compatible. I also have a different prompt so I immediately notice if I’m inside zsh.
- circularfoyers 6y agoThis is why I ended up sticking with zsh after I tried fish for a period. I liked some of fish's features, so I used the two plugins fast-syntax-highlighting and zsh-autosuggestions to get the same features in zsh.
- antihero 6y agoIt'd be cool if there was something like VSCode's model where it set up some sort of daemon that provided a shell environment (instead of an editor) remotely. Perhaps mosh can do something like that? Or even just a script which could quickly bootstrap a shell and dotfiles on a system.
- bandie91 6y agosomething like Plan9's cpu server would help here: you "mount" your shell/IDE environment from your computer and "mount" the other computer's cpu, memory, and fs over ssh. "mount" is in quotation because in Plan9 you not only can mount fs but cpu, network interfaces, desktop windows and what not too.
- Frost1x 6y agoThis is the core problem with so many software efforts now, there are just too many efforts that portability suffers. I remember years ago mucking around with my home computing environment, making it so convenient, custom UI shell, monitoring widgets, highly customized bash environment with all sorts of fancy utilities that were just so handy, and all sorts of nifty features everywhere to tackle any problem I encountered. Alas, the second I went anywhere else to do something--some friend or business's system, none of that underlying infrastructure existed. I lamented, "oh if only these other people followed my model I could just use X right now," life would be better. At some point in my career I realized I was just wasting a whole lot of time customizing my native environment because those features were non-portable and the more I dealt with working in other people's environment, the more I realized I should just focus on learning the best way to do things in the popularly adopted environments because it meant my knowledge transferred almost everywhere.
- pessimizer 6y agoI'm the same way, and I don't think it's ideal. I tend to do my work with the minimal set of tools that I usually expect to be available, and I'm extremely biased towards using the default settings and configurations of those tools. I do have settings that I really prefer so I have to use, but I naturally keep them to a short list that I can set up within a minute or five. I can tear them down in a minute or five also - I may not be using my account; I often find myself on Company X's account installing Company Y's software on Company Z's servers, and I wouldn't want someone else coming after me to be confused. I don't even really change the wallpaper on a desktop anymore, feels like polishing a hammer, a waste of time. I wish you could carry your environment around with you, but I don't see how it could possibly work that way neatly. An exception is that I usually end up installing a lot of stuff on Windows desktops to make them vaguely usable and scriptable, but Powershell and WSL will probably eventually mean I give up doing that, too. The previous sentiment was really about UNIXy systems.
- astrostl 6y agoThis is the fundamental divide on dev and ops environment customizations.
- jaegerpicker 6y agoI always wished for a ssh environment that worked more like a client server app. In other words you could connect to the remote server but your shell is still the one that take the calls and dispatches them like api requests. The remote server can still be as secure as the api exposed is only the ones that the user has permission for. The big difference is that your shell and tools are always the same and it would allow to easily run commands both locally and remotely in the same shell/session. More easily share data. There are probably good reasons to not do this but I think it would be a far better user experience.
- chubot 6y agoOil is a gradual upgrade path from bash for this reason: https://news.ycombinator.com/item?id=26125013 https://news.ycombinator.com/item?id=26125013 It won't immediately solve the problem, but it can eventually. It can be the default and only shell on a Linux distro, whereas shells like fish can't, because they would make the system non-POSIX.