3 ms·
Cool. Some feedback from a few minutes of use: - When I started typing a string, Chime added a double quote for me to terminate the string. Fine, but if I use
by shric 7y ago
Cool. Some feedback from a few minutes of use:
- When I started typing a string, Chime added a double quote for me to terminate the string. Fine, but if I use my years of muscle memory to terminate the string myself, it should replace the inserted quote instead of letting me double them up: fmt.Printf("Hello"") this does work correctly if you used autocomplete to generate a " format " hint from fmt.Printf.
- After typing fmt.Pr<escape> it showed me a number of options including fmt.Printf. When I selected that option, it presented me with fmt.Printf( format , a ) which I could fill in, fine. But I had to deliberately move the cursor into the " a " part to replace the " a " with my argument. If I didn't and just moved right after the comma, it would do e.g.: fmt.Printf("%d", 42a) Also, the fmt.Printf would be highlighted green instead of light blue like the others. Furthermore, if I then tried to do fmt.Pr<escape> on the next line, it wouldn't offer anything semantically related, just the local variables like x and y.
- mattiemass 7y agoThanks so much for trying. These two issues are both fairly related, and an area of active work. That string termination thing in particular is killing me as well. Going to be addressed in the next release or so, but thank you for reporting. The experiences around autocomplete interactions are noted and, with the exception of the very last bit, understood. Very much appreciate you reporting what happened.