this post was submitted on 01 Sep 2023
319 points (96.0% liked)
Programming
17313 readers
209 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.