Re: Deterministic paths option causing custom command pattern "!&" expand to all files
Thanks for your report.
So would an acceptable solution be that the "Keep temporary copies of remote files in deterministic paths" would not apply for custom commands? It might even be a good idea, as even a read-only custom command (like text search/grep-kind of command) might inadvertently overwrite a file you are just editing.
So would an acceptable solution be that the "Keep temporary copies of remote files in deterministic paths" would not apply for custom commands? It might even be a good idea, as even a read-only custom command (like text search/grep-kind of command) might inadvertently overwrite a file you are just editing.