Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
nerdculture.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
Be excellent to each other, live humanism, no nazis, no hate speech. Not only for nerds, but the domain is somewhat cool. ;) No bots in general. Languages: DE, EN, FR, NL, ES, IT

Administered by:

Server stats:

1.2K
active users

nerdculture.de: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#vscode

25 posts18 participants0 posts today
Public
Matt "msw" Wilson

The latest proprietary #VSCode extension that no longer works in non-Microsoft builds of the MIT licensed VS Code source code appears to be C and C++ support.

Your regular reminder: every day more of VSCode functionality is proprietary, and increasingly #FOSS hostile.

#FreeeSoftware #OpenSource #OSS

github.com/VSCodium/vscodium/i

As of the latest update of Microsoft's C/C++ extension (v1.24.5, released April 3, 2025), use on non-Microsoft products appears to have been blocked. Upon initializing the extension, I get the foll...
GitHubMicrosoft C/C++ Extension appears to no longer support unofficial forks of VS Code · Issue #2300 · VSCodium/vscodiumBy ImagineBaggins
Public
Benjamin Carr, Ph.D. 👨🏻‍💻🧬

#VSCode extensions 'Material Theme – Free' and 'Material Theme Icons – Free' with 9 million installs pulled over #security risks
Researchers told BleepingComputer that their specialized scanner detected malicious activity in the extension's code. One of the researchers, Amit Assaraf, says they believe the malicious code was introduced in an update to the extensions, indicating either a supply chain attack through a dependency or the developer's account was compromised.
bleepingcomputer.com/news/secu

BleepingComputer · VSCode extensions with 9 million installs pulled over security risksBy Bill Toulas
Public
jessehouwing :verified:

Playing around with MCP in #vscode and one of the things that struck me is the usage of .env files to store tokens. The guidance from #enthropic is to at least make this "secure" by adding the .env file to your .gitignore file, but I'd rather not do that either.

Way too easy for any process to capture that file and exfiltrate it.

So I set out to update the @github MCP Server with support for the GitHub CLI. Now when I chat to github using Visual Studio Code,

I can simply rely on the token stored in the Windows Credential Store for added safety.

Did a pull request, lets see if this will land.

Don't think this will easily be supported by the docker version of the MCP servers, since it won't have access to the Windows Credential Store.

Then again, running docker in visual studio code on windows on wsl is still not the best experience int he world.

If you'd like to try this yourself, clone this PR, build the GitHub MCP server locally and update your vscode insiders settings to the following:

```
"mcp": {
"github": {
"command": "node",
"args": ["node", "E:\\mcp-servers\\src\\github\\dist\\index.js" ],
"env": { "GITHUB_PERSONAL_ACCESS_TOKEN_USE_GHCLI": "true" } } } }
```

github.com/modelcontextprotoco

Description If instructed using the GITHUB_PERSONAL_ACCESS_TOKEN_USE_GHCLI environment variable, the github token will be read by calling gh auth token. This simplifies usage of the MCP server insi...
GitHubAllows reading github token from the github cli by jessehouwing · Pull Request #1239 · modelcontextprotocol/serversBy jessehouwing
Replied in thread
Public
Rainer

@thomas Nutze gerade mal die Wartezeit beim Frittenfön und zu faul auf englisch zu schreiben.

Mein Blog ist mit #hugo gemacht, was ja auch #markdown habe möchte.
Ich nutze da seit längerem schon Visual Studio Code #vscode. Das hat einen Preview und kann gleich noch #git. Ob es für z. B. Mairmaid-Markdown nativ unterstützt oder ich nen Plugin installiert habe, weiß ich gerade nicht auswendig. Für toml kann ich ein Plugin empfehlen. (1/3)

Public *
Daigoro Toyama 🌸

I spent a few hours dealing with the problem of #VSCode giving me a "syntax error" message when I manually entered a struct member variable in the Watch window (i.e. "ctx->id"). As it turned out, it was an issue with the #CodeLLDB extension. I switched to Microsoft's C/C++ extension ("cppdbg") and set "MIMode" to "lldb" so it used lldb instead of gdb. That fixed it. Note: this is on #macOS.

ExploreLive feeds
About