3 ms·
If you read the article, that's an option with Github's code spaces setup. > Visual Studio Code is great. It’s the primary tool GitHub.com engineers use to int
by selykg 5y ago
If you read the article, that's an option with Github's code spaces setup.
> Visual Studio Code is great. It’s the primary tool GitHub.com engineers use to interface with codespaces. But asking our Vim and Emacs users to commit to a graphical editor is less great. If Codespaces was our future, we had to bring everyone along.
snip
> From there, GitHub engineers can run Vim, Emacs, or even ed if they so desire.
- nsonha 5y agoThe lame part is that they have to spin up vscode just to ssh
- vbezhenar 5y agoI did not understand that part. Every heavy Emacs or vim user have its own customizations of editor. How does it work with shared image?
- zacmps 5y agoJust use an sshfs mount and a local editor.
- gnufied 5y agoI think this defeats the purpose of Codespaces, because it would mean that all the code runs locally and only thing that remote server provides is storage?
- gpanders 5y agoThe codespaces can have their own dotfiles.
- dcreager 5y agoThe repo owner gets to define the base Docker image that’s used in the codespace. And then it also looks for a dotfiles repo under your user account, which you can use to install all of your personal customizations. You can see mine at https://github.com/dcreager/dotfiles https://github.com/dcreager/dotfiles