Importing Exported Profile does not allow over-writing existing profile

[murugappanrm]

Does this issue occur when all extensions are disabled?: Yes

• VS Code Version:
  Version: 1.81.0 (user setup)
  Commit: 6445d93
  Date: 2023-08-02T12:37:13.485Z
  Electron: 22.3.18
  ElectronBuildId: 22689846
  Chromium: 108.0.5359.215
  Node.js: 16.17.1
  V8: 10.8.168.25-electron.0
  OS: Windows_NT x64 10.0.19045
• OS Version:
  Windows 10
  Steps to Reproduce:

1. Export the default profile from one installation
2. On the other installation, Import profile
3. The other installation only allows to create and not over-write existing profile.

[gjsjohnmurray]

Did you mean to write "does not" in the issue title?

I think it is by design that the Default profile cannot be overwritten. #168867 is an open issue discussing whether this constraint could be relaxed.

[murugappanrm]

@gjsjohnmurray sorry typo error, I have this inbuilt habit of omitting negative words... hehehe. I change the title.

Its odd, i could over write the default profile only yesterday, I guess the new update must have change things. It not a show stopper. The problem is that I have to create a new profile in all my instances (4 of them). I know i could sync using GitHub but i dont really like using GitHub as it has become too overloaded and no longer simple to use. Also too many dependencies. I never use GitHub repos except the GitHub Co-Pilot (fantastic stuff, not good for newbies using a language).

I am not sure with your answer though. Do i assume that it has been cast in stone not to allow overwrite (thought it was override)?

[sandy081]

/duplicate

It is not supported to overwrite the default profile. Above issue is meant for that. Please subscribe to it.

[vscodenpa]

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!