Make path separator escape configurable (#373)

[dbazile]

This adds an opt-out for the forced path separator escaping added for #373. This fixes an issue where paths are always escaped, making this feature unusable without constant backtracking to remove escapes (see sublimelsp/LSP-pylsp#180).

I don't know how valid the default listed in CONFIGURATION.md is (the default value is whether or not snippets are supported, which always seems to be true) but I can't figure out how better to phrase it.

Demo

demo-fix.webm

References

• file path auto completion add \ in path string #373
• File path completions unnecessarily escape trailing slashes for directories sublimelsp/LSP-pylsp#180

[ccordoba12]

Hey @dbazile, I don't think this is the correct approach. If your client supports code snippets, the escapes added to paths by this server need to be handled by it, not by an additional option here.

That's what we do in Spyder, at least:

[dbazile]

Funny thing about that. The client project (LSP-pylsp) said it’s a server issue. I literally got bounced here from two closed GH issues I raised over there. :)

…

On Fri, Feb 7, 2025, at 17:23, Carlos Cordoba wrote: Hey @dbazile <https://github.com/dbazile>, I don't think this is the correct approach. If your client supports code snippets, the escapes added to paths by this server need to be handled by it, not by an additional option here. That's what we do in Spyder, at least: dir-completions.gif (view on web) <https://github.com/user-attachments/assets/b9336f94-5f3c-4b0e-a4db-bad4d5868eb2> — Reply to this email directly, view it on GitHub <#611 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AALYTA24NRTG2BODIULIIHT2OU56DAVCNFSM6AAAAABVBMEUWOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNBUGMYTAOBZGI>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ccordoba12]

Ok, then why don't you disable code snippets? That would avoid the path separator escaping.