stef-levesque

I tried to expose the bottleneck parameters the best I could in 7c5339f7f40c7c0154d82018789853c3935e9489 I also updated the pre-release build available here: https://github.com/stef-levesque/vscode-perforce/releases You can download and install the `.vsix` file...

Sorry, I haven't been a good maintainer as of lately. I should push a new version by the end of the week.

`bottleneck` can be configured in by tweaking the values in `perforce.bottleneck`. The extension version 3.2.0 should be available soon.

@CelticMinstrel you are right, this feature is not meant for the lambda user. I exposed the Bottleneck parameters for power users, to help debug and propose solutions for their particular...

https://github.com/SGrondin/bottleneck/blob/master/README.md See the Construction and Strategies sections. It would also help to know which version is the P4 server, how many files you typically have in your change lists, how...

related to Microsoft/vscode#14582

This is addressed in the sections https://github.com/stef-levesque/vscode-perforce#activation and https://github.com/stef-levesque/vscode-perforce#source-control-in-vs-code . Feel free to add or request more info in the README.md

Can you try to enable the `realPath` experimental setting ? Add this in your user or workspace settings ``` "perforce.realpath": true, ```

I've been testing with the 64bit version for along time now, this is unlikely to come from there. Double-check your settings in the `.p4config` file. Otherwise, try to set your...

You can try to activate the experimental `perforce.realpath` in your settings. You can also try to set `perforce.dir` in your workspace settings, and set it to `/u/omeijer/project`