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

Consider making the max width / height of infoviews work via percentages of real estate rather than columns/rows

Open
#315 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua, neovim
Domain
frontend

Research direction

Start with demos/basic.tape, especially its narrow-screen dimensions, and trace the infoview sizing configuration in the Neovim plugin. Compare the current column/row limits with the proposed percentage-based behavior; done means the sizing can support percentage-based limits and the default no longer consumes an unnecessary half of a narrow screen.

Written by the indexing model from the issue text.

Description

enhancement infoview

For narrow screens -- such as the one used for the demo script (especially with even smaller dimensions) -- the infoview even at max width can seem to take up a full half of the available space, which is unnecessary.

It might be better if this max width was a percentage of the available columns, and then we set it to 1/3 or something.

This may really be about making both possible (a la CSS) to configure, and then changing the default to percentage-based.

Dominant language
Lua
Stars
607
Forks
63
Avg merge
1d 8h
Merged PRs (30d)
8

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.