News for hackers. Stuff that matters.
Re:GitHub’s engineering team has moved to Codespaces by selykg on Wednesday August 11, 2021 @01:34PM (#28145049)
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.

Re:GitHub’s engineering team has moved to Codespaces by vbezhenar on Wednesday August 11, 2021 @04:31PM (#28147366)
I did not understand that part. Every heavy Emacs or vim user have its own customizations of editor. How does it work with shared image?
Re:GitHub’s engineering team has moved to Codespaces by dcreager on Wednesday August 11, 2021 @08:07PM (#28149901)
The 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
Re:GitHub’s engineering team has moved to Codespaces by gpanders on Wednesday August 11, 2021 @05:41PM (#28148171)
The codespaces can have their own dotfiles.
Re:GitHub’s engineering team has moved to Codespaces by zacmps on Wednesday August 11, 2021 @05:35PM (#28148114)
Just use an sshfs mount and a local editor.
Re:GitHub’s engineering team has moved to Codespaces by gnufied on Wednesday August 11, 2021 @10:11PM (#28150836)
I 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?
Re:GitHub’s engineering team has moved to Codespaces by nsonha on Wednesday August 11, 2021 @03:20PM (#28146437)
The lame part is that they have to spin up vscode just to ssh