Das hab ich damals gerne gelesen! Auch die ganze Buchreihe. Kann man heute immer noch gut dabei haben, wenn man unterwegs nicht dauernd aufs Handy gucken will.
Das hab ich damals gerne gelesen! Auch die ganze Buchreihe. Kann man heute immer noch gut dabei haben, wenn man unterwegs nicht dauernd aufs Handy gucken will.
I really appreciate #emacs #tramp, but when I use it to start a shell on a remote, a bunch of the environment info gets printed with command output. I believe this to be due to tramp forcing /bin/sh to create the shell, because when I open a shell with bash in the tramp session manually, everything looks fine.
After reading through the documentation, I found an alternative shell can be used if such an override is supported. It isn't stated explicitly, but I'm inferring that bash is not such a shell. At least, setting tramp-default-remote-shell to /bin/bash doesn't do anything.
I hope I'm missing something because I don't really want to shore up my bashrc to be sh compliant, and I don't really want to switch shells.
I recently changed jobs and found myself in a position where I would need to do a lot of work on remote machines. Since I am Emacs user, the most common way to do this is using TRAMP (Transparent Remote access, Multiple Protcol). TRAMP is an Emacs package that let’s you treat a remote host like a local system, similar to VSCode Remote Development Extension. I had used TRAMP before and it tended to be slow.