Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Provide option to unbind default <Tab> and <CR> bindings for abbreviation expansion

Open
#355 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua, vim

Research direction

Start by reading the abbreviation setup around require("lua.abbreviations").convert() and trace how config.abbreviations currently installs the and bindings. Compare the proposed keymaps or mappings options and verify that abbreviations still work through explicitly mapped keys while the default bindings can be disabled.

Written by the indexing model from the issue text.

Description

enhancement

Hello!

I'm a big fan of the plugin and have been using it for class.

I would like the option to unbind <Tab> and <CR> from expanding abbreviations, without also disabling abbreviations entirely. If someone (like me) has an insane personal preference for using keys other than <Tab> and <CR> for completion, it can be annoying to hit <Tab> for indenting the line and then get an expansion instead.

It is currently easy to map another key to expand abbreviations, using the require("lua.abbreviations").convert() function. I believe it would also be nice to either:

  1. Allow for keymaps = false in config.abbreviations in order to not bind <Tab> and <CR>, or
  2. Allow for config.mappings = false to remove those bindings.

Thank you -- your plugin has really saved my butt in my Formal Methods class becuase now I don't need to leave Neovim to do my coursework!

Dominant language
Lua
Stars
607
Forks
63
Avg merge
3d 14h
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Julian/lean.nvim

All issues in Julian/lean.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.