Really hard to do in a terminal.
If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is.
Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates.
Another example: inline preview of latex or Template fragments.
Yea well most of the comments in here are lukewarm takes so… there you go.
I for one really love the zoomed out preview on the right that has become popular in recent years.
I almost never navigate code based on its order or “shape” in the file. LSP-based symbol tagging or searching is way faster than scrolling. I guess you can click the spot on the preview that you need, but I refuse to reach for my mouse while editing text.
Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is.
I use LSP integration to see a complete list of errors/warnings and jump to them.
Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates.
That’s for design, not text editing ;)
inline preview of latex or Template fragments.
I will use a latex or markdown language server that renders to a browser tab.
To be fair, I don’t do HTML/JS/CSS, so I bet VSCode or other GUI editors are great for that. But that’s specifically because you want to see something rendered. Most of the time you can just see it in an actual browser next to your text editor though.
The only thing a GUI text editor can be better at than a terminal editor is making it easier to use the mouse.
That really is one hell of a hot take 😀
I for one really love the zoomed out preview on the right that has become popular in recent years.
https://jason-williams.co.uk/assets/img/2020/debugging_screenshot.png
Really hard to do in a terminal. If you have errors you can see very fast where they are located/clustered in the file and can already tell just by the shape of the program where it is.
Another example: GUI color picker directly in my editor as a tooltip above color values in css/html templates.
Another example: inline preview of latex or Template fragments.
Yea well most of the comments in here are lukewarm takes so… there you go.
I almost never navigate code based on its order or “shape” in the file. LSP-based symbol tagging or searching is way faster than scrolling. I guess you can click the spot on the preview that you need, but I refuse to reach for my mouse while editing text.
I use LSP integration to see a complete list of errors/warnings and jump to them.
That’s for design, not text editing ;)
I will use a latex or markdown language server that renders to a browser tab.
To be fair, I don’t do HTML/JS/CSS, so I bet VSCode or other GUI editors are great for that. But that’s specifically because you want to see something rendered. Most of the time you can just see it in an actual browser next to your text editor though.
I almost exclusively do front end, in exclusively nvim. Exactly like you say, just have a browser window (or 2) permanently open.
https://github.com/gorbit99/codewindow.nvim
https://github.com/uga-rosa/ccc.nvim
https://github.com/jbyuki/nabla.nvim