lintplus VS vscode-remote-release

Former contributor and user of Lite XL here.

It's an awesome little editor. I quit using it though because it seemed like the future direction of the project wasn't very clear, and from a practical standpoint VS Code simply has a better developer experience, but I had great fun hacking around it nevertheless.

One of my favorite things about rxi/lite and Lite XL is just how easy it is to write plugins. Simply create a new .lua file in the plugins directory and monkey-patch whatever you need. And while it might seem like monkey-patching isn't the most clean solution, that's not exactly true — the source code of the editor doesn't need to be cluttered with explicit hooks, and plugins interoperate with each other very well, because one plugin doesn't know about the others' existence. From its standpoint it just modifies the vanilla editor.

This extensibility allowed me to write some really cool stuff, the one plugin I'm especially proud of is lint+ [1], which leverages the immediate mode nature of the UI to draw pretty lint messages atop the text editor (and it even renders Rust's friendly compiler errors with little rails on the left! see issue #3 [2]).

Can recommend.

  [1]: https://github.com/liquidev/lintplus

I desperately want this. I find text editors w/ basic linting to be too limited but full IDE's like Idea or even VSCode too heavy for some devices. Something in between :(. I've given up laptop development and am forced to work with my desktop until I can afford a better laptop because Idea/VSCode runs so slowly.

FWIW, I use lite (https://github.com/rxi/lite) if I need a very lightweight text editor that has rust linting (https://github.com/liquidev/lintplus) and Idea if I'm at my desktop.

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