The example before shows the author typing Prin with autocompletion. Maybe that was the original intent? I think that context is lost though and it would be better to just highlight the entire thing as you suggest.
Re:Chime – A Go Editor for macOS
by alangpierce on Sunday January 05, 2020 @04:49PM
(#21964382)
From the screenshot, it looks like the intention is that "Prin" has been typed by the user and "tf" is a suggestion, so it makes sense that "tf" would be gray and "Prin" would be green. (Of course, that could be made more clear.)
Same thought here. Simply omitting a cursor seems to be the most disorienting part.
Re:Chime – A Go Editor for macOS
by mattiemass on Sunday January 05, 2020 @09:51PM
(#21966029)
I swear it makes sense when you us it! But, the cursor is there. "Prin" before the insertion point, and the autocomplete suggestion of "t(<placeholder>)" comes after.
Re:Chime – A Go Editor for macOS
by alangpierce on Sunday January 05, 2020 @11:11PM
(#21966375)
Makes sense! The image we're referring to is the one for the "Built for macOS" section, not the full screenshot at the top of the page. That one doesn't have a cursor in it.
Re:Chime – A Go Editor for macOS
by mattiemass on Monday January 06, 2020 @05:56AM
(#21968176)
Oh man I'm an idiot. Yes. You've all figured it out. Cursor there would indeed make sense. Will fix!
Admittedly, I’d rather a development team spend more time and attention on their app than their landing page, but they should probably fix that since it kinda sticks out. Hopefully they’ll see these comments.