Hiren Hiranandani
Hiren Hiranandani
I think that's a great idea. I have thought about this a lot myself. I feel implementing this would mean expanding to the next "ring of functionality". That is going...
That didn't work.
Thanks for the feedback. This is a complex issue because I often use git fuzzy like this: ```bash $ vim $(git fuzzy status) ``` This means that if you're somewhere...
eagerly awaiting this with ❤️
I'm hesitant to support this since: 1. `{}` means something in bash and I'm not entirely sure it'll always work as desired ``` $ echo {1..2} 1 2 ``` 2....
After thinking about this, I'm open to implementing this. It's definitely true that `{1..2}` can easily just be quoted to avoid bash's expansion. It's also sort-of safe to have it...
I agree. I don't have the time to fix this right now. Feel free to make a PR.
If you can create a PR for #3 that addresses the issues I mentioned, then I think this can be added.
@louim how should we be providing configurations to the rails lsp app?
Is anyone actively working on this? I can take the Ruby LSP configuration propagation and the Rails LSP design for the configuration. @vinistock are you able to create an issue...