@roygreenhilt
Grr! I'm coming to your house! By the way, where do you live? :)
There will be another new popular winner in the editor wars at some point. #emacs - my favorite - won't be that winner, or the next winner after that. But Emacs will be around, and it will continue to be very, very good. All you #vim, #sublimetext#textmate#notepadplusplus#atom#vscode users you are all still my brothers and sisters in software development. Though I have to say I am still giving the hairy eyeball to you Vim folks :)
Q for #rstats#quarto users in #vscode - am I right that there is no way to see the final appearance of a plot other than rendering the document? There is no preview - other than in rstudio - which gives an accurate representation? The vsc plot window follows its own dimension (distorts proportions).
Love vs code but re-rendering the whole doc for each plot iteration feels quite cumbersome. Tagging the mighty @andrew since I think there was a related discussion on GH which I can't find..🙏🙏👏👏
I've been messing with VS Code for a few days now (despite being an MS hater), and it seems quite good; "all" of my friends use it, and SublimeText is sort of feeling abandoned these days.
One thing that's bugging me, and I can't figure out how to fix it, is that every time the window loses focus, something is reformatting my text. Type "something " with a space, switch to check info, switch back and the space is gone. 🤷
As far as I can tell, Microsoft's vscode team broke every color scheme with a January update. If you install a color scheme ("theme" in vscode speak), then open a file in the Go programming language, it won't look like the advertised color scheme. https://github.com/microsoft/vscode/issues/203998
Every color scheme but one, that is: the GitHub (owned by #Microsoft) color scheme appears to be unaffected.
They've closed the user-reported issue with "as designed".
This is a great workshop by Pamela Fox and Olivia Guzzardo McVicker for setting a dockerized 🐳environment in VScode with the Dev Containers extensions to connect to a Postgres 🐘 database with Python 🐍 and SQL.
Latest release of the #OPA#VSCode extension integrates #Regal for linting right in your editor! This was something I have wanted since I started working on Regal over a year ago, so to finally see it happen is quite rewarding 😍 Thanks @charlieegan3 for your exceptional work on this!
Motherfuckers will spend hours of their life tweaking and fixing their vim config just to get the same functionality as a fresh VSCode install. Get a real job.
#VSCode Profiles are very sweet. For those who don't know, you can have different extensions, snippets, and keyboard shortcuts for different purposes. Maybe a different language, a different stack, or various work and study environments.
Can anyone here tell me how to stop the #vscode#R linter highlighting lines where I define functions which have a na.rm argument, because it's not snake case? I've read as much as I could find about linter options but couldn't find the right one (camel case option yes, dot case no). The highlighted lines are distracting my brain ferrets, and I won't change the case of the option, because standards are a Thing.
Arbeite heute mal wieder unter Linux an meinem Spiel, allerdings treibt mich Visual Studio Code in den Wahnsinn. IntelliSense funktioniert nicht, weil es die ganze Zeit updated. Bis die git-Quellen angezeigt werden, dauert es 5 bis 10 Minuten, und beim Speichern einer Datei startet der den "C++ Formatter", der dann ebenfalls minutenlang blockiert. Frust.
Wahrscheinlich haben alle Probleme die gleiche Ursache, nur welche? Habe VS Code schon testweise gelöscht (Plugins und Config). Sobald ich die C++-Plugins installiere, ist das Problem wieder da. Ich tippe auf IntelliSense.
@weirdwriter@pixelate@halisonjl@weirdwriter, that article is a fantastic resource! Please do continue to keep it up to date with your discoveries. If I had found it earlier it could have saved me work discovering things on my own - then again, I do like figuring things out so I might have done the same anyway, just with a better start point.
When I was considering my options for tools to (re)learn to use after my vision loss my primary focus was on regaining my ability to write code instead of documents as that was more central to the type of work I did at the time. While I found learning to use #VSCode effectively with a screen reader to be a very frustrating and time-consuming process, it made sense at the time, and proved well worth it to me in the long run. After (re)learning to use it to code, discovering I could use it for #markdown as well was a very nice bonus. It is very web app like and can be very difficult to use with a screen reader without learning a library worth of hotkeys/key-binding/keyboard-shortcuts. If I had not already needed to learn them for coding, I don't know that I would have tried for writing documents alone. I have been consider switching to #vscodium. Less telemetry definitely appeals to me.
Thanks again for referencing that article! I'll definitely be giving it a follow.