BUG: completion selectors broken at line end (blocker for extension)

Hey @logan, thanks for the candid answer. I must admit it took me a while to come to terms with it. I understand that, what with Panic’s obvious disinclination to give their editor the resources it needs (and I am not comparing Nova to VSCode – I think Sublime is closer to the mark. But that is a discussion to be had with your bosses, not you.), you need to prioritise in a way that makes addressing gnarly bugs in core functionality an unattractive prospect. Still, I would be lying if I said that that wasn’t a frustrating answer when talking about a paid product.

I have taken your advice to “take a break from Nova” to heart and had a long, hard look at the competition out there, and I am afraid moving on is not working for me. VSCode is a monstrosity, and anything that uses TM 2 syntax grammars is out anyway, as there is not way to create a decent fish syntax in it; which also disqualifies things like Code Runner (actually not quite the toy anymore it started as). The newly LSP-enabled BBEdit … uh, I think I started using Macs too late to accept that kind of UI, and anyway, the syntax format doesn’t seem amenable to good fish support either. Which leaves Sublime, which has a meh fish syntax plugin for version 3 (it failed every single one of the syntax tests I wrote for the Nova extension) that could probably become quite good leveraging the new features in version 4, but what I see there is massive teething trouble, plus I’d end up with a thing you can theme just about enough to bring it into the uncanny valley of macOS UIs, which, honestly, yikes.

Long story short, considering the cost (not literal; I’m talking work hours and mindshare) I already sunk into Nova, you’re stuck with me and I will keep going on your nerves about this issue. This means two things:

  1. I will be releasing my fish extension with the piecemeal, overeager-where-it-works completion support I could cobble together with the currently broken selector API. That in turn means clearly and publicly labelling all support issues around completion out of scope because they are due to a Nova bug, but hey … ¯_(ツ)_/¯.
  2. I will be creating a new Discourse thread about this issue, partly as a FYI for other devs and reference for users of my extension, but mainly because I think I have, by now, pinpointed the misbehaviour in question far more precisely than I did in the original post. I’ll close this one as resolved to declutter things.