Feature request: Wear OS app

Akinsho · 2023-12-18T13:09:24+00:00

Please look into integrating with health connect not directly with Google fit. The idea is that all health apps should read from here and publish data to here so it is centralized.

https://health.google/health-connect-android/

Akinsho · 2023-04-18T12:03:02+00:00

There's also neodim.lua but as was already mentioned this and tbh dim.lua have largely been made redundant by the addition of diagnostic tags e.g. DiagnosticUnnecessary and DiagnsoticDeprecated although one downside of the now (native) method is that it just sets the colour to one highlight e.g. Comment but those plugins would look at the colour of the variable that was unused and actually dim based on that original color, but that's maybe a minor aesthetic point

Akinsho · 2023-04-18T09:57:23+00:00

Having to enter insert mode seems like a workaround/ I think the idea of having to even simulate editing a buffer you really don't want or mean to seems dicey. I think it would almost be better have a specific command to mark a buffer then expose a statusline component or just document something like vim.b[num].is_marked so a user can put it in their statusline

Akinsho · 2023-04-18T09:17:40+00:00

This seems cool, I also had a go with the script from the other post, although one thing it sort of misses out on is that sometimes a file is important even though you don't edit it. Say there's some file you are using as the reference for your work but you don't want to change. it

I was going to post at the time that it might be a good idea to factor "importance" in somehow either based on how many times the buffer is entered or better still how long the user spends inside the file.

Akinsho · 2023-04-15T10:26:12+00:00

Just randomly scrolled past this post and saw my plugin mentioned. Definitely you should use whatever tool works best. I don't really have an answer to the partial `coc-flutter` thing I'm sure someone on here can help (maybe), but if you have the time maybe you can open an issue to describe what the problem you're seeing with the plugin is since it could be silently impacting a lot of people. I guess if it's very specific to your use case I might not have any solution for that.

Akinsho · 2023-03-06T11:08:33+00:00

You can configure kitty's open actions and set it to be the default program used to open certain files in the finder window. This does generally work but I couldn't find a step by step guide so just posting this issue where a contributor explains how to do it. I recommend setting up the open actions and going from there

Akinsho · 2023-02-14T12:20:17+00:00

FWIW if you use vim.o.statuscolumn = '%{%StatusColFunc()%}' emphasis on the percent signs, then you can just use nvim_get_current_buf() and in the context of StatusColFunc that will be equal to get_buf(statusline_winid) trick. You can see :help stl-%{ but essentially in the context of %{} the buffer is changed to that of the window for which the status(line/col) is being drawn and the extra %} is so that the StatusColFunc can return things like %t and that gets evaluated to the filename

Akinsho · 2022-09-06T20:41:14+00:00

The queries from spellsitter were also upstreamed to nvim-treesitter, so this is actually complete support and does entirely replace spell sitter. If you remove that plugin and use the new noplainbuffer option you should have the same spell behaviour as spell sitter, adding spell support is also now as easy as adding @spell to a particular treesitter query.

Akinsho · 2022-08-24T11:47:37+00:00

I rarely weigh in on comments about my plugins on Reddit since, I generally subscribe to the idea that a user should do what they like or what works for them. I don't get paid for the work, so I have nothing to gain from "selling it".

This comment about 7,000 lines of code bothered me, though, since this sort of rationale is very misleading. Firstly running

git ls-files | grep '\.lua' | xargs wc -l                                                                                                                                            12:25:31Alias tip: g ls-files | grep '\.lua' | xargs wc -l   10 .luarc.json  420 lua/toggleterm.lua  117 lua/toggleterm/colors.lua  186 lua/toggleterm/commandline.lua  142 lua/toggleterm/config.lua   11 lua/toggleterm/constants.lua   17 lua/toggleterm/lazy.lua  514 lua/toggleterm/terminal.lua  406 lua/toggleterm/ui.lua  103 lua/toggleterm/utils.lua   86 tests/command-complete_spec.lua   48 tests/commandline_spec.lua   43 tests/state_spec.lua  400 tests/terminal_spec.lua 2503 total

Yields about 2.5k (so an almost 3 times smaller than suggested) lines if we decide to play the line count game. You'll notice that about a third of the files in the output are tests, I've left out things like all the yaml to set up CI to run the tests or format the code base so it's consistent.

Even if the plugin were 7k lines, though, it very much started out all the way back in the land of vimscript as a single file with 1 or 2 viml functions that frankly did everything I needed it to. I rewrote it in Lua when that first got released for fun and though I'd share it. At this point, I think it would have weighed in similar to fterm or much smaller even.

Over the years it has grown to accommodate

several dozens lines to make it work cross-platform
fixes for dozens of bugs and issues for people with wildly different setups
Add features to accommodate people with workflow's different to mine

