folke / dot

☕️ My Dot Files

Dot Files

You can find my Neovim dot files here

dot's Issues

Rust-tools doesn't appear used here, and if it is, buffer becomes all white text on launch

Hi, so my config is heavily based off yours. I noticed rust-tools doesn't work, and that's because rust_analyzer is loaded in plugins/lsp/init.lua

I modified it to be like so at the bottom:

for server, opts in pairs(servers) do
  opts = vim.tbl_deep_extend("force", {}, options, opts or {})

  if server ~= "tsserver" and server ~= "rust_analyzer" then
    require("lspconfig")[server].setup(opts)
  elseif server == "rust_analyzer" then
    require("plugins.rust-tools").setup(opts)
  elseif server == "tsserver" then
    require("typescript").setup({ server = opts })
  end
end

however, this causes the first buffer opened in a session to be pure white, which is fixed by running :e

I'm here to ask for insight on how you think you could fix this, because rust-tools' inlay hints are just so nice I would rather not give them up, thanks :)

Question regarding the bar you're using

What bar are you using, I feel like I'm kind of missing it in your files and would love to use it for myself and maybe also add some more stuff to it. I just love how you have some of these widgets set up

Can I use your nvim config ?

Hello, Can you share your local nvim projects so I can use your nvim config ?

Thanks

Getting error while try up your nvim build.

Getting several error from the below images, it is because i done a mistake or any extra change needed, to make it work.

Do you mind null-ls got archived?

Hi, @folke
I see you as a most pragmatic and experienced neovim user.
So i wondering what is your thoughts on possible vulnerabilities to your formatting and diagnostics on next neovim minors.
Null-ls been maintaining the linkage between multiple sources and now it doesn't. So community got frustrated a bit because of leak of that tool in near future.

I totally understand if you feel like it's not necessary until it fails in next versions.
But can you share your thoughts around that? Like what you think better to do when the issues came out - keep using null-ls parts that's still func ok or migrate to stuff like neoformat/formatter.nvim or any other options that i can't imagine (i'm not taking seriously COC and ALE in nowadays)

I will be happy if you'd have some time to discuss here

Lazy

When u put in github lazy.nvim

Accidentally leaked API key

Hey, I was just looking through your dotfiles and stumbled upon this line.

dot/nvim/lua/plugins/coding.lua

Line 5 in d2bf2a9

api_token = "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",

Apparently hfcc.nvim now also supports setting the key using environment variables or by using the hugginface cli. See here.
This change was ironically introduced 2 days after your commit, which added the plugin to your config.

nVim magic

Hi,

I wonder if you plan do jam a write-up on your setup:

Indentline that works over empty lines with dynamic highlight is especially interesting.

Thanks!

Dynamic structuring of plugins

Hi, I currently run a small nvim distro and could use some guidance on how to implement additional plugins, beyond what is set up by default for the distro.

Example implementation for default plugins:

require('lazy').setup('cosmic.plugins', {
  ui = {
    border = 'rounded',
  },
})

Requested/wanted implementation:

require('lazy').setup({
  'cosmic.plugins',
  'another/plugin'
}, {
  ui = {
    border = 'rounded',
  },
})

Where cosmic.plugins is sourced from lua/cosmic/plugins as expected and another/plugin is sourced from git.

This would be very helpful for me with defining a set of "default" plugins.

I realize there are alternatives but none that would allow me the ease of use of simply adding cosmic.plugins as the source for my default plugins.

Any changes or advice would be greatly appreciated!

Using `opts` with `nvim-treesitter/nvim-treesitter`

Hi,

Your dots have been a massive source of inspiration, a curated list of awesome plugins, and a great example of Lazy setup. Thanks for publishing them! (and awesome work on Lazy, btw!).

I'm hoping that you can help me understand something in your config of tree-sitter:

I've noticed that you're using opts to configure nvim-treesitter/nvim-treesitter (https://github.com/folke/dot/blob/master/config/nvim/lua/plugins/treesitter.lua#L23).

My understanding is that opts calls <module-name>.setup {opts}.

However, nvim-treesitter configuration is passed to nvim-treesitter.configs (https://github.com/nvim-treesitter/nvim-treesitter#modules).

On my end, I cannot seem to make opts={…} work, and need to instead use config = function() … end:

{
    "nvim-treesitter/nvim-treesitter",
    require 'nvim-treesitter.configs'.setup {
        ...opts
    },
}

It's totally possible I'm missing an obvious feature that would make this work (or maybe a future feature of Lazy that currently only exists in your dev environment?), but I just can't seem to find it if that's the case.

Thanks in advance!

Wondering how your dashboard/loading previous sessions works with persistence

I have based my config heavily off yours since I think it's the most well written, comprehensive, and feature-rich I've come across. As such, figuring out a few quirks has taken some time but is quite fun. The issue I'm facing is say I'm in directory ~/projects/rust-project and I previously had a session open with a few buffers. The session does in fact save in .config/nvim/sessions/dir-separated-by-%s.vim, however when going back with "nvim" in the root project dir, hitting "SPC s l" does nothing, and I cannot restore this session. Let me know how to do so! Thanks :)

change color of matching closing element

Hello, I am using you'r nvim config, I wont to thank you for the hard work, its my favorite setup, I have 2 things however that I can't change because I cant find where they are being defined..
where do you define the color change to the matching closing element like (, { and even jsx tags.
In addition where do you change the status line to show the line of the closing tag if it's offscreen?
Thank you again...

bat colorscheme not applying

I'm using @folke bat config in my config, but I'm unable to use config colors in bat file

I'm so confused right now.

How did you set up your outline's postition?

sorry i'm new to neovim, and i've searched through your nvim config but didn't find where is it set and encoutered error when derectly open nvim with your config.

wezterm-types?

Hi Folke - I noticed you have a .neoconf.json for wezterm-types.

Is that this repo: https://github.com/nekowinston/wezterm-types/tree/main or something you've made custom?

If it's custom, and you have the time, would you mind putting together a repo / plugin for it?

Thanks for all your amazing work in the Neovim community!

{
  "lspconfig": {
    "lua_ls": {
      "Lua.workspace.library": [
        "/home/folke/.local/share/nvim/lazy/wezterm-types/types"
      ]
    }
  }
}