Andy Freeland comments

Results 81 comments of


                                            Andy Freeland

Text output render issue

I’m running 0.7.2

Text output render issue

Hmm, I see the same cutting off behavior on the latest nightly nvim: ``` NVIM v0.8.0-dev-762-g0a049c322 Build type: RelWithDebInfo LuaJIT 2.1.0-beta3 ```

Text output render issue

Hmm, I'm still seeing the same cutting off behavior on a3229e979980c8b78e12ab9741e8c41390643b37. ``` NVIM v0.7.2 Build type: Release LuaJIT 2.1.0-beta3 Compiled by [email protected] ```

Text output render issue

On 2a887fe9b2ae604dac9715261355b75b67323dc0, I run the test, call `neotest.output.open`, and it's still cut off. 😞 Tested on 0.7.2 and v0.8.0-dev-1020-gea10e0c10...

Python `match` statement not supported

It looks like this could be solved by updating https://github.com/returntocorp/semgrep-python to the latest [tree-sitter-python](https://github.com/tree-sitter/tree-sitter-python)

How to disable output clipping in docker build?

It looks like passing the env variable through the config works now

`Field.number(kind=...)` supports any function that returns a number

Hmm, I didn't notice mypy isn't happy with this. We might need our own protocol with `__float__` and the comparison operators. @glyph does that sound reasonable?

`Field.number(kind=...)` supports any function that returns a number

> > Hmm, I didn't notice mypy isn't happy with this. We might need our own protocol with `__float__` and the comparison operators. @glyph does that sound reasonable? > >...

`Field.number(kind=...)` supports any function that returns a number

@glyph updated with a `_Numeric` protocol! I tried setting it as a bound on a `TypeVar` and using that for `minimum`, `maximum`, and `kind`, but mypy complains and I couldn't...

`Field.number(kind=...)` supports any function that returns a number

Ohhh, thanks for the fix! I'll add the coverage ignore tomorrow during the workday.