stef-levesque

This is related to the [quick diff editor gutter decorations](https://code.visualstudio.com/docs/extensionAPI/api-scm#_quick-diff), computed by VS Code itself. @joaomoreno any idea why the editor would used a cached version of the 'Original' resource?

Nice catch, thanks !

Can you provide the Windows path, the depot path, and the `Perforce: Output` of a filename causing problem ?

Unfortunately, I couldn't repro your issue on Windows 10, nor macOS (which is case-sensitive anyway). In the extension code, the only explicitly lowercase impacting the p4 command is done on...

Thanks, that now makes much more sense. Yes, using [true-case-path](https://www.npmjs.com/package/true-case-path) seems like a proper fix for this. I'll include it in the next release.

Now supported. Please update to version 2.0.0

Sorry, I misunderstood your request. The extension currently follow the same behavior as P4V, which mean all newly added/edited files go to the `default` changelist, where you can then moved...

have you tried to add a `.p4config` or `.p4settings` file at the root of each workspaces ?

I pushed a new version of the extension (2.2.2) Let me know if it resolve your issue.

Can you try to change your vscode user settings, clear any previous `perforce` parameter and only keep ```javascript "perforce.activationMode": "always" ``` Then reload your vscode workspace. This should let `p4`...