keymap in config file to insert text at top of file

[wf5w]

For years I have had a key binding to insert #!/usr/bin/env xxx at the top of a file, and then restore my position.

FYI: hx is the binary in my PATH, for the helix editor

This I have tried:

[keys.normal]
"C-S-p" = [
"save_selection",
":sh echo '#/usr/bin/env python' | hx --clipboard-provider",
"goto_file_start",
"open_above",
"normal_mode",
"paste_before",
"jump_backward"
]

I get all kinds of errors.

Can anyone help? Thanks.

[weuderr]

Two things are going on in your attempt:

• hx --clipboard-provider isn't a CLI flag, and :sh only shows the output in a popup. It doesn't put it in the clipboard. That's where the errors come from.
• Also, the shebang is missing the ! (#/usr/bin/env → #!/usr/bin/env).

You don't need the clipboard at all. :insert-output runs a shell command and inserts its output before each selection:

[keys.normal]
"C-S-p" = [
  "save_selection",
  "goto_file_start",
  "extend_to_line_bounds",
  ":insert-output echo '#!/usr/bin/env python'",
  "collapse_selection",
  "jump_backward",
]

Why extend_to_line_bounds is there: in shell() (helix-term/src/commands.rs), Helix strips the trailing newline from the command output when the selection doesn't end with \n. With only goto_file_start, the selection is the first character, so the newline gets dropped and the shebang is glued onto your first line. Selecting the whole first line keeps the \n, so the shebang lands on its own line above it.

jump_backward then takes you back to where you were. Jumplist positions are mapped through the edit, so you return to the same spot, one line lower.

One caveat: whether C-S-p is distinguishable from C-p depends on your terminal. It needs one that supports the kitty keyboard protocol (kitty, WezTerm, foot, Ghostty…). If it doesn't fire, try a different chord like "space" = { "!" = [...] } to test.

[wf5w]

looked good. exactly what I wanted.

Alas, this still produces errors.

Jerry

[weuderr]

Glad the approach fits! Could you paste the exact error (and hx --version)? My guess is the shell part: on Helix older than 25.01, the old argument parser drops the quotes around '#!/usr/bin/env python', so sh sees # as the start of a comment and things break.

Here's a version that avoids the shell entirely. It's a macro keybinding (Helix 25.01+), which replays plain keys:

[keys.normal]
"C-S-p" = "@<C-s>ggO#!/usr/bin/env<space>python<esc><C-o>"

Step by step: <C-s> saves the selection to the jumplist, gg goes to the file start, O opens a line above, the shebang is typed in, <esc> returns to normal mode, and <C-o> jumps back to where you were.

(Macro bindings can't be mixed into a [...] command list, so it has to be a single string like above.)

If it still errors, the error text will tell us whether it's the config parse or the key itself. C-S-p needs a terminal that supports the kitty keyboard protocol to be distinguished from C-p.

[wf5w]

versions:

hx --version is 25.07.1 appimage
using wezterm 20260906-101927-d2f3f05b

your way worked.

btw how do I insert a after the python. or should i do this:
... pythongho

jerry

[weuderr]

Great, glad it works! 🎉

The Enter key is <ret> in macros. Since you're still in insert mode after typing the shebang, just add it before <esc>:

[keys.normal]
"C-S-p" = "@<C-s>ggO#!/usr/bin/env<space>python<ret><esc><C-o>"

That gives you the shebang plus an empty line below it. <C-o> still brings you back to where you were.

Your <esc>gho idea isn't wrong, but <ret> is simpler: it stays in insert mode, with no extra motions.