Not include spaces after autocompletion of extension methods/LINQ
![](https://secure.gravatar.com/avatar/d41d8cd98f00b204e9800998ecf8427e?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Pete Wilson commented
Code snippets don't really help me with this as I write/add a lot of LINQ extension methods.
-
B Ward commented
Joe (the author) was kind enough to respond to an email I sent on this topic. His response was, "Create a code snippet and LINQPad will pick it up.... If it conflicts with an inbuilt snippet, your snippet will win."
I have been able to do this with snippets that I have explicitly selected from the list, but not for the ones that are triggered with autocomplete (like the space after an extension method).
-
Pat Kujawa commented
Yes, it would be great to customize this particular behavior. It really bugs me to have a space before parentheses when I'm invoking a function. A space after if, using, while, etc makes sense, but please don't put one after a function. (Interestingly, when you open up a C# Program query, the main method is written *without* the annoying space, viz. void Main().)