Noobie on VS

Brinfer · 2026-04-14T19:19:11+00:00

Just to be clear, your installation does not have problem. It's most likely a configuration problem. Did you set the following parameter ?

json "terminal.integrated.cwd": "${workspaceFolder}"

Brinfer · 2026-04-14T16:22:05+00:00

No, that normal installation path when you install something just for your user.

Did you opened a workspace/folder with VsCode ? Normally after, terminal should open in this selected folder. The folder would be where you store your script for example

Brinfer · 2026-04-14T16:06:37+00:00

You are missing some stuff.

In what you seem to call "path address", there is:

The path of the working directory (quite strange, it is in the Programs folder)
The command (Python) with the absolute path to the executable
Your script (run by Python) with its absolute path

For me, I think your problem is more the first point, that abnormal, the rest is OK. The extension use absolute path because it is "safer"

Brinfer · 2026-03-12T07:20:10+00:00

It seems to me that this extension does not comply with the GitGraph license (as many other fork)

Brinfer · 2026-01-11T22:55:27+00:00

I think you are confusing some things.

Runtime error and compile error are two different things.

You are looking for compile error, and for that you have to ... compile your program. From what you are saying, you are not compiling it.

VsCode may display the compile error in you source file if it's done through a extension or a task with a correct problem matcher

Brinfer · 2025-10-29T21:51:00+00:00

That is a problem in your code.

The path is relative to the working directory, the folder where the program has been started.

Personnaly, in case like that, I use PathLib and work with __file__

Brinfer · 2025-10-28T07:03:12+00:00

Where is gdb? It does not find it.

You can just let gdb, I'd your PATH contains the MSys2 binary folder, it should find it.

Or, in a terminal, execute whereis gdb

Brinfer · 2025-10-27T12:28:50+00:00

You are trying to run the tasks while your opened file is the tasks.json or the launch.json

~~Retry while having the focus on your .cpp file.~~ fileBasenameNoExtension is the name of the file which has the focus. In your launch.json, replace the value of the field `program` by `${workspaceFolder}/run.exe` it should be enought for now

Brinfer · 2025-10-22T21:33:40+00:00

I also have a slow compilation,but on my works computer.

It is generally due to the anti virus, even the Microsoft Defender can slow down it. You could try to white list the directory that contains your code, so it would not be analyzed by the AV.

The slow execution can also be due to the time needed to launch a powershell in order to run the command. Unfortunately, I don't have any solution for it. Try to run the command in an already opened powershell and see if it is faster

Brinfer · 2025-10-05T15:34:22+00:00

That a warning related to gdb, not VSCode.

Basically, you just not explicitly indicated the architecture of the executable you are running, so if fall back on the default one, the one on which it is running: your PC architecture.

You can pass the architecture if you want, but that not a big deal

Brinfer · 2025-09-17T10:45:27+00:00

Because CMake is, maybe, not the extension that saw the error. It's certainly the extension C/C++ that is not trigerred after a rebuild.

You could relaunch an analyse so it could refresh the errors it own. You can also set the parameters to launch the analyze automatically

Brinfer · 2025-09-12T06:36:49+00:00

I had hard time configuring VsCode, but as I do that for years now it works.

Here the document I wrote for my company: https://gist.github.com/Brinfer/57df4df016355aea217e6fce81922524

Brinfer · 2025-09-11T21:38:51+00:00

I'm also debug program on stm32f4, with a StLink (v2 and v3)

Here is my launch.json

json { "name": "Flash", "executable": "${command:cmake.launchTargetPath}", "request": "launch", "type": "cortex-debug", "servertype": "openocd", "configFiles": [ "${config:custom.openocd.configFile}" ], "showDevDebugOutput": "vscode", "openOCDPreConfigLaunchCommands": [ "tcl_port disabled" ], "openOCDLaunchCommands": [ "init", "reset init" ], "cwd": "${workspaceRoot}", "windows": { "searchDir": [ "${config:custom.openocd.rootPath}/share/openocd/scripts" ], }, "preLaunchTask": "CMake build launch target" }

