Share your setups #36
Replies: 35 comments 105 replies
-
|
Hi, my config https://github.com/axpira/dotfiles/blob/main/nvim/init.lua |
Beta Was this translation helpful? Give feedback.
-
|
Thanks! That is a minimal one indeed :) Couple of observations:
|
Beta Was this translation helpful? Give feedback.
-
require("mini.base16").setup {
palette = {
base00 = "#000000",
base01 = "#111111",
base02 = "#333333",
base03 = "#bbbbbb",
base04 = "#dddddd",
base05 = "#ffffff",
base06 = "#ffffff",
base07 = "#ffffff",
base09 = "#ff2222",
base08 = "#ff9922",
base0A = "#ff22ff",
base0B = "#22ff22",
base0C = "#4444ff",
base0D = "#22ffff",
base0E = "#ffff22",
base0F = "#999999",
},
use_cterm = false,
}
require("mini.comment").setup {}
require("mini.completion").setup {}
require("mini.jump").setup {
mappings = {
repeat_jump = "",
},
highlight_delay = 0,
}
require("mini.pairs").setup {}
require("mini.sessions").setup {
directory = vim.fn.stdpath "config" .. "/sessions",
}
require("mini.starter").setup {
evaluate_single = true,
}
require("mini.statusline").setup {}
require("mini.surround").setup {
n_lines = 100,
mappings = {
add = "S",
delete = "ds",
find_left = "[s",
find = "]s",
highlight = "",
replace = "cs",
update_n_lines = "",
},
}
require("mini.tabline").setup {} |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, Adam! Some thoughts:
|
Beta Was this translation helpful? Give feedback.
-
|
I use I honestly expected |
Beta Was this translation helpful? Give feedback.
-
|
I tried to recreate vim startify as close as possible: local starter = require('mini.starter')
local my_items = {
starter.sections.builtin_actions(),
{ name = 'Sessions', action = ":lua require'telescope'.extensions.sessions.sessions{}", section = 'Telescope' },
{ name = 'Recent Files', action = ':Telescope oldfiles', section = 'Telescope' },
{ name = 'File Brower', action = ':Telescope file_browser', section = 'Telescope' },
-- starter.sections.recent_files(10, false),
-- starter.sections.recent_files(10, true),
-- Use this if you set up 'mini.sessions'
starter.sections.sessions(9, true),
{ name = 'Addons', action = ':e ~/.config/blender/2.82/scripts/addons', section = 'Bookmarks' },
{ name = 'NvimPlugs', action = ':e ~/.local/share/nvim/site/pack/packer/start', section = 'Bookmarks' },
}
starter.setup({
-- Whether to open starter buffer on VimEnter. Not opened if Neovim was
-- started with intent to show something else.
autoopen = true,
-- Whether to evaluate action of single active item
evaluate_single = true,
-- Items to be displayed. Should be an array with the following elements:
-- - Item: table with <action>, <name>, and <section> keys.
-- - Function: should return one of these three categories.
-- - Array: elements of these three types (i.e. item, array, function).
-- If `nil` (default), default items will be used (see |mini.starter|).
items = my_items,
-- Header to be displayed before items. Should be a string or function
-- evaluating to single string (use `\n` for new lines).
-- If `nil` (default), polite greeting will be used.
header = nil,
-- Footer to be displayed after items. Should be a string or function
-- evaluating to string. If `nil`, default usage help will be shown.
footer = nil,
-- Array of functions to be applied consecutively to initial content.
-- Each function should take and return content for 'Starter' buffer (see
-- |mini.starter| for more details).
content_hooks = {
starter.gen_hook.adding_bullet(),
starter.gen_hook.indexing('all', { 'Builtin actions', 'Telescope', 'Bookmarks'}),
starter.gen_hook.padding(5, 2),
starter.gen_hook.aligning('left', 'top'),
},
-- Characters to update query. Each character will have special buffer
-- mapping overriding your global ones. Be careful to not add `:` as it
-- allows you to go into command mode.
query_updaters = [[abcdefghijklmnopqrstuvwxyz0123456789_-.]],
}) |
Beta Was this translation helpful? Give feedback.
-
|
I had a go at getting mini.ai to work with treesitter text objects. It seems to work alright with the little testing I've done, but I'm sure there are some edge cases that will break this. Credit for most of the work goes to the nvim-treesitter-textobjects plugin, the One other thing I added is the ability to use a table of queries instead of just one. Most of the logic was already there, it should just find the best match of any of the given queries. I'm 99% sure this is more complicated than it needs to be, as I've just kinda smooshed the two things together. UpdateThanks to the amazing update to the api (seriously, thanks so much @echasnovski), I have massively simplified this to the below function. My approach does come with the dependency on the nvim-treesitter plugin, but it supports multiple queries in one object and should have full support for all queries defined by nvim-treesitter-textobjects. local queries = require "nvim-treesitter.query"
local miniAiTreesitter = function(ai_type, _, _, query_list)
ai_type = ai_type == "a" and ".outer" or ".inner"
query_list = vim.tbl_map(function(query) return query .. ai_type end, query_list)
local matches = {}
for _, query in pairs(query_list) do
vim.list_extend(matches, queries.get_capture_matches_recursively(0, query, "textobjects"))
end
matches = vim.tbl_map(function(match)
local from_line, from_col, to_line, to_col = match.node:range()
return {
from = { line = from_line + 1, col = from_col + 1 },
to = { line = to_line + 1, col = to_col + 1 }
}
end, matches)
return matches
end
local miniAiTreeWrapper = function(query_list)
if type(query_list) ~= "table" then
query_list = { query_list }
end
return function(ai_type, _, opts)
return miniAiTreesitter(ai_type, _, opts, query_list)
end
end
require("mini.ai").setup({
custom_textobjects = {
o = miniAiTreeWrapper({"@block", "@conditional", "@loop"}),
s = miniAiTreeWrapper({"@function", "@class"}),
c = miniAiTreeWrapper("@comment"),
},
})If I make any further changes to this you should be able to find them here |
Beta Was this translation helpful? Give feedback.
-
|
@jonatan-branting, latest |
Beta Was this translation helpful? Give feedback.
-
|
Another quick one, git hunks. This one depends on gitsigns.nvim to get the list of hunks. I think the way I'm getting the hunks is using an internal api, so no guarantees that it won't break without warning. I tried using the local miniAiGitsigns = function()
local bufnr = vim.api.nvim_get_current_buf()
local hunks = require("gitsigns.cache").cache[bufnr].hunks
hunks = vim.tbl_map(function(hunk)
local from_line = hunk.added.start
local from_col = 1
local to_line = hunk.vend
local to_col = #vim.api.nvim_buf_get_lines(0, to_line-1, to_line, false)[1] + 1
return {
from = { line = from_line, col = from_col },
to = { line = to_line, col = to_col },
}
end, hunks)
return hunks
end |
Beta Was this translation helpful? Give feedback.
-
|
Question for the ignorant (aka, me); how might you be using this to visually select, say, Thanks! |
Beta Was this translation helpful? Give feedback.
-
Hopefully I'm not misunderstanding. Are you referring to the word object in my config? If so that was taken from the examples in the mini.ai documentation. But you're right, it doesn't include underscores, I've just updated mine by replacing %w with [%w_]. I'm sure there are lots of other cases where it behaves differently from the default object that I haven't realised out yet (and on that I have, it doesn't deal with characters like super and subscripts or Greek letters properly, my next goal is to sort that out) |
Beta Was this translation helpful? Give feedback.
-
|
🤦 thank you and thank you. i should have dug in further into what those regex patterns. (i loathe regex 🤣) |
Beta Was this translation helpful? Give feedback.
-
|
mini.nvim is beautifull one set plugin, here is my setup |
Beta Was this translation helpful? Give feedback.
-
|
Thanks so much! |
Beta Was this translation helpful? Give feedback.
-
|
previously i used base16 template, but there are some plugins that are not integrated properly and I haven't had time/time to customize base16 with the plugins I'm using, it's really impressive if all the plugins can be integrated into mini.nvim |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I noticed that :) Do you remember which plugins you were using felt like lacking 'mini.base16' support? It would really help me prioritize which plugins to add. |
Beta Was this translation helpful? Give feedback.
-
|
i would love if mini.nvim could integrate easily with some lsp for neovim, Neovim LSP and DAP I will create a new issue for new features |
Beta Was this translation helpful? Give feedback.
-
|
This is my config It's still a work in progress (I started a couple of days ago, switching from vscode after I decided, finally, to go 100% neovim). So mini is currently 90% of my plugins, if not more. 🤣 This is amazing, I said in reddit and I need to say that again: thank you for this impressive work. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing!
Hope you enjoy this and spread the word about it! This helps a lot. One suggestion, though: my preference is to supply config settings only if it differs from defaults. It both makes config file more concise and limits possibility of possible breaking changes (which I try to make very rare). There were cases when way of supplying setting changed while preserving default behavior, so nothing was broken if nothing was supplied. For example, I am writing a big update to 'mini.surround'. It will change some default surroundings, the way custom "input" surroundings are defined, add new search methods, and more. Basically, #103. After that, your comment in 'mini.surround' config will be outdated. Not a big deal, but I hope I made the point. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, if I have the opportunity I will help in spreading about this. I think a video will be helpful, somehow, but I am not a youtuber. If only some vim-rock-star could do a video about it... Regarding your suggestion, I think this is something I copy-pasted when I was starting with the plugin... Do you mean that adding a table to setup that does not differ from the default is pointless, right? |
Beta Was this translation helpful? Give feedback.
-
It doesn't have any effect, yes. Here is my config, for example. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I have edited my config. |
Beta Was this translation helpful? Give feedback.
-
|
An idea that maybe could be of interest of more people: https://www.reddit.com/r/neovim/comments/x0hf25/nicer_jupyter_notebook_workflow_with_neovim/ |
Beta Was this translation helpful? Give feedback.
-
|
Nice! Couple of thoughts:
By the way, I am a data scientist myself. A bit controversial, but I don't really like notebooks. Prefer using terminal window with opened REPL ( |
Beta Was this translation helpful? Give feedback.
-
|
Hey! Thanks for the suggestion!
|
Beta Was this translation helpful? Give feedback.
-
|
Sorry, answered in the wrong thread. I've hidden that as off-topic. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Very nice. (Minimap scrolls to the sides - not necessary.)
|
Beta Was this translation helpful? Give feedback.
-
|
dragging the mouse to the side of minimap can cause display corruption, i'm not sure what causes this
|
Beta Was this translation helpful? Give feedback.
-
|
Not sure what you mean here. By default map window shouldn't react on mouse clicks. If you set |
Beta Was this translation helpful? Give feedback.
-
|
Mini is my favourite plugin. My neovim setup is minimal, so I really enjoy that I can setup all my mini modules of choice without setting any preferences, because the defaults are just so solid for me. The proof is that I can just loop an array to initialise them. |
Beta Was this translation helpful? Give feedback.
-
|
You can look at mine in here
|
Beta Was this translation helpful? Give feedback.
-
|
Nice! Thanks for sharing. Two immediate things I've noticed:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks, I copied the loop and forgot to edit it... As for |
Beta Was this translation helpful? Give feedback.
-
Ah, yes. 'mini.nvim' uses |
Beta Was this translation helpful? Give feedback.
-
No problem 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Here is my setup: The border colors for the notify window seem to be both fore- and background to be the same: |
Beta Was this translation helpful? Give feedback.
-
|
Nice!
This is not a color scheme problem. This looks like an effect of positive
That was my mistake. Vim's Base16 implementation has I generally have all 'mini.nvim' modules to have actually visible border (meaning Couple of notes:
|
Beta Was this translation helpful? Give feedback.
-
|
Argh, I'm feeling really dumb now. I'm pretty sure it was working some weeks ago. Was there any change in mini.basics? |
Beta Was this translation helpful? Give feedback.
-
Yes, there was 937386c, but it should only affect Neovim<0.10 (which, I presume, you are using). So not sure what is going on. |
Beta Was this translation helpful? Give feedback.
-
|
I'm using 0.10.0-dev-1588 and 0.10.0-dev-1589, so I should rather look into my terminals :) But as long as I got it working, I'm fine. |
Beta Was this translation helpful? Give feedback.
-
Ah. I'd suggest to update the version then. It would have fixed both of the issues. Generally, if you have problems using Nightly, first try to use newer version. |
Beta Was this translation helpful? Give feedback.
-
|
Here is how { -- Split parameters, simpler version of treesj.lua
url = 'https://github.com/echasnovski/mini.splitjoin',
version = '*',
opts = {
mappings = {}, -- Configured in treesj => treesitter.lua
detect = {
separator = '[,;]'
}
}
},
{ -- Split/Join, integrated with mini.splitjoin
url = 'https://github.com/Wansmer/treesj',
dependencies = { 'https://github.com/nvim-treesitter/nvim-treesitter/' },
keys = {
{ '<leader>m', mode = { 'n', 'v' }, desc = 'Toggle split' }
},
config = function()
local tsj = require('treesj')
tsj.setup({
use_default_keymaps = false,
max_join_length = 512,
})
local function get_pos_lang(node)
local c = vim.api.nvim_win_get_cursor(0)
local range = { c[1] - 1, c[2], c[1] - 1, c[2] }
local buf = vim.api.nvim_get_current_buf()
local ok, parser = pcall(
vim.treesitter.get_parser,
buf,
vim.treesitter.language.get_lang(vim.bo[buf].ft)
)
if not ok then
return ""
end
local current_tree = parser:language_for_range(range)
return current_tree:lang()
end
vim.keymap.set({ 'n', 'v' }, "<leader>m", function()
local tsj_langs = require("treesj.langs")["presets"]
local lang = get_pos_lang()
if lang ~= "" and tsj_langs[lang] then
require("treesj").toggle()
else
require("mini.splitjoin").toggle()
end
end)
end
} |
Beta Was this translation helpful? Give feedback.
-
|
I spent this morning tweaking the look of my mini.statusline: Wide: Wide with search count: Less wide: Narrow: My changes from the default:
I spent a couple hours (yes, sadly), experimenting with lots of other variations:
I love I love I also enabled The only packages I've tried thus far that I did not care for were With regards to Overall, love all the hard work you've put into the mini packages. Simply amazing! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the detailed feedback! It is much appreciated! Some thoughts:
I can see that people are not really used to having those around. Strangely enough, for me it is quite essential during actual text edit, as I find myself checking this information often.
We all have been there :)
All config and thoughts here are very good so far. I think you'll fit nicely in the Neovim users community :)
Understandable. There are other configurations besides default one (which is more or less tailored to what I feel is best) and/or jumping spotter is extensible, if you'll ever got time to tweak the config again. |
Beta Was this translation helpful? Give feedback.
-
|
Interesting! I just tested all of them and I really like the While I won't make excuses for myself, as a matter of marketing, it might help others if this bullet point in the README
had a few sub-bullets enumerating the other built-ins for others to see what is in the realm of possibility. The only other functionality that I rely on from Flash is the ability to select treesitter scopes, but that's only because I didn't realize treesitter already had incremental search, which I just discovered thanks to your response to this user inquiring about the same. So, I'll be removing Flash in favor of Jump2D now. Thanks for the nudge in the right direction with those other built-ins. Great stuff! |
Beta Was this translation helpful? Give feedback.
-
Sounds reasonable. This is now live on |
Beta Was this translation helpful? Give feedback.
-
|
I prefer |
Beta Was this translation helpful? Give feedback.
-
|
All |
Beta Was this translation helpful? Give feedback.
-
|
Recently migrated to
Highlights: Lazy stats (startup time). Currently updated via auto command due to stats not being available when `mini.starter` starts. -- Set starter footer and refresh after `startuptime` is available
vim.api.nvim_create_autocmd("User", {
pattern = "MiniStarterOpened",
callback = function()
vim.api.nvim_create_autocmd("User", {
pattern = "LazyVimStarted",
callback = function()
local starter = require "mini.starter"
local stats = require("lazy").stats()
local ms = (math.floor(stats.startuptime * 100 + 0.5) / 100)
starter.config.footer = function()
return "⚡ Loaded plugins: "
.. stats.loaded
.. "/"
.. stats.count
.. "\n⚡ Startup time: "
.. ms
.. " ms"
end
starter.refresh()
end,
})
end,
})A dedicated section for workspaces from `workspaces.nvim`. local workspace_items = function()
local workspaces = require "workspaces"
local items = {}
for _, w in pairs(workspaces.get()) do
table.insert(items, {
name = w.name .. " " .. vim.fn.fnamemodify(w.path, ":~:."),
action = "WorkspacesOpen " .. w.name,
section = "Workspaces",
})
end
return items
endA workaround for centralizing header and justifying select sections. -- A workaround to centralize everything.
-- `aligning("center", "center")` will centralize the longest line in
-- `content`, then left align other items to its beginning.
-- It causes the header to not be truly centralized and have a variable
-- shift to the left.
-- This function will use `aligning` and pad the header accordingly.
-- It also goes over `justified_sections`, goes over all their items names
-- and justifies them by padding existing space in them.
-- Since `item_bullet` are separated from the items themselves, their
-- width is measured separately and deducted from the padding.
local centralize = function(justified_sections, centralize_header)
return function(content, buf_id)
-- Get max line width, same as in `aligning`
local max_line_width = math.max(unpack(vim.tbl_map(function(l)
return vim.fn.strdisplaywidth(l)
end, starter.content_to_lines(content))))
-- Align
content = starter.gen_hook.aligning("center", "center")(content, buf_id)
-- Iterate over header items and pad with relative missing spaces
if centralize_header == true then
local coords = starter.content_coords(content, "header")
for _, c in ipairs(coords) do
local unit = content[c.line][c.unit]
local pad = (max_line_width - vim.fn.strdisplaywidth(unit.string))
/ 2
if unit.string ~= "" then
unit.string = string.rep(" ", pad) .. unit.string
end
end
end
-- Justify recent files and workspaces
if justified_sections ~= nil and #justified_sections > 0 then
-- Check if `adding_bullet` has mutated the `content`
local coords = starter.content_coords(content, "item_bullet")
local bullet_len = 0
if coords ~= nil then
-- Bullet items are defined, compensate for bullet prefix width
bullet_len = vim.fn.strdisplaywidth(
content[coords[1].line][coords[1].unit].string
)
end
coords = starter.content_coords(content, "item")
for _, c in ipairs(coords) do
local unit = content[c.line][c.unit]
if vim.tbl_contains(justified_sections, unit.item.section) then
local one, two = unpack(vim.split(unit.string, " "))
unit.string = one
.. string.rep(
" ",
max_line_width
- vim.fn.strdisplaywidth(unit.string)
- bullet_len
+ 1
)
.. two
end
end
end
return content
end
endHow it is used in `MiniStarter.setup`. starter.setup {
-- evaluate_single = true,
header = "███████████████████████████\n"
.. "███████▀▀▀░░░░░░░▀▀▀███████\n"
.. "████▀░░░░░░░░░░░░░░░░░▀████\n"
.. "███│░░░░░░░░░░░░░░░░░░░│███\n"
.. "██▌│░░░░░░░░░░░░░░░░░░░│▐██\n"
.. "██░└┐░░░░░░░░░░░░░░░░░┌┘░██\n"
.. "██░░└┐░░░░░░░░░░░░░░░┌┘░░██\n"
.. "██░░┌┘▄▄▄▄▄░░░░░▄▄▄▄▄└┐░░██\n"
.. "██▌░│██████▌░░░▐██████│░▐██\n"
.. "███░│▐███▀▀░░▄░░▀▀███▌│░███\n"
.. "██▀─┘░░░░░░░▐█▌░░░░░░░└─▀██\n"
.. "██▄░░░▄▄▄▓░░▀█▀░░▓▄▄▄░░░▄██\n"
.. "████▄─┘██▌░░░░░░░▐██└─▄████\n"
.. "█████░░▐█─┬┬┬┬┬┬┬─█▌░░█████\n"
.. "████▌░░░▀┬┼┼┼┼┼┼┼┬▀░░░▐████\n"
.. "█████▄░░░└┴┴┴┴┴┴┴┘░░░▄█████\n"
.. "███████▄░░░░░░░░░░░▄███████\n"
.. "██████████▄▄▄▄▄▄▄██████████\n"
.. "pwd: "
.. vim.fn.fnamemodify(vim.fn.getcwd(), ":~:."),
items = {
workspace_items,
starter.sections.recent_files(10, false, function(path)
-- Bring back trailing slash after `dirname`
return " " .. vim.fn.fnamemodify(path, ":~:.:h") .. "/"
end),
{ section = "Tools", name = "Lazy", action = "Lazy" },
{ section = "Tools", name = "Telescope", action = "Telescope" },
starter.sections.builtin_actions(),
},
content_hooks = {
-- starter.gen_hook.adding_bullet(),
centralize({ "Recent files", "Workspaces" }, true),
},
}
workspaces.nvim |
Beta Was this translation helpful? Give feedback.
-
|
Look very nice! Thanks for sharing! |
Beta Was this translation helpful? Give feedback.
-
|
@echasnovski Thanks for I have edited my comment above to include the fix for using |
Beta Was this translation helpful? Give feedback.
-
|
I thought I’d share mine now. It’s a bit rough around the edges, but it has grown organically, and I’ve become really comfortable with it. The current structure makes it easy for me to add new plugins and see if they fit into my workflow. Overall, it’s nothing fancy—just pretty basic. One cool thing (though still a work in progress) is the Emacs <-> Neovim integration for Magit, which also integrates with RandomHue on the fly. https://github.com/wroyca/dotfiles/tree/main/dot_config/nvim
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing! This looks very thought through. A bit complex for my taste, but everybody is different :) Rescheduling loading shada is a nice touch, but I think it might break plugins which depend on it during startup (although there is a listed 'mini.starter', so I am not sure if it is true in this case). Reading shada file can indeed be a source of a large startup delay, which is mostly fixed by limiting the number of history entries (like search patterns, commands, user inputs) it stores. Limiting from default 10000 to 100 greatly reduces startup time. I personally use this approach |
Beta Was this translation helpful? Give feedback.
-
Correct—it breaks dashboard-type plugins like mini.starter, alpha, startify, and so on. Most of these have a refresh (redraw) command, though, so I've added I also have to admit that I'm growing increasingly frustrated with ShaDa as a whole—it often gets tainted by junk and invalid buffers. We can skip some of this with At some point, I need to figure out a better way to handle my jumplist. Visits sound lovely for that, but I admittedly haven’t gotten around to the slightly higher mental overhead compared to just using In any case, feel free to AMA about the configuration! |
Beta Was this translation helpful? Give feedback.
-
|
I already posted parts of my config in the "show and tell" section. Recently I finished all "todos" and refactored a few hacks into proper solutions. Thanks for creating https://github.com/abeldekat/nvim_pde Most of the plugins are now from |
Beta Was this translation helpful? Give feedback.
-
|
Beautiful and nicely documented config! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback. Very much appreciated! |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone. I just created a webpage in my personal website showcasing my neovim configuration and explaining how I migrated all the way from vim to neovim and switched most of the stuff to mini.nvim. Please do check it out and let me know how do you feel about it. Below is the link for the webpage. https://231tr0n.github.io/blog/config Below is the link for my neovim configuration. https://github.com/231tr0n/config/blob/main/nvim/init.lua Here are a few screenshots of it |
Beta Was this translation helpful? Give feedback.
-
For the first question, the problem I faced was not matching speed but the UI speed. So the thing is when the lines are way too big like in the case of output files from rollup for sveltekit, the UI seems to take a lot of time to move between different entries when in preview mode. Also, overall I felt like how the entries are shown in fzf with multi line are way clearer as in the below picture. For the second question, now that I read your message it actually makes sense, I taught whenever mini.nvim loads, each lua module is added using the |
Beta Was this translation helpful? Give feedback.
-
If you can create a reproducible example (as small as possible, please; without the need to use sveltekit), I'll take a look at what causes it. Chances are, it is indeed the result of how preview is done. But who knows. |
Beta Was this translation helpful? Give feedback.
-
Sure I will try raising a issue on this. I wanted to do it at that time. I just forgot ig. Also just wanted to ask if it is in scope of mini.nvim to use fzf as the backend UI instead of mini.pick for all the pickers provided. Is that doable @echasnovski. If this is doable, I can knock of entire fzf-lua with just mini.pick. |
Beta Was this translation helpful? Give feedback.
-
In theory, any part of picker specification can be customized. For example, use Don't get me wrong, 'fzf-lua' is a great plugin with an awesome author/maintainer. If you feel like it suits your needs better - use it. |
Beta Was this translation helpful? Give feedback.
-
|
The only thing I feel is really great about fzf than mini.pick is that it shows the entries very neatly. That and the above issue of performance was my only concern. Nothing else. |
Beta Was this translation helpful? Give feedback.
-
|
https://github.com/masroof-maindak/nvim I would love some feedback on this (particularly if there's a better way to handle certain things like my base16 & statusline setups... |
Beta Was this translation helpful? Give feedback.
-
|
Very nice! (ASCII art and wizard pug especially :) ) I don't see any obvious problems with either base16 or statusline setups. Maybe these nit picks:
|
Beta Was this translation helpful? Give feedback.
-
|
Much appreciated, thanks bro. |
Beta Was this translation helpful? Give feedback.
-
|
made a config to center each portion of the starter individually 😄 lua configlocal starter = require("mini.starter")
require("mini.starter").setup({
header = table.concat(require("ascii").art.text.neovim.dos_rebel, "\n"),
evaluate_single = true,
footer = os.date(),
items = {
starter.sections.pick(),
starter.sections.builtin_actions(),
},
content_hooks = {
starter.gen_hook.adding_bullet("› "),
function(content)
-- Coords
local header_coords = starter.content_coords(content, "header")
local section_coords = starter.content_coords(content, "section")
local item_coords = starter.content_coords(content, "item")
local footer_coords = starter.content_coords(content, "footer")
-- Lines
local header_width = math.max(unpack(vim.tbl_map(function(c)
local line = content[c.line][c.unit].string
return vim.fn.strdisplaywidth(line)
end, header_coords)))
local section_width = math.max(unpack(vim.tbl_map(function(c)
local line = content[c.line][c.unit].string
return vim.fn.strdisplaywidth(line)
end, section_coords)))
local item_width = math.max(unpack(vim.tbl_map(function(c)
local line = content[c.line][c.unit].string
return vim.fn.strdisplaywidth(line)
end, item_coords)))
local footer_width = math.max(unpack(vim.tbl_map(function(c)
local line = content[c.line][c.unit].string
return vim.fn.strdisplaywidth(line)
end, footer_coords)))
local max_width = math.max(header_width, section_width, item_width, footer_width)
for _, line in ipairs(content) do
if not (#line == 0 or (#line == 1 and line[1].string == "")) then
local line_str = ""
local line_types = {}
for _, unit in ipairs(line) do
line_str = line_str .. unit.string
table.insert(line_types, unit.type)
end
local line_width = 0
for _, type in ipairs(line_types) do
if type == "item" or type == "section" then
line_width = math.max(item_width, section_width)
elseif type == "header" then
line_width = header_width
elseif type == "footer" then
line_width = footer_width
end
end
local left_pad = string.rep(" ", (max_width - line_width) * 0.5)
table.insert(line, 1, { string = left_pad, type = "empty" })
end
end
return content
end,
starter.gen_hook.aligning("center", "center"),
},
}) |
Beta Was this translation helpful? Give feedback.
-
|
Nice! Thanks for sharing! I'd personally suggest wrapping the right hand side of Also a full date in a footer is a simple yet great idea! |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the suggestion, i also added an autocmd to disable mini.indentscope in the starter buffer since all the text was no longer indented the same 
configvim.api.nvim_create_autocmd("User", {
pattern = "MiniStarterOpened",
callback = function(ev)
vim.b[ev.buf].miniindentscope_disable = true
end,
})
local starter = require("mini.starter")
local content_type_width = function(content, section_type)
local coords = starter.content_coords(content, section_type)
local width = math.max(unpack(vim.tbl_map(function(c)
local line = content[c.line][c.unit].string
return vim.fn.strdisplaywidth(line)
end, coords)))
return width
end
require("mini.starter").setup({
header = table.concat(require("ascii").art.text.neovim.dos_rebel, "\n"),
evaluate_single = true,
footer = os.date(),
items = {
starter.sections.pick(),
starter.sections.builtin_actions(),
},
content_hooks = {
starter.gen_hook.adding_bullet("› "),
function(content)
-- Coords
local header_width = content_type_width(content, "header")
local section_width = content_type_width(content, "section")
local item_width = content_type_width(content, "item")
local footer_width = content_type_width(content, "footer")
local max_width = math.max(header_width, section_width, item_width, footer_width)
for _, line in ipairs(content) do
if not (#line == 0 or (#line == 1 and line[1].string == "")) then
local line_str = ""
local line_types = {}
for _, unit in ipairs(line) do
line_str = line_str .. unit.string
table.insert(line_types, unit.type)
end
local line_width = 0
for _, type in ipairs(line_types) do
if type == "item" or type == "section" then
line_width = math.max(item_width, section_width)
elseif type == "header" then
line_width = header_width
elseif type == "footer" then
line_width = footer_width
end
end
local left_pad = string.rep(" ", (max_width - line_width) * 0.5)
table.insert(line, 1, { string = left_pad, type = "empty" })
end
end
return content
end,
starter.gen_hook.aligning("center", "center"),
},
})
|
Beta Was this translation helpful? Give feedback.
-
|
Here's a configuration I cooked up after playing around with |
Beta Was this translation helpful? Give feedback.
-
|
Hi @echasnovski, I looked through some of your snippets in Also, could you help me find a way to change the height of the picker window based on the number of entries?
-- Window related options
require("mini.pick").setup({
window = {
config = {
relative = "cursor",
border = "rounded",
anchor = function() -- doesn't work because `anchor` requires String (Invalid 'anchor': Expected Lua string)
local current_window = vim.api.nvim_get_current_win()
local row, _ = vim.api.nvim_win_get_cursor(current_window)
if row > vim.fn.winheight(current_window) / 2 then
return "SW"
end
return "NW"
end,
row = 1, -- `1` on 'NW' anchor, `0` on `SW` anchor
col = 0,
},
},
}) |
Beta Was this translation helpful? Give feedback.
-
You can use local get_cursor_anchor = function() return vim.fn.screenrow() < 0.5 * vim.o.lines and 'NW' or 'SW' end
local win_config_at_cursor = function()
return {
relative = 'cursor',
anchor = get_cursor_anchor(),
row = 0,
col = 0,
width = math.floor(0.618 * vim.o.columns),
height = math.floor(0.45 * vim.o.lines),
}
endWhat I just realized is that there is no way to customize picker options only for
There are at least three "scopes" to interpret that question:
Thank you for trying it out! 🙏 |
Beta Was this translation helpful? Give feedback.
-
|
@samminhch, on latest local get_cursor_anchor = function() return vim.fn.screenrow() < 0.5 * vim.o.lines and 'NW' or 'SW' end
local win_config_at_cursor = function()
return {
relative = 'cursor',
anchor = get_cursor_anchor(),
row = 0,
col = 0,
width = math.floor(0.618 * vim.o.columns),
height = math.floor(0.45 * vim.o.lines),
}
end
vim.ui.select = function(items, opts, on_choice)
local start_opts = {
options = { content_from_bottom = get_cursor_anchor() == 'SW' },
window = { config = win_config_at_cursor },
}
return MiniPick.ui_select(items, opts, on_choice, start_opts)
endI also plan to include the |
Beta Was this translation helpful? Give feedback.
-
Thank you, this ended up working for changing the anchor position for me :D Also, just saw your recent commit, yay! |
Beta Was this translation helpful? Give feedback.
-
|
Okay, with a little bit of working around with your help, I was able to get the intended behavior I was looking for: vim.ui.select = function(items, opts, on_choice)
local get_cursor_anchor = function() return vim.fn.screenrow() < 0.5 * vim.o.lines and "NW" or "SW" end
local num_items = #items
local max_height = math.floor(0.45 * vim.o.columns)
local height = math.min(math.max(num_items, 1), max_height)
local start_opts = {
options = { content_from_bottom = get_cursor_anchor() == "SW" },
window = {
config = {
relative = "cursor",
anchor = get_cursor_anchor(),
row = get_cursor_anchor() == "NW" and 1 or 0,
col = 0,
width = math.floor(0.618 * vim.o.columns),
height = height,
},
},
}
return MiniPick.ui_select(items, opts, on_choice, start_opts)
end
I think this might be a useful snippet for people to refer to, thank you @echasnovski 😊 |
Beta Was this translation helpful? Give feedback.
-
|
This is what I've got so far, still WIP: https://gist.github.com/luisdavim/b985e141310567969d90114d9cbd15b8 |
Beta Was this translation helpful? Give feedback.
-
|
Nice! Thanks for sharing! Here are a couple of feedback notes:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback, this is my first lua based config. |
Beta Was this translation helpful? Give feedback.
-
|
Welcome to the Lua world! If you have any 'mini.nvim' related questions, feel free to ask here or in a separate question in discussions :) |
Beta Was this translation helpful? Give feedback.
-
|
Hi I just found this discussion and here is my swahpy/mvim. Looking forward to your feedback! |
Beta Was this translation helpful? Give feedback.
-
|
Love the breadcrumbs at the top especially 😊 Also loving the colorscheme too, I'll give evergarden a try as well! |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing! Here are some observations:
|
Beta Was this translation helpful? Give feedback.
-
|
hi thank you so much for reviewing my config and providing the valuable feedback. I did some changes and it now looks better(but still WIP).
|
Beta Was this translation helpful? Give feedback.
-
|
Nice! Looks better now!
Oh, yeah, my bad. I constantly keep forgetting about the buffer-local and global mappings difference when it comes to disabling. In this particular instance, "disabling" global mapping in a single buffer with this little trick. In Lua it would be something like this: -- disable `[` from inserting whole pair in markdown files
-- so that no extra ]s being inserted in links
local f = function(args) vim.keymap.set('i', '[', '[', { buffer = args.buf }) end
vim.api.nvim_create_autocmd('Filetype', { pattern = 'markdown', callback = f })
Yes, indeed, 'mini.visits' supports only on "whole path" scope (i.e. there can not be two or more entries in the index for the same path). But if that is not the deal breaker, this example should be a good fit for a general "bookmark" workflow. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Hello, I would also like to share and get feedback from my configuration:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing!
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your feedback.
|
Beta Was this translation helpful? Give feedback.
-
|
My entire nvim dots are in one file and is great for java development right now. I had a version with lazy a while back with 30 plugins and now I have around 10 and some can be removed. Mini.nvim made life so much easier here is the repo: https://github.com/DarthMooMancer/MacOS-Dots |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, there is indeed something satisfying in having a single file config. I personally prefer keeping |
Beta Was this translation helpful? Give feedback.
-
|
Here is my config: https://github.com/aorith/dotfiles/tree/master/topics/neovim/nvim I really like the consistency of |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I've seen those functions somewhere :) The Here are couple of observations:
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the suggestions, much appreciated. I just did a little refactor with them =) |
Beta Was this translation helpful? Give feedback.
-
|
Nice! Looks better. As a small treat, with the very latest |
Beta Was this translation helpful? Give feedback.
-
|
Hope I'm not late to the party. I read through mini files and IN LOVE with the bookmarks function. Perf for navigation in large projects. However, I'd prefer to have that in per project approach rather than in-memory solution where the bookmarks is lost when closing neovim. So I took the liberty to fork and modify it a little bit to store the data to 'mini.files' setupreturn {
"liketoeatcheese/mini.files",
branch = "main",
dependencies = {},
config = function()
require("mini.files").setup( -- No need to copy this inside `setup()`. Will be used automatically.
{
-- Customization of shown content
content = {
-- Predicate for which file system entries to show
filter = nil,
-- What prefix to show to the left of file system entry
prefix = nil,
-- In which order to show file system entries
sort = nil,
},
-- Module mappings created only inside explorer.
-- Use `''` (empty string) to not create one.
mappings = {
close = "<space>q",
go_in_plus = "L",
--[[ go_in_plus = "L", ]]
go_in = "",
go_out = "H",
mark_goto = "'",
mark_set = "m",
reset = "<BS>",
reveal_cwd = "@",
show_help = "g?",
synchronize = "=",
trim_left = "<",
trim_right = ">",
},
-- General options
options = {
-- Whether to delete permanently or move into module-specific trash
permanent_delete = true,
-- Whether to use for editing directories
use_as_default_explorer = true,
},
-- Customization of explorer windows
windows = {
-- Maximum number of windows to show side by side
max_number = math.huge,
-- Whether to show preview of file/directory under cursor
preview = true,
-- Width of focused window
width_focus = 30,
-- Width of non-focused window
width_nofocus = 35,
-- Width of preview window
width_preview = 55,
},
}
)
vim.api.nvim_create_autocmd("User", {
pattern = "MiniFilesWindowUpdate",
callback = function(args)
vim.cmd([[
setlocal relativenumber
]])
local config = vim.api.nvim_win_get_config(args.data.win_id)
-- Ensure fixed height
config.height = vim.o.lines - 2
--[[ config.height = 10 ]]
-- Ensure title padding
if config.title[#config.title][1] ~= " " then
table.insert(config.title, { " ", "NormalFloat" })
end
if config.title[1][1] ~= " " then
table.insert(config.title, 1, { " ", "NormalFloat" })
end
vim.api.nvim_win_set_config(args.data.win_id, config)
end,
})
local mini_utils = {}
-- Copy just the filename
function mini_utils.copy_filename()
local entry = MiniFiles.get_fs_entry()
if not entry then
return
end
local filename = vim.fs.basename(entry.path)
if vim.fn.has("wsl") == 1 then
vim.fn.setreg("+", filename)
vim.fn.system("wslcopy", vim.fn.getreg("+"))
else
vim.fn.setreg("+", filename)
end
vim.notify("Copied: " .. filename)
end
-- Copy the full path in Windows format (for WSL)
function mini_utils.copy_windows_path()
local entry = MiniFiles.get_fs_entry()
if not entry then
return
end
local filepath = entry.path
-- Convert WSL path to Windows drive letter format
local win_path = filepath:gsub("^/mnt/(%w)", function(drive)
return string.upper(drive) .. ":/"
end)
win_path = win_path:gsub("/", "\\")
if vim.fn.has("wsl") == 1 then
vim.fn.setreg("+", win_path)
vim.fn.system("wslcopy", vim.fn.getreg("+"))
else
vim.fn.setreg("+", win_path)
end
vim.notify("Copied: " .. win_path)
end
-- Copy the full path
function mini_utils.copy_filepath()
local entry = MiniFiles.get_fs_entry()
if not entry then
return
end
local filepath = entry.path
--[[ filepath = filepath:gsub("/", "\\") ]]
if vim.fn.has("wsl") == 1 then
vim.fn.setreg("+", filepath)
vim.fn.system("wslcopy", vim.fn.getreg("+"))
else
vim.fn.setreg("+", filepath)
end
vim.notify("Copied: " .. filepath)
end
-- Copy relative path from current working directory
function mini_utils.copy_relative_path_forward_slash()
local entry = MiniFiles.get_fs_entry()
if not entry then
return
end
local filepath = entry.path
-- Get the current working directory
local cwd = vim.fn.getcwd()
-- Convert both paths to absolute paths
local abs_filepath = vim.fn.fnamemodify(filepath, ":p")
local abs_cwd = vim.fn.fnamemodify(cwd, ":p")
-- Get the relative path
local relative_path = vim.fn.fnamemodify(abs_filepath, ":." .. abs_cwd .. ":~")
-- Remove leading './' if present
relative_path = relative_path:gsub("^%./", "")
relative_path = relative_path:gsub("\\", "/")
if vim.fn.has("wsl") == 1 then
vim.fn.setreg("+", relative_path)
vim.fn.system("wslcopy", vim.fn.getreg("+"))
else
vim.fn.setreg("+", relative_path)
end
vim.notify("Copied: " .. relative_path)
end
-- Copy relative path from current working directory
function mini_utils.copy_relative_path()
local entry = MiniFiles.get_fs_entry()
if not entry then
return
end
local filepath = entry.path
-- Get the current working directory
local cwd = vim.fn.getcwd()
-- Convert both paths to absolute paths
local abs_filepath = vim.fn.fnamemodify(filepath, ":p")
local abs_cwd = vim.fn.fnamemodify(cwd, ":p")
-- Get the relative path
local relative_path = vim.fn.fnamemodify(abs_filepath, ":." .. abs_cwd .. ":~")
-- Remove leading './' if present
relative_path = relative_path:gsub("^%./", "")
if vim.fn.has("wsl") == 1 then
vim.fn.setreg("+", relative_path)
vim.fn.system("wslcopy", vim.fn.getreg("+"))
else
vim.fn.setreg("+", relative_path)
end
vim.notify("Copied: " .. relative_path)
end
-- Set root directory to current directory (equivalent to Neotree's set_root)
function mini_utils.set_root()
-- Works only if cursor is on the valid file system entry
local cur_entry_path = MiniFiles.get_fs_entry().path
local cur_directory = vim.fs.dirname(cur_entry_path)
vim.fn.chdir(cur_directory)
vim.api.nvim_set_current_dir(cur_directory)
MiniFiles.trim_left()
end
local go_in_plus = function()
for _ = 1, vim.v.count1 do
MiniFiles.go_in({ close_on_file = true })
end
end
vim.api.nvim_create_autocmd("User", {
pattern = "MiniFilesBufferCreate",
callback = function(args)
local map_buf = function(lhs, rhs)
vim.keymap.set("n", lhs, rhs, { buffer = args.data.buf_id })
end
map_buf("<Esc>", MiniFiles.close)
map_buf("q", MiniFiles.close)
map_buf("<c-h>", MiniFiles.go_out)
map_buf("<c-l>", go_in_plus)
vim.keymap.set("n", ".", mini_utils.set_root, { buffer = args.data.buf_id })
vim.keymap.set("n", "a", "o", { buffer = args.data.buf_id })
--[[ vim.keymap.set("n", "y", mini_utils.copy_filename, { buffer = args.data.buf_id }) ]]
vim.keymap.set("n", "gm", mini_utils.copy_relative_path_forward_slash, { buffer = args.data.buf_id })
vim.keymap.set("n", "gy", mini_utils.copy_filepath, { buffer = args.data.buf_id })
vim.keymap.set("n", "<s-y>", mini_utils.copy_relative_path, { buffer = args.data.buf_id })
end,
})
local go_in_plus = function()
for _ = 1, vim.v.count1 do
MiniFiles.go_in({ close_on_file = true })
end
end
local map_split = function(buf_id, lhs, direction)
local rhs = function()
-- Make new window and set it as target
local cur_target = MiniFiles.get_explorer_state().target_window
local new_target = vim.api.nvim_win_call(cur_target, function()
vim.cmd(direction .. " split")
return vim.api.nvim_get_current_win()
end)
MiniFiles.set_target_window(new_target)
go_in_plus()
-- This intentionally doesn't act on file under cursor in favor of
-- explicit "go in" action (`l` / `L`). To immediately open file,
-- add appropriate `MiniFiles.go_in()` call instead of this comment.
end
-- Adding `desc` will result into `show_help` entries
local desc = "Split " .. direction
vim.keymap.set("n", lhs, rhs, { buffer = buf_id, desc = desc })
end
vim.api.nvim_create_autocmd("User", {
pattern = "MiniFilesBufferCreate",
callback = function(args)
local buf_id = args.data.buf_id
-- Tweak keys to your liking
vim.keymap.set("n", "<C-A-v>", "<C-v>", { noremap = true, desc = "Enter visual block mode" })
map_split(buf_id, "<C-v>", "vertical")
end,
})
end,
}For the bonus. This is not really related to mini at all. I wrote this since I use search and replace a lot and there's no plugin out there that do this (Not that I know off at least). This basically allows you to visually select the text you one and escape all special characters that sed needs snap it into :%s/ or do the same for the word that you are on, and some other nuggets of searching within buffer, within the project, etc...: search_and_replace.lualocal M = {}
-- Escape special characters in the string
local function escape(str)
return str:gsub("([~\\^$.*\\/%[%]])", "\\%1"):gsub("\n", "\\n")
end
-- Escape special characters in the string
local function escapeFzf(str)
--[[ return str:gsub('([~\\^$*\\/%[%]\'\\])"', "\\%1") ]]
return str:gsub("([\\'])", "\\%1"):gsub("\n", "\\n")
end
local function get_visual_selection()
local start_pos = vim.fn.getpos("'<")
local end_pos = vim.fn.getpos("'>")
-- Adjust for Lua's 1-indexing
local start_col = start_pos[3]
local end_col = end_pos[3]
-- If selection is within a single line
if start_pos[2] == end_pos[2] then
return vim.fn.getline(start_pos[2]):sub(start_col, end_col)
end
local lines = vim.fn.getline(start_pos[2], end_pos[2])
if #lines == 0 then
return ""
end
-- Adjust first and last line of the selection
lines[1] = lines[1]:sub(start_col)
lines[#lines] = lines[#lines]:sub(1, end_col)
return table.concat(lines, "\n")
end
-- Function to be called from Neovim command
function M.SaveWithHighlight()
-- Get the current visual selection
local text = get_visual_selection()
text = escape(text) -- Escape the text for regex
-- Put the text into the command line
vim.fn.setreg("h", text)
end
-- Function to be called from Neovim command
function M.SubstituteWithPreviousHightlightHighlightMakeGroup()
-- Get the current visual selection
local content = vim.fn.getreg("h")
-- Put the text into the command line
local cmd = ":'<,'>s/\\(" .. content .. "\\)/"
vim.fn.feedkeys(vim.api.nvim_replace_termcodes(cmd, true, false, false))
end
-- Function to be called from Neovim command
function M.SubstituteWithHighlightMakeGroup()
-- Get the current visual selection
local text = get_visual_selection()
text = escape(text) -- Escape the text for regex
-- Put the text into the command line
local cmd = ":%s/\\(" .. text .. "\\)/"
vim.fn.feedkeys(vim.api.nvim_replace_termcodes(cmd, true, false, false))
end
-- Function to substitute with the word under the cursor
function M.SubstituteWithWord()
local word = vim.fn.expand("<cword>")
word = escape(word)
local cmd = ":%s/\\(" .. word .. "\\)/"
vim.fn.feedkeys(vim.api.nvim_replace_termcodes(cmd, true, false, true))
end
-- Function to substitute with the word under the cursor
function M.SearchWithWord()
local word = vim.fn.expand("<cword>")
word = escape(word)
local cmd = "/" .. word .. "<cr>"
vim.fn.feedkeys(vim.api.nvim_replace_termcodes(cmd, true, false, true))
end
-- Function to substitute with the word under the cursor
function M.SearchWithWORD()
local word = vim.fn.expand("<cWORD>")
word = escape(word)
local cmd = "/" .. word .. "<cr>"
vim.fn.feedkeys(vim.api.nvim_replace_termcodes(cmd, true, false, true))
end
-- Function to be called from Neovim command
function M.SearchWithHighlight()
-- Get the current visual selection
local text = get_visual_selection()
text = escape(text) -- Escape the text for regex
-- Put the text into the command line
local cmd = "/" .. text
vim.fn.feedkeys(vim.api.nvim_replace_termcodes(cmd, true, false, false))
end
-- Function to be called from Neovim command
function M.SearchWorkSpaceWithHighlight()
-- Get the current visual selection
local text = get_visual_selection()
text = escapeFzf(text) -- Escape the text for regex
-- Put the text into the command line
local cmd = ":lua require('fzf-lua').live_grep_native({multiprocess=true,search = '" .. text .. "'})<CR>"
vim.fn.feedkeys(vim.api.nvim_replace_termcodes(cmd, true, false, true))
end
return MMappingskeymap("v", "<Leader>rp", ':lua require"utils.search_and_replace".SubstituteWithHighlightMakeGroup()<CR>', opts)
keymap("v", "<Leader>rs", ':lua require"utils.search_and_replace".SaveWithHighlight()<CR>', opts)
keymap(
"v",
"<Leader>rh",
':lua require"utils.search_and_replace".SubstituteWithPreviousHightlightHighlightMakeGroup()<CR>',
opts
)
keymap("n", "<Leader>rp", ':lua require"utils.search_and_replace".SubstituteWithWord()<CR>', opts)
keymap("v", "<Leader>lh", ':lua require"utils.search_and_replace".SearchWithHighlight()<CR>', opts)
keymap("v", "<Leader>lf", ':lua require"utils.search_and_replace".SearchWithHighlight()<CR>', opts)
keymap("n", "<Leader>lw", ':lua require"utils.search_and_replace".SearchWithWord()<CR>', opts)
keymap("n", "<Leader>lW", ':lua require"utils.search_and_replace".SearchWithWORD()<CR>', opts)
keymap("v", "<Leader>lw", ':lua require"utils.search_and_replace".SearchWorkSpaceWithHighlight()<CR>', opts) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing! In the future, please, don't post such long code samples without hiding it under a spoiler (wrap in As per the 'mini.files' setup and persistent bookmarks, the suggested approach is to autocreate them on every explorer start (this can be modified for bookmarks to depend on the current working directory or explorer anchor). There is nothing particularly wrong with persistent bookmarks (in local or global directory), but 'mini.files' doesn't implement that due to extra complexity and security concerns. As for search-and-replace, I've heard good things about MagicDuck/grug-far.nvim. And I think it is more appropriate to post this kind of code in a separate Show and tell discussion. That way it will be more easily searched in the future and not make this discussion (for how users adopt 'mini.nvim' in their config, preferably with links to a public dotfiles repo) more on point. |
Beta Was this translation helpful? Give feedback.
-
|
Ooo apologies. First time sharing so didn't know about that. Yea, I believe I did read that through. At the time I also tried to play with it but persistent bookmarks is quite a big deal to me. I would of thought there's a reason behind what you did so didn't do a pull request or anything :) For my personal reason, it's good enough. Appreciate that! I've tried that one before, always find myself back to the old and classic vim sed way. Roger that! |
Beta Was this translation helpful? Give feedback.
-
|
Loving mini so far, honestly no complaints :) |
Beta Was this translation helpful? Give feedback.
-
|
That's a high praise :) I noticed couple of oddities with 'mini.ai' textobjects:
Also, using both 'fzf-lua' and 'mini.pick' seems redundant. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the pointer on the custom text objects, I'll go back through the specification . I was in a hurry last night (actually early this morning) and I clearly rushed. And that is correct on the redundancy, I will get those both addressed this evening. |
Beta Was this translation helpful? Give feedback.
-
|
Hey! I wanted to share a small experience I had while configuring MiniStarter in Neovim. I customized the header colors and tweaked every detail to better match the overall colorscheme.
MiniStarter:local header = require("config/header")
MiniStarter.setup({
evaluate_single = true,
header = table.concat(header.header.val, "\n"),
footer = function()
local stats = require("lazy").stats()
local ms = (math.floor(stats.startuptime * 100 + 0.5) / 100)
return "⚡ Neovim loaded " .. stats.count .. " plugins in " .. ms .. "ms"
end,
items = {
MiniStarter.sections.pick(),
},
content_hooks = {
-- MiniStarter.gen_hook.adding_bullet(""),
},
})
vim.api.nvim_create_autocmd("User", {
pattern = "MiniStarterOpened",
callback = function(ev)
local ns = vim.api.nvim_create_namespace("MiniStarterOpenedHeader")
if vim.bo.filetype == "ministarter" then
for i, x in ipairs(header.header.opts.hl) do
for _, z in ipairs(x) do
vim.api.nvim_buf_set_extmark(ev.buf, ns, i - 1, z[2], { end_col = z[3] - 1, hl_group = z[1] })
end
end
return
end
vim.api.nvim_buf_clear_namespace(ev.buf, ns, 0, -1)
end,
})
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for sharing! Yeah, 'mini.starter' was (intentionally) not designed to work with colored header and footer out of the box. Glad that you found a way to make it work. Also, I don't think But the most impressive part here is that all 15 plugins load in 0 ms 😄 |
Beta Was this translation helpful? Give feedback.
-
|
@echasnovski Yes, that makes sense. Thanks for pointing it out! 😄 MiniStarter:local header = require("config/header")
local colors_header = function(content, _)
local hl = header.header.opts.hl
local count_index = 1
for z, x in ipairs(header.header.val) do
local group = {}
for char in x:gmatch("[%z\1-\127\194-\244][\128-\191]*") do
if hl[z][count_index] ~= nil then
local hl_group = hl[z][count_index][1]
table.insert(group, { type = "header", string = char, hl = hl_group })
end
count_index = count_index + 1
end
count_index = 1
table.insert(content, z, group)
end
return content
end
MiniStarter.setup({
evaluate_single = true,
header = table.concat(header.header.val, "\n"),
footer = function()
local stats = require("lazy").stats()
local ms = (math.floor(stats.startuptime * 100 + 0.5) / 100)
return "⚡ Neovim loaded " .. stats.count .. " plugins in " .. ms .. "ms"
end,
items = {
MiniStarter.sections.pick(),
},
content_hooks = {
-- MiniStarter.gen_hook.adding_bullet(""),
MiniStarter.gen_hook.aligning("center", "center"),
colors_header,
},
})
yeah haha, I'm not really sure why it says 0 ms, kind of weird 😅. I noticed that when I resize the terminal, the time changed from 0 ms to 126.61 ms. Also, huge thanks for creating mini.nvim. I really love it! :D |
Beta Was this translation helpful? Give feedback.
-
|
I'm enjoying it :D MiniStarter.mp4 |
Beta Was this translation helpful? Give feedback.
-
|
Heya, it's actually my first time switching from vscode to neovim and i were told to use some IDE distro such as NvimChad and lazynvim but i stumbled on this godsend while browsing through lazy's plugin dependencies. And i'm loving it so far 💕 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for kind words! Hope, you'll keep enjoying to use 'mini.nvim' :) Couple of things I noticed after quick glance:
|
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the insights. I will be completely honest with you; i don't understand the later() and now() functions that much. It'd be fantasic if you can explain to me more about them. Things like what are the |
Beta Was this translation helpful? Give feedback.
-
This pretty much sums it up.
Using Hope this makes sense. |
Beta Was this translation helpful? Give feedback.
-
|
Ah i think i get it now more or less. Thank you again for this awesome collection. I really enjoy almost all your modules, only a few either i haven't tried yet or just don't feel completed but i do have high hopes for them. Looking foward soon ! And more importantly stay safe bro |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
Seeing how other people use
mini.nvimis a very helpful feedback for me. It helps me reason about which modules are used the most and whatconfigvalues are used. This might influence my future decisions in design and default values. And also might other people new ideas.Feel free to share a link to specific part of dotfiles (might be a good idea to pin to specific commit), code or screenshot (if too big, please hide under spoiler).
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions