Kevin Hwang

Results 187 comments of Kevin Hwang

![image](https://user-images.githubusercontent.com/17562139/181908193-751d3455-a4a9-42c5-82af-050fab5b08b3.png) It's too hard. 1. `19-22` and `23-43` are level1, 22 line is the lower but 23 line is the upper, it can't balance aesthetics and practicality; 2. A line...

> @kevinhwang91 I don't fully understand some of the issue you are seeing, but the result of the screenshot so far looks great. I'm guessing that the highlights are in...

maybe only use `▔` to indicator the `startLnum` and highlight current range is a compromise method. The upper/lower icon is hard to select and `⁀‿` in some fonts are asymmetric....

I get sucked with the UI. There're many potential errors that need to handle. BTW, `ctrl-w+o` will work fine with the floating window foldcolumn. https://user-images.githubusercontent.com/17562139/181925985-66dbf19e-bd79-4659-9c3f-c66b1cbe0796.mp4

`UFO_LOG=info nvim` and provide the log. BTW, what's the formater you use?

reproduced. I will fix it later.

After debugging, this is `nvim_buf_set_text` issue called from `lua vim.lsp.buf.format()`, you can disable ufo and then open the text you provided, and then: 1. `2,4fold` 2. `5delete` 3. `lua vim.lsp.buf.format()`...

https://github.com/neovim/neovim/issues/19571

`saving and restoring the view`: is this issue existing for now? `before and after the formatting`: There're two format ways, one is full edit, and another is local range edit....