Price Hiller

> > > Seems like #190 is related? > > > > > > Yeah, now playing around with it with the sample you screen shotted, I think #190 is...

> Here are the essentials for a bug report with repro (shamelessly taken from [lazy.nvim](https://github.com/folke/lazy.nvim/issues)). I actually like the issue template that Lazy uses, wouldn't mind nabbing it. The only...

I agree with all three points you raised above. So here's the deal, instead of clutching my pearls on "what ifs", if you send a PR using a `lazy.nvim` repro...

This *should* be doable depending on the language and the associated treesitter parser. I'll look into this when I get some time and other issues I've prioritized are knocked out.

@roycrippen4 if you open a PR to me, I'll gladly merge it (preferably with tests, but it's ok if none are written 🙂 ). Should be gated beind the `enable_close_on_slash`...

After some investigation of this previously, this is a non-trivial addition to `nvim-ts-autotag` to my knowledge. I'll pin this so it doesn't get auto-closed as this is very much an...

Pinned label that is 😅

Will jump on this in the next few days when I have a moment or two. I'll likely be using [Hickory's Resolver](https://docs.rs/hickory-resolver/latest/hickory_resolver/config/struct.ResolverOpts.html) based on a [recommendation from jszwedko in the...

Thanks for the PR! This means the user can't pass a custom config to `setup` AFAIK -- probably not the right way to shim out `nvim-treesitter`. I'm game to retire...

Totally missed your response! > Would it be better to remove from `plugin/nvim-autotag.lua` to `after/plugin/nvim-autotag.lua`? This should make sure users' `setup` is loaded before our `setup`. Sure, you can do...