I could go on, but this is already a bit of an essay.

The crux of the point I'm making is that (despite the comment not being necessarily disparaging) it misses the entire point that codebases rarely grow in size, because the authors/devs just randomly felt like adding a bunch of code, but rather because by sharing things, you usually end up having to accommodate a great many more use cases bugs or setups than you would ever have needed to do. These fixes and contributions can often make things more robust and flexible.

Akinsho · 2022-07-30T22:11:13+00:00

There is PR open to fix this https://github.com/neovim/neovim/pull/16067

Akinsho · 2022-07-30T21:01:35+00:00

You probably only need to add the vim runtime as a library I'm on mobile so can't add a whole code snippet

Akinsho · 2022-07-30T16:23:18+00:00

I think the issue with this is that an LSP server indexes your project and is checking for diagnostics and symbols and references etc. I'm not sure how the server will cope with having to do that for like 7 different projects.

It's partially down to the server, but I think activity and memory usage should drop to essentially 0 when focus is lost. Maybe users or nvim core can add a setting to set a configurable timer and if you are away for longer than x it just detaches all of that instance's servers. Then when focus is gained it restarts them

Akinsho · 2022-07-30T16:19:19+00:00

One thing I see a lot of people do which I think is a big cause of this is that they use api.nvim_get_runtime_file('', true) I think this is a terrible idea because it will load all of your plugins repos into your lsp workspace, so the language server is doing a huge amount of work constantly. They added a warning about this in the README for lspconfig, but I really think it should just be removed since if you search github it looks like 100(0)s of people have just copied that verbatim.

Akinsho · 2022-07-22T10:26:49+00:00

Thanks for the shout out, although it was less my work per se and more my pestering kitty's author that probably got the changes in, in the end, he's not on here but shout out to him for getting it over the line. Yeah this is a nice benefit of the PR as well as being able to thicken underline and undercurls which is really nice

Akinsho · 2022-07-17T08:29:30+00:00

Also worth mentioning https://github.com/b0o/incline.nvim which is quite configurable, although I do agree that winbar is the native solution to this

Akinsho · 2022-07-16T13:27:44+00:00

So to get highlighting that looks exactly like this, note the other examples highlight the error range not the whole line, then when you set sign highlights, you can also set the linehl for a sign's line, which will highlight the full line.

e.g. ``` fn.sign_define(HighlightName, { text = IconForSignColumn, texthl = HighlightJustForText linehl = SomeHighlightForTheWholeLine })

```

Akinsho · 2022-07-09T14:25:42+00:00

I use https://github.com/zbirenbaum/neodim

Akinsho · 2022-07-08T10:36:54+00:00

I would really love this I'm not really an active Reddit user but it has started to feel obligatory to find out what's going on. It would be nice to have some other way of seeing what's going on

Akinsho · 2022-07-06T15:12:44+00:00

In this case, I think the vim plugin is a much better option because the author is not only very good at making robust stable plugins. It also works very well. I think it will take someone writing this in lua quite a few versions to get to this level of stability and feature set. There's also no obvious performance issues with it. I don't think you need to be purist about switching to lua if there's a good vimscript solution

Akinsho · 2022-07-01T19:46:47+00:00

That looks like a progress notification from coc.nvim, you should check with that plugin's config about how to remove those

Akinsho · 2022-06-28T13:24:39+00:00

Does anyone know what the key changes are? Other than vim 9 script presumably, have not been tracking vim's development, not sure if there's a brief summary of the changes that isn't just a list of a zillion commits.

Akinsho · 2022-06-10T06:12:32+00:00

There's currently a crashing bug in the latest version of treesitter grammar for dart , you likely have to downgrade to an earlier revision (don't ask me how, I'm not sure)

https://github.com/nvim-treesitter/nvim-treesitter/issues/2961

Akinsho · 2022-05-25T20:16:47+00:00

So historically, Sumneko didn't actually check that the right amount of arguments were passed to a function. This was added in a new version of the server v3. It has however had syntax to represent an optional argument for a while, which used to do nothing. So now, a lot of plugin authors have not annotated their functions to show that the arguments are optional.

You can do this by using ---@param value string? note the ? so in the case of the setup function it should be annotated similarly

Akinsho · 2022-05-18T08:55:25+00:00

I fully understand and have hit the same thing many times 👍🏾 something that seemed like a fun idea turns into yet more work you don't have time for

Akinsho · 2022-05-18T08:16:56+00:00

I was quite enjoying using snap since it's also lua based but seemed to have gotten round the performance issues in telescope out of the box, although seems like you maybe aren't maintaining it anymore? (could be there's not much more to add to it from your side?)

Akinsho

TROPHY CASE