atom VS vscode-remote-release

I thought a lot of the Atom developers moved to create Pulsar Editor.

https://pulsar-edit.dev/

Also, the community forked Atom into a community edition (CE), still getting updates?

https://github.com/atom-community/atom/

What makes this "Atom Developer Editor" different than Pulsar or Atom-CE.

There's https://github.com/atom-community/atom, hoping that or similar will gain traction

A couple community maintained Atom forks have emerged: Atom Community and Pulsar. Of the two, Pulsar seems to be more actively developed.

Yes, I know Microsoft is archiving the Atom editor repo, but a public fork lives on. https://github.com/atom-community/atom/ atom-slime is probably still my favorite of the bunch. It actually uses Emacs SLIME. But I haven't looked at it in a couple years or longer.

Looks like the Atom community also started a fork of Atom a while back: https://github.com/atom-community/atom/

There is this: https://github.com/atom-community/atom

If you haven't heard, MS is retiring Atom in December 2022. I assume most of us will try the Atom community fork. But as back-up, etc., what editors are folks thinking about / exploring?

After the announcement of Atom sunset, people started to continue it as a community fork. It seems it's growing and drawing attention: At July 10th (two days after the announcement), it had 86 stars, but now it has more than 230! It may be no comparable to the star count of Atom itself (around 58k), but it's rising.

But - the community is taking the job to reimplement the servers. We're not sure about teletype, but packages will be able to be installed - well, in a different Atom binary that the community will provide. For more info: https://github.com/atom-community/atom/discussions

It would be great, if people interested in this feature/having similar problems would consider pushing the following issue: https://github.com/microsoft/vscode-remote-release/issues/8373

The other option may require that you add the Remote X11 extension to VSCode (Unless Microsoft has undone the damage they did to their OpenSSH client in the last few years in which case you could just enable X11 forwarding in your ssh options) if you're trying to execute everything from VSCode, and you would have to have a suitable browser or viewer installed on the remote server along with the xdg-utils package (or whatever contains xdg-open if you're not running Debian).

Take a look at this: https://github.com/microsoft/vscode-remote-release/issues/6375

If it's "The connection to the terminal's pty host process is unresponsive, the terminals may stop working", apparently it's an old problem: https://github.com/microsoft/vscode-remote-release/issues/7964

VSCode with Remote-Container extension installed.

Possibly related github issue?

This might be it.

Hello! I came across this Github issue that I think would be helpful for remote workers. It's about the possibility to connect to an existing tunnel by using the terminal of OS instead of VSCode UI. This would allow us to use tunnels as a full SSH replacement in scenarios where SSH itself isn't possible. If you think this would be helpful, please upvote the issue here: https://github.com/microsoft/vscode-remote-release/issues/8238