How do I paste the current Git commit hash directly from Vim using the expression register?

Q: How do I paste the current Git commit hash directly from Vim using the expression register?

`"=system('git rev-parse --short HEAD')->trim() p` If you frequently write commit references in notes, code comments, or release docs, you can avoid shell context switches and paste the hash straight from Vim. The expression register evaluates Vimscript on demand, so you can run a shell command, clean its output, and insert it in one sequence. This is fast in review/debug workflows where you need a precise revision ID repeatedly. ## How it works ```vim "=system('git rev-parse --short HEAD')->trim() p ``` - `"=` opens the **expression register** prompt - `system('git rev-parse --short HEAD')` runs Git and captures stdout - `->trim()` removes the trailing newline from shell output - ` ` confirms the expression and stores the result in the expression register - `p` puts the resulting text after the cursor ## Example Before: ```text Investigated regression in parser, fixed in commit: [cursor] ``` After (example hash): ```text Investigated regression in parser, fixed in commit: a1b2c3d ``` ## Tips - Use `P` instead of `p` when you want insertion before the cursor - The same pattern works for other dynamic values, for example branch names (`git branch --show-current`) - If the current file is not in a Git repo, the command returns an error string; run it only in repository buffers

Question

Accepted Answer

`"=system('git rev-parse --short HEAD')->trim()p` If you frequently write commit references in notes, code comments, or release docs, you can avoid shell context switches and paste the hash straight from Vim. The expression register evaluates Vimscript on demand, so you can run a shell command, clean its output, and insert it in one sequence. This is fast in review/debug workflows where you need a precise revision ID repeatedly. ## How it works ```vim "=system('git rev-parse --short HEAD')->trim()p ``` - `"=` opens the **expression register** prompt - `system('git rev-parse --short HEAD')` runs Git and captures stdout - `->trim()` removes the trailing newline from shell output - `` confirms the expression and stores the result in the expression register - `p` puts the resulting text after the cursor ## Example Before: ```text Investigated regression in parser, fixed in commit: [cursor] ``` After (example hash): ```text Investigated regression in parser, fixed in commit: a1b2c3d ``` ## Tips - Use `P` instead of `p` when you want insertion before the cursor - The same pattern works for other dynamic values, for example branch names (`git branch --show-current`) - If the current file is not in a Git repo, the command returns an error string; run it only in repository buffers

Answer

Explanation

How it works

Example

Tips

Related Tricks

How do I append the current line to a register from command line without using yank?

How do I put a register as true line list so embedded newlines stay split correctly?

How do I inspect a macro register with escaped control characters so I can debug it safely?

How do I capture command-line output directly into a register?

How do the numbered delete registers work and why does deleted text rotate through registers 1 through 9?