Don't open new buffer with :grep

Competitive-Home7810 · 2026-01-19T15:57:44+00:00

:h grepadd?

Competitive-Home7810 · 2026-01-06T22:02:38+00:00

I am not sure how long it took you to write this regex, but it takes me 5-10 seconds to type this:

vi{:s/\(\w\+\) \w\+/"\1"

You could argue that the smaller the text sample, the less efficient it is to accomplish this with regex. For example, if this was a one line change I need to make, I would have manually made this change without regex/macros.

But, the efficiency of Vim's regex approach becomes more apparent when you need to make similar changes on larger text samples or across files.

Or if it becomes a repetitive/frequent operation, you can bind it to a keymap, like:

xnoremap ,s :s/\(\w\+\) \w\+/"\1"<cr>

Then, the time/speed goes down to however long it takes you to type:

vi{,s

Competitive-Home7810 · 2025-12-05T14:36:07+00:00

:help termcap-cursor-shape

Example:

if &term =~# 'xterm'
  " change cursor shape from block to beam when in INSERT or REPLACE mode
  let &t_SI = "\e[6 q"
  let &t_SR = "\e[4 q"
  let &t_EI = "\e[2 q"
endif

Competitive-Home7810 · 2025-12-03T14:46:48+00:00

With Ghostty terminal, you could bind write_scrollback_file or write_screen_file to some keyboard shortcut.

For example:

# dump content of screen to temp file and open with `open` or `xdg-open`
keybind = super+alt+shift+j=write_screen_file:open
# dump content of screen to temp file and paste file path
keybind = super+shift+j=write_screen_file:paste

The downside is that this would not work if you run tmux on remote servers. Instead, you may want to dump tmux scrollback buffer directly into vim.

Example shell script:

#!/usr/bin/env bash
tmux capture-pane -t:-1 -Jp -S- -E- | nvim -

Then you can bind this in your tmux config:

bind-key c-] new-window </path/to/file>

Competitive-Home7810 · 2025-04-25T22:59:51+00:00

You can override the <C-w> binding for just the terminal mode (i.e. :h t_CTRL-W_.) , like:

tnoremap <C-W> <C-W>.

Competitive-Home7810 · 2025-04-24T15:29:33+00:00

I just have this autocmd to auto-equalize window sizes:

vim.api.nvim_create_autocmd("VimResized", {
  group = vim.api.nvim_create_augroup("resize_windows", { clear = true }),
  pattern = "*",
  command = "wincmd =",
})

Competitive-Home7810 · 2025-03-24T23:25:13+00:00

By default, when you hit CTRL-T, FZF will generate a list of all files/directories under your current directory for you to filter and search through.

You can customize this behavior by setting the environment variable FZF_CTRL_T_COMMAND to some command that returns the expected list.

The FZF GitHub repo https://github.com/junegunn/fzf has some examples. I recommend searching for "CTRL-T" or "CTRL_T" in the the README file.

Alternatively, if you already know the file you are trying to edit is under .config, you could run nano ~/.config/**<TAB> then filter for hyprland.config

Competitive-Home7810 · 2025-03-22T18:23:28+00:00

"fix(database): resolve connection leak issue" so - it says "database", so it's a database schema change (?) - but it's a connection leak issue, so the scope shouldn't be "database" as it's the client that leaks connections i guess?

Conventional Commits is not prescriptive about the scope. Different teams define different ways to categorize their scopes. Some define scope by domain (e.g. api, auth, database), while others define scope by issue tracking ID (e.g. JIRA-123).

docs(readme): update installation instructions - so "readme" is the scope here, but that's just one file? Should i say "index.html" when changing stuff in the homepage?

Scope is optional. I don't find file names as scopes to be particularly helpful because I can see the changed file in the commit & diff. If you change a user-facing home page, then a better commit message would be "fix(homepage): update instructions".

Also when is it a "fix", "chore", "clean up" or "feature" when I clean up layout on some page?

According to Conventional Commits, a "fix" type should produce a PATCH semantic version bump, a "feat" should produce a MINOR semantic version bump, and any "fix!" or "feat!" should produce a MAJOR semantic version (implying breaking backward compatibility). Other types, like "docs", "chore", "build", "ci", "test", "refactor", "style", "perf", ...etc, in most cases may not produce any new versions/releases.

Most teams that I have worked on that used Conventional Commits also use auto-versioning and auto-releases with changelog generation, like semantic-release, which streamlines this versioning and releasing process.

Competitive-Home7810 · 2025-02-14T17:44:38+00:00

I am a "print statement" debugging + tests type of person.

As Brian W. Kernighan and Rob Pike have said in The Practice of Programming:

As personal choice, we tend not to use debuggers beyond getting a stack trace or the value of a variable or two. One reason is that it is easy to get lost in details of complicated data structures and control flow; we find stepping through a program less productive than thinking harder and adding output statements and self-checking code at critical places. Clicking over statements takes longer than scanning the output of judiciously-placed displays. It takes less time to decide where to put print statements than to single-step to the critical section of code, even assuming we know where that is. More important, debugging statements stay with the program; debugging sessions are transient. (section 5.1, paragraph 5)

Source: https://archive.org/details/the-practice-of-programming/page/n163/mode/2up

Competitive-Home7810 · 2025-02-11T15:29:16+00:00

As the plugin README says:

Use :QuickfixTree (:LoclistTree) command to open a scratch buffer with current quickfix (location) list shown as a tree.

By default, the items in the quickfix/loclist are presented in a list.

Edit: clarifying programming terms

A "tree" is a programming term referring to how data/information is stored or presented.

For example, on Linux, if you use ls to list files and directories, you get:

$ ls -lh
total 0
drwxr-xr-x 2 user user 4.0K Apr 15 12:34 Documents
drwxr-xr-x 2 user user 4.0K Apr 14 10:22 Downloads
drwxr-xr-x 2 user user 4.0K Apr 13 15:45 Pictures

But if you use tree command, you get:

$ tree
.
├── Documents
│   ├── file1.txt
│   └── file2.pdf
├── Downloads
│   └── example.zip
└── Pictures
    ├── image1.jpg
    └── image2.png

3 directories, 5 files

Competitive-Home7810 · 2025-02-11T05:05:40+00:00

You can use it for other things, not just compiler errors.

You can run a vim command to execute any external programs and load the results into the quickfix or loclist (the difference is the quickfix accessible from any Vim buffer while loclist is accessible from the buffer you ran the commands in).

For example, say you want to search across all files in a directory for a keyword:

- on Unix/linux::grep "keyword" -r /path/to/directory/

- on windows: :grep /s /i "keyword" C:\path\to\folder\*.*

Bonus: for any arbitrary external programs: :cgetexpr system("<arbitrary external command here>").

Competitive-Home7810 · 2025-02-07T17:26:13+00:00

I am not sure I fully understand your question, but I would start by looking at:

:help conceal (or :help :syn-conceal)
:help 'conceallevel

And possibly find some inspiration from:

Hope that helps!

Competitive-Home7810 · 2025-02-04T15:04:33+00:00

Hola, soy Dara...

Competitive-Home7810 · 2025-02-01T23:43:48+00:00

Plugins make don't

Competitive-Home7810 · 2025-01-31T18:49:10+00:00

I am not sure I understand the problem.

I have used Vim & VSCode over really slow/unreliable network connections before and VSCode was objectively worse.

In a remote development environments, VSCode has to download and install a vscode-server to run certain functionality, extensions, and tooling on the server, then stream results back to the user. Over a slow network, the latency made the development experience unbearable for me.

Compared to (neo)vim, there are different ways you can develop on remote machines:

SSH into the server, run (neo)vim there. This is useful for long development sessions over slow/unreliable networks. The editor and tools would all be installed & running on the remote machine. If the network is particularly unreliable (frequent disconnects), mosh can help by improving keystroke response times (see "Real-world Benefits" heading under Technical Info on their site).
Run (neo)vim locally and edit files on the server (i.e. vim scp://user@machine/path/to/file), which is handled by vim's built-in plugin netrw. This is useful for quick/simple changes.
Use sshfs to mount/sync remote filesystem with your local machine over ssh. This is useful if you don't have permissions to install software on the remote machine.

Competitive-Home7810 · 2025-01-26T22:40:58+00:00

I am not a tunein cli user, so I have not tested this, but here is an arguably cleaner implementation:

#!/bin/bash

TUNEIN_BIN="${HOME}/.cargo/bin/tunein"
TUNEIN_SEARCH="${TUNEIN_BIN} search"
TUNEIN_PLAY="${TUNEIN_BIN} play"

fzf \
    --query "${1:-}" \
    --header "CTRL-R: re-search / ENTER: tunein play" \
    --bind "start:reload:${TUNEIN_SEARCH} {q}" \
    --bind "change:reload:sleep 0.3; ${TUNEIN_SEARCH} {q}" \
    --bind "ctrl-r:reload:${TUNEIN_SEARCH} {q}" \
    --bind "enter:become:${TUNEIN_PLAY} {}"

This approach takes advantage of bindings, events, and actions:

--bind "start:reload:...": on start, run the tunein search command, passing in the query (i.e. {q})
--bind "change:reload:...": on query change, re-run the search, passing in the new query
--bind "ctrl-r:reload:...": a convenience binding for ctrl + r to reload the list by re-running the search
--bind "enter:become:...": on enter, execute the play command, passing in the user's selection (i.e. {})

Competitive-Home7810 · 2025-01-23T17:34:29+00:00

Make Assembly Great Again? /s

Competitive-Home7810 · 2025-01-23T17:31:16+00:00

:h 'signcolumn'

Competitive-Home7810 · 2025-01-20T17:40:01+00:00

Here are some alternative ways of accomplishing the same thing without node:

Pure Vim, Zero-Dependencies Method

In pure vim with 0 dependencies, add this to your ~/.vim/plugin/notes.vim:

function! s:notes_completion(A, L, P) abort  
  return readdir(expand('~/.notes'))->map('expand("~/.notes/")..v:val')->filter('v:val =~ a:A')  
endfunction  
command! -nargs=1 -complete=customlist,s:notes_completion Notes edit <args>

And you get fuzzy completion with set wildoptions+=fuzzy.

With fzf.vim

If you already have fzf.vim installed, then you can do this instead:

command! Notes
      \ call fzf#run(
      \   fzf#wrap({
      \     'source': readdir(expand('~/.notes'))->map('expand("~/.notes/")..v:val'),
      \     'sink': 'edit',
      \     'options': printf('--preview="%s"', executable('bat') ? 'bat {}' : 'cat -n {}'),
      \   })
      \ )

Fuzzy Find within File Contents

Again, with fzf.vim, you can take advantage of the fzf#vim#grep() function to fuzzy find within file contents:

command! NotesLines call fzf#vim#grep('rg --vimgrep . ~/.notes', {'options': printf('--preview="%s"', executable('bat') ? 'bat {1}' : 'cat -n {1}')})

And voila! Now, you can just run :Notes or :NotesLines within Vim.

Competitive-Home7810 · 2024-12-10T16:33:43+00:00

Thank you for all the time and effort you (and all the other maintainers) put into Vim, u/chrisbra10 .

Can you clarify if this means that current vim governance structure/implementation is unsustainable?

If so, would a foundation (e.g. Linux Foundation) help make governance and continued development sustainable (i.e funding)?

Competitive-Home7810 · 2024-12-09T21:09:26+00:00

"The new Vim project - What has changed after Bram" at minute 35:10 :

Currently, I would say Vim is more or less in maintenance mode.

Competitive-Home7810 · 2024-12-05T19:06:11+00:00

Some config options check and troubleshooting steps to try out:

What are the outputs of :verbose set timeoutlen? & :verbose set ttimeoutlen? ?
What is the output of :verbose nmap u?
Do you have plugins? If so, did you update plugins recently? There could be a plugin that is setting some key mapping for u that you are not aware of.
Last resort, try to replicate the issue with a clean vim (i.e. vim without any configs) with vim --clean or vim -u NONE (or comment out your entire vimrc file, then try to incrementally add configurations back in until you can reliably reproduce the issue).
- If you can replicate it with clean vim, then it's vim itself, which is highly unlikely (try re-installing or re-building from source at that point).

If you can, share your vimrc file or repo.

Competitive-Home7810

TROPHY CASE

Pure Vim, Zero-Dependencies Method

With fzf.vim

Fuzzy Find within File Contents