u/114sbavert

Hey all,

I recently re-wrote the popular LazyGit plugin that is often recommended here for integrating LazyGit into NeoVim. I was using it for some time but since I only started using NeoVim, I was not very experienced in configuring it but overtime I noticed many issues the plugin has

I raised an MR with a fix for one of the issues but while fixing it, I realized the codebase is very bloated and was suffering from the burden of legacy support, so, I have forked and overhauled the codebase and added a few meaningful QoL improvements, namely:

1. Instead of using vim.g.* for configuration, it now uses the conventional setup({}) function
2. Plenary-based windows no longer spawn new lazygit processes, while leaking older ones (this was the issue my MR focused on).
3. You can now use * wildcards to specify custom lazygit configurations (in case you divide them into multiple files or whatever).
4. Plenary based buffers, as with regular buffers, now get custom buffer and window properties. This was not done in the older code for some reason.
5. Replaced legacy VimScript FFI calls (such as through vim.fn.* methods) with vim.api.* wherever possible.

The only major trade offs are:

1. No more Vim support (I removed all VimScript code)
2. Needs NeoVim 0.10 >=

Link to my fork: https://github.com/103sbavert/lazygit.nvim

Also, AI was used, but for adding LuaCATS doc comments for type hints and completions, to re-arrange already finished code into different files (without changing its internals or logic), and to understand the previous code structure but every line of code is hand crafted and well understood by me. If you find any issues, please report them. This was a major re-write so some things may have fucked up, let me know if that's the case.

Also, I hate vibe coding, so rest assured, this is not one of those shitty AI-slop plugins.

Hey everyone, I recently started using NeoVim and quite like it. I am not very experienced, I only started using it the last week of June. I am tinkering around with my config which is forked off the kickstart NeoVim config by TJ. I have configured notify.nvim in my nvim config like so:

require("noice").setup({
  routes = {
    {
      view = "shell_display",
      filter = {
        event = "msg_show",
        kind = {
          "shell_out",
          "shell_err",
        },
      },
    },
  },
  views = {
    shell_display = {
      view = "split",
      size = "auto",
      enter = true,
      focusable = false,
      close = {
        keys = { "q", "<Esc>" },
      },
      buf_options = {
        filetype = "noice_shell_display",
      },
      format = {
        "{cmdline}",
        "{message}",
        "\n",
      },
    },
  },
})

(Find more at https://github.com/103sbavert/nvim-config/)

And the result looks like this: https://freeimage.host/i/C1oFrRj

This keeps appending to the original scratch buffer downwards (instead of replacing its contents) and appends the hint text that follows the cursor in the cmdline as well.

But I want to change the configuration a bit to always re-write the history buffer when a new command is triggered and only the actual shell command that was run is shown. Is that something possible with noice/nvim at this moment?

Greetings all,

TLDR: Created a dummy video generation CLI tool in Python because not many good ones exist. Realized Golang is better suited for the job and I really wanted to learn the language and needed an excuse to learn it anyway.

---

I am primarily a .NET and C# backend developer with some grasp on DevOps due to my close involvement with the actual DevOps team at my company which is busy implementing AI in everything that exists and because I daily Linux. I have been really liking what I've heard about Golang in the community so I really wanted to start learning it. I felt like it was the right balance between frictionless development and good runtime performance,

Yesterday I needed something that I realized isn't as abundant on the internet as I thought. I wanted something to retrieve random (real) videos for testing a thumbnail generation tool I am building at work. I was hesitant to use random videos on YouTube out of fear of "corporate-unfriendly" content in the video as well as legal issues with using the video for commercial use unless I've fully watched it. I wanted something like picsum.photos (you're welcome) but for videos. Before this need, I have always used sparse files using commands like truncate but they obviously only contain garbage data that cannot be transcoded. The idea was to be able to retrieve random, copyright free, completely PG13, REAL videos with a video stream but no meaningful content and on demand.

The goal of the thumbnail generation tool focuses somewhat on low-memory overhead and speed because that was one of the bottlenecks of the existing tool we used at the company. I quickly realized finding dummy sample videos of 200 - 500 MiBs is rather easy but finding videos 2 - 3 GiB large is not unless you use commercial content which invoked my aforementioned concerns. Hence the inspiration for the below tool:

GitHub https://github.com/103sbavert/vidgen

While the above text explains the intention of making the project at all, I am actually re-wrting the one-day worth of Python work I did in Golang (check the dev/golang-rewrite branch) because I really wanted a reason to learn the language without feeling I'm performing household chores by watching YT tutorials at the ripe age of 23.

Anyways, go ahead and give your best critique. Also do read the README.md (it's in the name).