™
™
> Running `ln -sf /usr/local/Cellar/[email protected]/1.1.1o/lib/libcrypto.dylib /usr/local/lib/` solved the issue for me. Thanks. if i install sublime text 4126 using official sublimetext, will i face this issues? or while installing brew...
but in the contents of the app directory, there are `libcrypto.1.1.dylib` as well as `libssl.1.1.dylib` , so is the issue with symlink?
or can it be done in this way, that sublime will only use the backdated library instead of making it the default one.
> The best would be to fork the extension and remove the telemetry from it. > > But the license is weird. It's a MIT but at the begin you...
Also, can u confirm if the telemetry of the extension still work under vscodium?
> In general, VSCodium do not remove/disable any telemetry found in an extension from the marketplace. So yes, the telemetry still works for `vscode-cpptools` and use the lib `@vscode/extension-telemetry`. A...
is this problem with apple silicon mac?
> Well, I don't have enough information to conclude that the issue has to do with my machine being an `M1` because I haven't ran `flameshot` on an Intel based...
> Yes using Rosetta vs running natively makes a lot of differences, u should know.
> I do know that @DeveloperKev. Because not all apps have been natively compiled for `M1`, every release of MacOS comes with `rosetta2` since Big Sur. And that is also...