fosstodon.org is one of the many independent Mastodon servers you can use to participate in the fediverse.
Fosstodon is an invite only Mastodon instance that is open to those who are interested in technology; particularly free & open source software. If you wish to join, contact us for an invite.

Administered by:

Server stats:

9.9K
active users

#LazyVim

1 post1 participant0 posts today

I was looking into #neovim yesterday (have a #lazyvim config I've not touched for some time) Some general thoughts:
- Neovim still looks good, is still fast, navigating and changing code is a pleasure.
- Ecosystem bikeshredding is just on another level - I have not touched nvim for a year and I have no idea about half of the packages. Blink, snacks, what is all this? My thoughts are that maybe the provided level of abstraction is too low and offloads everything to packages.

Eureka 🥳

I've now got Neovim :neovim: using working really nice. Including the Python :python: LSP showing errors for not installed libraries. Awesome!

And yes, I do prefer as color scheme.

Now it's time to do something about that ugly looking green bar on top...

Hello #fediverse

I am happy to report I have managed to migrate to #LazyVim from my custom #nvim config.

The major pain point for me was that Konsole was screwing up my keybindings:
1. It translated `Ctrl+/` to `Ctrl+_` (this took me so long to figure out, thank you r/neovim)
2. I never got to register "Ctrl+`" keybinding for toggling terminal. (This is originally done by (1) but this is something I use in VSCode so I needed it)

Alas, I gave in and installed #Alacritty and all my problems have vanished. I also managed to customize it a little.

Now, I need to figure out how to manage the dotfiles!! Any ideas? What do you use?

#diary#vim#linux

Update: I figured it out, answer in next toot

Would any #LazyVim users be willing to help me out? I'm trying to get a beloved Vim plugin working with lazy.vim and I haven't been able to figure it out.

It's vim-textobj-quote, for putting typographic/"curly" quotes in text: github.com/preservim/vim-texto

Use ‘curly’ quote characters in Vim. Contribute to preservim/vim-textobj-quote development by creating an account on GitHub.
GitHubGitHub - preservim/vim-textobj-quote: Use ‘curly’ quote characters in VimUse ‘curly’ quote characters in Vim. Contribute to preservim/vim-textobj-quote development by creating an account on GitHub.

J’hésite à passer de Thunderbird à #Neomutt mais je me pose deux questions :
1. Existe-t-il un plugin qui permette, automatiquement quand la pièce jointe est trop lourde, de proposer la transformation de la pièce jointe en lien (notamment sur un serveur Nextcloud) ? C’est une fonctionnalité de Thunderbird dont je me sers très régulièrement.
2. Existe-t-il une distribution de Neomutt préconfigurée facile pour débuter, sur le principe de #Lazyvim , qui m’a aidé à sauter le pas vers #Neovim ?
#mutt

Yeah, I’m sold on #LazyVim, needs more tweaking but it's such a sensible starting point and more stable than my custom config.

Also Snacks, what an amazing collection of tools. Folke apparently had an 'hey echasnovski (mini.nvim), hold my beer.’ moment.

You could build one hell of an #neovim code editor config with those two multi-function plugins alone.

U zult zich afvragen: wat doet zo'n cupcake nou op een zaterdagavond?
Welnu, ik heb me gek gepuzzeld hoe ik in #neovim html/php code kan formatteren.
En het is gelukt!
Deze configuratie formatteert eerst de code als html en daarna pakt het de php code en formatteert deze netjes. Ik kan u zeggen, ik ben er erg in mijn nopjes mee.
Ik gebruik de LazyVim neovim distributie.

return {
  "stevearc/conform.nvim",
  opts = {
    -- log_level = vim.log.levels.DEBUG,

    formatters = {
      prettier_php = {
        command = "prettier",
        args = {
          "--plugin",
          "/home/xxxxxx/.nvm/versions/node/v23.9.0/lib/node_modules/@prettier/plugin-php/src/index.mjs",
          "$FILENAME",
        },
      },
      prettier = {
        options = {
          ext_parsers = {
            php = "html",
          },
        },
      },
    },
    formatters_by_ft = {
      php = { "prettier", "prettier_php" },
    },
  },
}
I've completely moved my vanilla NeoVim configuration over to a LazyVim config tonight. I had some difficulties to get UltiSnips to work but that was all. It was a good decision after all. My old config was a mess. Now it's simple and clean, and LazyVim has a lot of tools already set up the right way. For example Mason automatically loads LSP servers when needed AFAIK until now. There is also a GitTUI in the LazyExtras which is really easy to use. I like it!

#NeoVim #LazyVim #Vim #Editor

Ok I have spent one working week with #LazyVim and "things that infuriate me" outnumber "neat features" by a distressing margin. I might give it one more week, but it's not looking good for everyone's favorite Neovim setup.

goyo.vim을 lazy.vim에 설치하는 방법을 찾았다.

```
return {
{ "junegunn/goyo.vim" },
}
```

goyo.vim 말고도 vim-plug로 작동하는 플러그인은 이런 방식으로 설치 가능한 듯 하다. 파일은 .lua 확장자로 저장하고 `nvim/lua/plugins` 폴더에 넣으면 되는 듯.

참고: github.com/MiragianCycle/OVIWr

GitHubOVIWrite/lua/plugins/goyo.lua at main · MiragianCycle/OVIWriteIntegrated Writing Environment (IWE) based on NeoVim - MiragianCycle/OVIWrite
#vim#neovim#lazyvim
Continued thread

LazyVim은 깔았다가 지워버렸는데, vim 기초도 숙지 못 한 상태에서 덜컥 LazyVim부터 건드리면 안 될 것 같아서. 최대한 ‘바닐라(순정)’ 상태로 쓰고 싶은 생각도 크고. (Vim-plug 씀)
#lazyvim #vim #vimplug