home.social

#vs-code — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #vs-code, aggregated by home.social.

fetched live
  1. Comenzamos directo de desarrollo!! Vamos a desarrollar una extensión de vscode para raylib. #gamedev #raylib #vscode

    twitch.tv/makeclassicgames

  2. Comenzamos directo de desarrollo!! Vamos a desarrollar una extensión de vscode para raylib. #gamedev #raylib #vscode

    twitch.tv/makeclassicgames

  3. Updated my guide on using LLMs with #Rstats (including #Rstudio, #Positron, and #VSCode options) to be more BYOK friendly and reflect changes in both VS Code Chat and Posit Assistant.
    github.com/tpavlic/docs-and-gu

  4. Updated my guide on using LLMs with #Rstats (including #Rstudio, #Positron, and #VSCode options) to be more BYOK friendly and reflect changes in both VS Code Chat and Posit Assistant.
    github.com/tpavlic/docs-and-gu

  5. #VisualStudioCode, when you move the window from one monitor to the other with Win-Key+Direction Key, then minimize, and restore the window, it'll come up on the monitor it moved away from, not the one it got minimized on.

    #VSCode #VisualStudio

  6. #VisualStudioCode, when you move the window from one monitor to the other with Win-Key+Direction Key, then minimize, and restore the window, it'll come up on the monitor it moved away from, not the one it got minimized on.

    #VSCode #VisualStudio

  7. Save yourself repetitive typing: CMake can read configuration values straight from environment variables, letting you set your preferred generator, enable compile_commands.json, and more - once in your shell config, applied to every build folder from then on.

    For example: set CMAKE_GENERATOR=Ninja to skip typing -G Ninja every time.
    It's not just cmake, either - ctest reads environment variables too. Set CTEST_OUTPUT_ON_FAILURE=1 and you'll always see output from failing tests.

    This complements CMake presets rather than replacing them: presets define per-project option sets, environment variables carry your personal defaults into every new project you create.

    Full details: kdab.com/%C2%B5-boosting-your-

    #CMake #CPlusPlus #VSCode

  8. Save yourself repetitive typing: CMake can read configuration values straight from environment variables, letting you set your preferred generator, enable compile_commands.json, and more - once in your shell config, applied to every build folder from then on.

    For example: set CMAKE_GENERATOR=Ninja to skip typing -G Ninja every time.
    It's not just cmake, either - ctest reads environment variables too. Set CTEST_OUTPUT_ON_FAILURE=1 and you'll always see output from failing tests.

    This complements CMake presets rather than replacing them: presets define per-project option sets, environment variables carry your personal defaults into every new project you create.

    Full details: kdab.com/%C2%B5-boosting-your-

  9. I don't like that #vscode have switched to a very rapid release cadence. Make the update-button go away, I can't help but clicking it.

  10. I don't like that #vscode have switched to a very rapid release cadence. Make the update-button go away, I can't help but clicking it.

  11. Playing with creating a #VSCode extension (local only) to launch my Hugo shortcut commands. So I don't have to type them in the terminal but use the VSCode Command Palette.

    This is easier than I thought it would be.

  12. Playing with creating a #VSCode extension (local only) to launch my Hugo shortcut commands. So I don't have to type them in the terminal but use the VSCode Command Palette.

    This is easier than I thought it would be.

  13. Is there an easy way to use the new version of VSCode's Laravel extension?

    I see on Github they released 2.0.0 last week but the marketplace is still showing 1.7.0, no idea how to get the vsix out of the source code.

    github.com/laravel/vs-code-ext
    marketplace.visualstudio.com/i

    #Laravel #VSCode #PHP

  14. Is there an easy way to use the new version of VSCode's Laravel extension?

    I see on Github they released 2.0.0 last week but the marketplace is still showing 1.7.0, no idea how to get the vsix out of the source code.

    github.com/laravel/vs-code-ext
    marketplace.visualstudio.com/i

    #Laravel #VSCode #PHP

  15. #vscode extension kaellarkin.hugo-shortcode-syntax seems malicious. Its #cybersecurity badness score is 91/100!

    ```json
    {"id": "kaellarkin.hugo-shortcode-syntax", "score": 91, "platform": "vscode"}
    ```

  16. #vscode extension kaellarkin.hugo-shortcode-syntax seems malicious. Its #cybersecurity badness score is 91/100!

    ```json
    {"id": "kaellarkin.hugo-shortcode-syntax", "score": 91, "platform": "vscode"}
    ```

  17. #vscode extension iotaledger.iota-move seems malicious. Its #cybersecurity badness score is 100/100!

    ```json
    {"id": "iotaledger.iota-move", "score": 100, "platform": "vscode"}
    ```

  18. #vscode extension iotaledger.iota-move seems malicious. Its #cybersecurity badness score is 100/100!

    ```json
    {"id": "iotaledger.iota-move", "score": 100, "platform": "vscode"}
    ```

  19. Today I appreciated #VSCode's ability to show a preview of an .md file, rendered into nice Markdown. #OpenSource

  20. Today I appreciated #VSCode's ability to show a preview of an .md file, rendered into nice Markdown. #OpenSource

  21. #vscode extension nihilus118.perl-debugger seems malicious. Its #cybersecurity badness score is 98/100!

    ```json
    {"id": "nihilus118.perl-debugger", "score": 98, "platform": "vscode"}
    ```

  22. #vscode extension nihilus118.perl-debugger seems malicious. Its #cybersecurity badness score is 98/100!

    ```json
    {"id": "nihilus118.perl-debugger", "score": 98, "platform": "vscode"}
    ```

  23. #vscode extension jt.jakt seems malicious. Its #cybersecurity badness score is 99/100!

    ```json
    {"id": "jt.jakt", "score": 99, "platform": "vscode"}
    ```

  24. #vscode extension jt.jakt seems malicious. Its #cybersecurity badness score is 99/100!

    ```json
    {"id": "jt.jakt", "score": 99, "platform": "vscode"}
    ```

  25. #vscode extension Flutterando.flutter-mobx seems malicious. Its #cybersecurity badness score is 91/100!

    ```json
    {"id": "Flutterando.flutter-mobx", "score": 91, "platform": "vscode"}
    ```

  26. #vscode extension Flutterando.flutter-mobx seems malicious. Its #cybersecurity badness score is 91/100!

    ```json
    {"id": "Flutterando.flutter-mobx", "score": 91, "platform": "vscode"}
    ```

  27. #vscode extension casualjim.gotemplate seems malicious. Its #cybersecurity badness score is 93/100!

    ```json
    {"id": "casualjim.gotemplate", "score": 93, "platform": "vscode"}
    ```

  28. #vscode extension casualjim.gotemplate seems malicious. Its #cybersecurity badness score is 93/100!

    ```json
    {"id": "casualjim.gotemplate", "score": 93, "platform": "vscode"}
    ```

  29. #vscode extension AndenetAlexander.vim-cheatsheet seems malicious. Its #cybersecurity badness score is 96/100!

    ```json
    {"id": "AndenetAlexander.vim-cheatsheet", "score": 96, "platform": "vscode"}
    ```

  30. #vscode extension AndenetAlexander.vim-cheatsheet seems malicious. Its #cybersecurity badness score is 96/100!

    ```json
    {"id": "AndenetAlexander.vim-cheatsheet", "score": 96, "platform": "vscode"}
    ```

  31. #vscode extension maptz.regionfolder seems malicious. Its #cybersecurity badness score is 100/100!

    ```json
    {"id": "maptz.regionfolder", "score": 100, "platform": "vscode"}
    ```

  32. #vscode extension maptz.regionfolder seems malicious. Its #cybersecurity badness score is 100/100!

    ```json
    {"id": "maptz.regionfolder", "score": 100, "platform": "vscode"}
    ```

  33. #vscode extension helper-beeps.solidity-pro seems malicious. Its #cybersecurity badness score is 90/100!

    ```json
    {"id": "helper-beeps.solidity-pro", "score": 90, "platform": "vscode"}
    ```

  34. #vscode extension helper-beeps.solidity-pro seems malicious. Its #cybersecurity badness score is 90/100!

    ```json
    {"id": "helper-beeps.solidity-pro", "score": 90, "platform": "vscode"}
    ```

  35. #vscode extension MarinhoBrandao.Angular2Tests seems malicious. Its #cybersecurity badness score is 92/100!

    ```json
    {"id": "MarinhoBrandao.Angular2Tests", "score": 92, "platform": "vscode"}
    ```

  36. #vscode extension MarinhoBrandao.Angular2Tests seems malicious. Its #cybersecurity badness score is 92/100!

    ```json
    {"id": "MarinhoBrandao.Angular2Tests", "score": 92, "platform": "vscode"}
    ```

  37. #vscode extension magne-sjaastad.opm-flow-editor-support seems malicious. Its #cybersecurity badness score is 92/100!

    ```json
    {"id": "magne-sjaastad.opm-flow-editor-support", "score": 92, "platform": "vscode"}
    ```

  38. #vscode extension magne-sjaastad.opm-flow-editor-support seems malicious. Its #cybersecurity badness score is 92/100!

    ```json
    {"id": "magne-sjaastad.opm-flow-editor-support", "score": 92, "platform": "vscode"}
    ```

  39. #vscode extension AlDuncanson.react-hooks-snippets seems malicious. Its #cybersecurity badness score is 93/100!

    ```json
    {"id": "AlDuncanson.react-hooks-snippets", "score": 93, "platform": "vscode"}
    ```

  40. #vscode extension AlDuncanson.react-hooks-snippets seems malicious. Its #cybersecurity badness score is 93/100!

    ```json
    {"id": "AlDuncanson.react-hooks-snippets", "score": 93, "platform": "vscode"}
    ```

  41. #vscode extension AcademiaDosDevs.javafx seems malicious. Its #cybersecurity badness score is 100/100!

    ```json
    {"id": "AcademiaDosDevs.javafx", "score": 100, "platform": "vscode"}
    ```

  42. #vscode extension AcademiaDosDevs.javafx seems malicious. Its #cybersecurity badness score is 100/100!

    ```json
    {"id": "AcademiaDosDevs.javafx", "score": 100, "platform": "vscode"}
    ```

  43. #vscode extension rumbledb.jsoniq-vscode seems malicious. Its #cybersecurity badness score is 94/100!

    ```json
    {"id": "rumbledb.jsoniq-vscode", "score": 94, "platform": "vscode"}
    ```

  44. #vscode extension rumbledb.jsoniq-vscode seems malicious. Its #cybersecurity badness score is 94/100!

    ```json
    {"id": "rumbledb.jsoniq-vscode", "score": 94, "platform": "vscode"}
    ```

  45. #vscode extension amd.gaia-vscode seems malicious. Its #cybersecurity badness score is 94/100!

    ```json
    {"id": "amd.gaia-vscode", "score": 94, "platform": "vscode"}
    ```

  46. #vscode extension amd.gaia-vscode seems malicious. Its #cybersecurity badness score is 94/100!

    ```json
    {"id": "amd.gaia-vscode", "score": 94, "platform": "vscode"}
    ```

  47. #vscode extension slb235.vscode-coffeelint seems malicious. Its #cybersecurity badness score is 100/100!

    ```json
    {"id": "slb235.vscode-coffeelint", "score": 100, "platform": "vscode"}
    ```

  48. #vscode extension slb235.vscode-coffeelint seems malicious. Its #cybersecurity badness score is 100/100!

    ```json
    {"id": "slb235.vscode-coffeelint", "score": 100, "platform": "vscode"}
    ```

  49. #vscode extension mitsuhiko.insta seems malicious. Its #cybersecurity badness score is 97/100!

    ```json
    {"id": "mitsuhiko.insta", "score": 97, "platform": "vscode"}
    ```

  50. #vscode extension mitsuhiko.insta seems malicious. Its #cybersecurity badness score is 97/100!

    ```json
    {"id": "mitsuhiko.insta", "score": 97, "platform": "vscode"}
    ```