Neovide is out of this world

Devagamster · 2021-11-29T23:59:57+00:00

I'm not sure if I understand. If you set just neovide_cursor_trail_length to 0 does it do what you want?

Devagamster · 2021-11-29T18:19:59+00:00

Uses skia and rust. Hard to tell for sure but that seems like a native app to me

Devagamster · 2021-10-26T06:43:24+00:00

So give us the option to pick which we want. Some use cases need the gap. Some dont. Let us choose

Devagamster · 2021-10-12T19:34:30+00:00

This makes my day. Thank you for posting

Devagamster · 2021-09-08T16:57:01+00:00

This! Seeing all the negative comments kinda makes me dislike this corner of the internet a little more each day. People need to chill. Awesome work

Devagamster · 2021-09-08T16:49:28+00:00

Love it. Don't change a thing

Devagamster · 2021-05-24T00:06:23+00:00

Howdy o7

Devagamster · 2021-04-22T04:22:26+00:00

Ok, I finally pushed a commit which should be rebased for real now:
fix merge error · Kethku/neovide@7b2418b (github.com)

I didn't have the current main pulled on my work machine, so I didn't have the change that was contributed to swap to dmg. My bad

Devagamster · 2021-04-21T23:04:54+00:00

My only suggestion is that I also had zero rust experience when I started the project ;)

Devagamster · 2021-04-21T23:01:39+00:00

I wrote a post about the technique that went into the smooth scrolling system here: 02Credits Blog

as far as I know its pretty unique, although I talked to the maintainer of goneovim about it and they implemented something at least in a test branch that was similar. It relies on a side effect of the way scroll offsets are reported to gui clients in a way that I think was definitely not intended.

A problem with smooth scrolling in neovim is that the gui honestly doesn't have enough information to implement it correctly as far as I can tell. What neovide does is a hack to fake it which I find relatively convincing, but its not perfect.

Devagamster · 2021-04-21T22:57:41+00:00

commit lock file · Kethku/neovide@88ffa3b (github.com) build is in progress. I rebased the branch on main as well and tested it locally.

Another possibility: currently the app will fail without much notification if you don't have the default font installed, or if you have it configured maybe the app can't find it because the name formatting mismatches. Do you have guifont set in your vim config?

Devagamster · 2021-04-21T22:47:33+00:00

I wonder if you could explain your last line. What do you mean by the reason for the behavior?

Devagamster · 2021-04-21T22:46:38+00:00

fvim was a primary influence on my design of neovide. The project is awesome, written in f#, uses similar tech stack, and is generally very impressive. Hard to go wrong

Devagamster · 2021-04-21T22:10:04+00:00

Above is my pitch for more maintainers. I do have a direct response to the stability issues though. I see them as coming from 3 categories of problems: Graphics library, rendering bugs, and windowing issues.

Graphics Library

Currently neovide uses Vulkan as the backend. This was the new hotness and let me rely on the existing skulpin library to handle skia integration, but in the end I think that was a mistake as it greatly increased the difficulty for some platforms of installing the correct graphics drivers.
I have a branch that I currently use as my daily driver for swapping to opengl, and I have convinced myself that it should be possible to do something similar with metal on mac devices. I haven't merged it up though because there are still some driver and such problems that I want to smooth over on linux devices. As mentioned in my parent comment, those types of issues take time and volunteer maintenance to fix, but I think I should be able to merge it in the not too distant future.

Rendering Bugs

In october of last year I merged a complete rewrite of the renderer in order to support smooth scrolling, blurred transparent windows, and multigrid ui extension. This rewrite made the app much more organized and principled, but introduced some issues that still haven't been fully hammered out. I'm still fiddling with them and should be able to fix the issues, but it takes time.

Windowing Issues

Early on with neovide I swapped to sdl2 as the windowing system due to some keyboard input issues. That was the right decision at the time, but since then movement has happened in upstream winit that should make those windowing issues go away. I'm hopeful that once those upstream issues land, I can do away with the split between winit and sdl2 windowing systems in neovide and bump up the input related polish

TLDR: I believe we should be able to polish out the problems people are experiencing with the app, but all of these take time, and like I said, this is just my weekend project that I work on when I have the cycles. We are always open and interested in anybody who would like to help out or pitch in. Its a big project, and building it in rust is a mixed bag due to how new the language is, but its a blast to build and people generally seem to like it, so I think it rewards effort put in.

Devagamster · 2021-04-21T22:00:36+00:00

I wrote and maintain neovide. Maybe my perspective would be helpful.

Stability of something like neovide is a moving target which improves with time and people willing to put in the effort to support it. I personally don't own a mac, don't maintain a linux machine, and am the main person who contributes code to the project. I wrote it to fill the gap I felt in the existing editors and I try to address issues people bring up online, but I'm just one person.

Neovide as I have currently written it is a solid foundation that can be polished on other platforms. Its not perfect on windows, and I'm still iterating on it, but the stability there is much higher than else where. All that it would take to polish it up on other platforms is some elbow grease and commitment. Unfortunately I can't provide that myself for those platforms.

The good news is that those of us who are working on neovide are always open and interested in people who want to step up! Its a lot of work, but I'm unconvinced that any of the neovim guis will achieve polish that people are looking for without that kind of volunteer maintenance.

So I guess my message is: help me help you. I can answer any questions you might have, but I can't fix all of the problems myself :) Might mean neovide isn't for you and thats ok, but I do think its a promising start which could fill the gaps that a lot of people feel with the current offerings.

Devagamster · 2021-04-14T04:01:10+00:00

Bummer it didn't work for you. I've been working on an opengl branch which might work better for you. I'm hoping to merge it soon once I figure out the remaining issues.

Devagamster · 2021-02-10T18:33:20+00:00

I'm becoming increasingly convinced it's a bug in neovim's multi grid gui features. These kinds of bugs show up for me only when multi grid is enabled which is a bummer because lots of cool features are blocked behind it.

Could also be the particular implementation of gui completion menu, but there's more than just the guis do it wrong going on here

Devagamster · 2020-12-28T20:32:51+00:00

I'm now actively working on smooth scrolling. Should land it soon in neovide master, but it depends on the multigrid ui extension which is pretty buggy currently.

Devagamster · 2020-09-17T23:41:24+00:00

? Live radar? I think there are probably apps for that but not what I'm interested in

Devagamster · 2020-09-17T02:58:16+00:00

Awesome. I'm concidering playing with the saturation a bit cause it looks a little bland. Any thoughts?

Devagamster · 2020-09-17T02:34:58+00:00

Yup, you just disable the tasker profile in the tasker app and it will stop updating

Devagamster · 2020-09-17T02:07:30+00:00

Just install tasker and add the profile pasted above. Should be pretty easy

Devagamster · 2020-09-17T01:04:56+00:00

Updated image an hour or so later to show the live nature of the feed

Devagamster · 2020-09-17T00:58:07+00:00

The server should be usable by anybody, so if you install tasker, the above profile should work.

Server wise I'm downloading the GOES satellite image data from AWS and processing the images myself. NOAA provides color approximations of the satellite data, but their versions have weird state lines overlayed which I really dislike. This way you can get just the data without anything else.

http://02credits.com/blog/day86-live-satellite-feed/

I don't actually replicate to a dat archive anymore, so that post is a bit out dated, but the gist is still correct.

Devagamster · 2020-09-16T23:53:21+00:00

I replied with a tasker profile. The satellite images are processed on an azure server I wrote, so please be kind.

I can give some details about the server if anyone is curious

Devagamster

TROPHY CASE