this post was submitted on 01 Sep 2023
337 points (96.2% liked)

Programming

17407 readers
76 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] exi@feddit.de 7 points 1 year ago* (last edited 1 year ago) (2 children)

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.

[โ€“] tatterdemalion@programming.dev 2 points 1 year ago* (last edited 1 year ago) (1 children)

That really is one hell of a hot take

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.

[โ€“] stinodes@lemmy.world 2 points 1 year ago

I almost exclusively do front end, in exclusively nvim. Exactly like you say, just have a browser window (or 2) permanently open.

[โ€“] xigoi@lemmy.sdf.org 1 points 1 year ago* (last edited 1 year ago)

the zoomed out preview on the right

https://github.com/gorbit99/codewindow.nvim

GUI color picker directly in my editor

https://github.com/uga-rosa/ccc.nvim

inline preview of latex

https://github.com/jbyuki/nabla.nvim