Wojciech Muła

> So, the current behavior is that `avo` will output the build constraint syntax consistent with the Go version `avo` was compiled with. I'm assuming this is going to be...

> I know it's not ideal, but how annoying is it to use Go 1.17 for your code generation? TBH, this would not be convenient. But I realized I can...

@mmcloughlin That would be perfect. However, I'm thinking now if it's really needed. So far I'm the only person who asked about that, and there's a workaround. Additionally, Go 1.16...

Thank you for the report. Do you have aspell-dev installed? If you have, what's the full path to aspell.h?

Good that you fixed the problem. However, it would be great if setup checked (somehow) for aspell.h presence.

@sjagadee It works, but you had to manually modify the file. I'm looking for a better solution. :)

@mbarkhau that's a long-standing issue... any help to make it possible is warmly welcomed :)

@mbarkhau Thanks for checking!

AFAIR it's not possible, here is the list of options that somehow affects on suggestions: > sug-repl-table ('boolean', True, 'use replacement tables, override sug-mode default') partially-expand ('boolean', False, 'partially expand...

No, seems to be noop.