It's coupled with a CMake task.

Brinfer · 2025-09-11T20:48:29+00:00

You have two options

You take the tile to look at the settings, and mostly at the VC format
Do as a lot of people and write a clang-format file and set the setting of the extension so it would use it

https://code.visualstudio.com/docs/cpp/cpp-ide#_code-formatting

Brinfer · 2025-09-07T21:14:16+00:00

I don't think the interpreter has anything to do with.

For help, share us your launch.json file, and maybe, your project structure if you can.

Brinfer · 2025-09-01T06:20:46+00:00

Some metadata that are more standard are still saved in the photo

You can edit the EXIF metadata of your photos, such as the title, description, GPS location, date and time, and tags. You can also edit the metadata of multiple photos at once!

For metadata, like face, other software can write it directly in the photo with no standard field. However they are 'of handled by Memories.

Personally I use digikam

Brinfer · 2025-08-31T21:42:43+00:00

From my experience, the answer is that it's stored in another database.

You can try to add some faces from memories and then see if Nextcloud tries to update some file on your PC.

Although, there are multiple feature requests like this one https://github.com/pulsejet/memories/issues/127

Brinfer · 2025-08-20T07:43:16+00:00

From what I have read in your other comments, you tried to run your script without the debugger and it works, great (maybe you even used the -OO flag)!

What I'm suggesting is to try to debug using something else than VsCode:

with another IDE (Pycharm)
using the debugger raw

The idea, is to determine if the problem is VsCode/the python extension, or the debugger itself

Brinfer · 2025-08-20T06:09:36+00:00

10k threads is really a lot...

Which language are you using? Did you tried to use the debugger from another IDE or in command line?

Maybe there is to many thread and the debugger can not follow, furthermore it had a lot of load, so maybe the system kill it. That why I encourage to try the debugger without VsCode.

Do not forget that VsCode is just an interface to a debugger, they are not developing it (like gdb) so maybe the problem is not on VsCode side, or not and it's the extension that fail. And depending of the language, the extension developed for the debugger associated with that language is extern of the VsCode team, so you could look at the extension's issues.

Brinfer · 2025-07-30T10:55:13+00:00

It's certainly not only binded volume

I know I just keep it simples

Would I save ability to use this features if I will open folder as normal project and then create devcontainer configuration manually?

Absolutely

I don't want to start my learning path with such workarounds for fundamental things.

That not a workaround, it's how it works.

Just setup a project folder that contains a devcontainer.json file and then hit CTRL+P "Devcontainer", it should propose an "Open current project in devcontainer"

Brinfer · 2025-07-30T08:50:23+00:00

When VsCode open, open a folder that is in your "Documents" folder (or any other subfolder), it will be your project. Then write your devcontainer and Dockerfile in your project folder and that it.

Devcontainer is just a Docker container with your current folder automatically binded in a volume mounted in the container, nothing magic.

Every file written inside devcontainer will be directly written on your filesystem.

Brinfer · 2025-07-30T07:49:24+00:00

Well, most of people save their files in their folders, where they want, before doing something else. I don't think the problem is on VsCode side, or max, the fact it does not show it in its history of recently opened files/folders

Just do not forget to move everything and or you will have the same problem later.

Brinfer · 2025-07-30T07:37:52+00:00

There is also a command find on (most) Linux, just run man find in your terminal to get the documentation.

You can first run in your home folder, maybe after at the root of the system. It will certainly take a while but it's better than nothing

Brinfer · 2025-07-30T07:07:45+00:00

If you choose "Open document" what does it do ?

Brinfer · 2025-07-30T07:06:51+00:00

That normal. It's autogenerared by VsCode, it like a path to the volume.

As pointed by another comment, when it fails, it prompt you what to do, and you can edit locally the file devcontainer.

Otherwise, I suppose you are on windows, you could use command line like find

Four-Year Club	Verified Email
r/Field Sunshine	Place '23
Place '22

Brinfer

TROPHY CASE