Kyle Kovacs

_From @chick on November 5, 2018 3:11_ Migrate to the firrtl-interpreter repo.

I had the [same issue](https://github.com/rcarriga/nvim-notify/issues/189#issuecomment-1919622230) as @jdujava with the extra line. I can confirm that adding both changes from @dasupradyumna and @jdujava fixes the notification position for `fade`, `slide`, `static`,...

I thought this feature would be useful too, so I made a pull request (#248) to add the appropriate command. I think another separate useful feature to help @miversen33's use...

For me, using `fade_in_slide_out` positions the notification correctly, while `fade`, `slide`, and `static` position it over the statusline. ### Position with `fade_in_slide_out` 😄  ### Position with `fade`,...

Link issue #3255

Hi Michal, thank you for the response. > possible in case there are lots of validation tasks. It's also possible I wrote the `must` statements in a non-optimal way... >...

Sorry for making this comment so long, but there's a lot to say. > There is a fairly recent [feature](https://github.com/sysrepo/sysrepo/blob/master/src/sysrepo_types.h#L180) ### For anyone else that comes across this issue, here's...

### `must` statemets I fully don't expect you to help with my YANG model, since it's my issue to figure out, but if you're willing to take a look and...

Upon more investigation, I don't think a custom DS plugin is worth doing for my case, because modifying the backing JSON file directly doesn't hook into the sysrepo-plugind plugins anyway,...

> EDIT: Implemented now when you can set all the modules with disabled running DS in a cmake variable. I noticed today that my `startup` and `running` datastores were separate....