Enhance Kickstart.nvim UX with Buffer Completions, Options, and Autocommands #1642
Conversation
| @@ -184,6 +190,9 @@ vim.keymap.set('n', '<leader>q', vim.diagnostic.setloclist, { desc = 'Open diagn | |||
| -- or just use <C-\><C-n> to exit terminal mode | |||
| vim.keymap.set('t', '<Esc><Esc>', '<C-\\><C-n>', { desc = 'Exit terminal mode' }) | |||
|
|
|||
| -- Close current buffer | |||
| vim.keymap.set('n', '<leader>Q', ':bd<CR>', { desc = 'Close current buffer' }) | |||
There was a problem hiding this comment.
IMO this is not very useful because <C-w>q (which quits the window instead of the buffer) serves the purpose of closing splits, If I need to actually close buffers I usually use <M-d> inside of Telescope's buffers picker.
What do you think?
There was a problem hiding this comment.
Thanks for the feedback, I agree that <C-w>q and Telescope's buffer picker are good ways to manage windows and buffers in advanced workflows.
However, since Kickstart.nvim is primarily aimed at users new to Neovim, I think keeping the <leader>Q mapping for :bd is a good idea. as for many beginners, "closing a file" intuitively means closing the buffer, not just the window.
init.lua
Outdated
| -- disable automatic comment on newline | ||
| -- vim.api.nvim_create_autocmd('FileType', { | ||
| -- desc = 'Disable automatic comment on newline', | ||
| -- group = vim.api.nvim_create_augroup('kickstart-disable-auto-comment', { clear = true }), | ||
| -- pattern = '*', | ||
| -- callback = function() | ||
| -- vim.opt_local.formatoptions:remove { 'c', 'r', 'o' } | ||
| -- end, | ||
| -- }) | ||
|
|
There was a problem hiding this comment.
IMO this might be too niche
There was a problem hiding this comment.
That's a fair point. My goal with adding these autocommands was to give users a better idea of what's possible with them, as the original repo only included just one example.
If you still think it's too much to add to init.lua, I can make a new file with these autocommands, plus some other useful ones, and add it to lua/kickstart/autocmds.lua or a similar location. That way, users could still have them as examples.
What do you think?
|
Thanks for the feedback, I really appreciate you guys taking the time to review everything 🙏. I'm still pretty new to Lua and Neovim myself, so I'm learning a lot as I go. Apologies if this PR has caused any headaches – I definitely don't want to make extra work for y'all 😅😅. |
This pull request aims to enhances the
kickstart.nvimconfiguration by integrating features that directly improve user experience, with a core focus on session persistence, efficient navigation, and smarter completion functionality. The changes meticulously maintain the project's foundational minimal and extensible philosophy.Detailed Changes
⚙️ Options
vim.opt.undofile = true: Enables persistent undo history across Neovim sessions. This enhancement allows users to undo and redo changes even after closing and reopening files, boosting productivity and safety.vim.opt.smoothscroll = true: Activates smooth, line-by-line scrolling (requires Neovim 0.10+). This visual improvement enhances readability and navigation, especially within large files and when traversing completion menus.vim.opt.colorcolumn = '100': This option is intentionally commented out. If uncommented, it would visually highlight column 100 to indicate a preferred maximum line length, but it remains disabled to uphold the configuration's minimalist design principle.⌨️ Keymaps
<leader>Qmapping: Introduces a convenient, quick shortcut to close the current buffer (:bd<CR>). This streamlines buffer management and improves workflow efficiency.🔄 Autocommands
TextYankPost: Enhanced by addingtimeout = 200. This modification effectively limits the duration of the yank highlight, reducing visual distraction. Furthermore, the explicittimeoutvalue offers users a clear point of customization to increase or decrease the highlight duration based on their personal preference, promoting a more tailored experience.BufReadPost: Implements an autocommand to restore the cursor position on file open (pattern = '*'). This ensures session continuity improves user experience by returning users directly to their last editing location across all file types.BufWritePre: Automatically creates any missing parent directories when saving a file. This eliminates a common friction point, improving usability when creating new files with nested paths.FileType: This autocommand, if enabled, would disable automatic comment continuation for all filetypes. It remains commented out, offering users the flexibility to enable or disable it based on their specific coding conventions and preferences.💡
blink.cmpConfigurationbuffersource intosources.default: This addition toblink.cmpprovides relevant word completions directly from currently open buffers. The source is further refined with a filter restricting completions to user-chosen filetypes, currently pre-configured for markdown and text files.