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

Async element load for part that will be update later

Open
#492 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
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
lua
Domain
cli

Research direction

Start by examining the dashboard element API and the rendering paths for elements such as the logo and footer. The request mentions vim.api.nvim_buf_set_lines and needs asynchronous updates that preserve the dashboard theme and survive window resizing. Done would be a documented callback or update API, or an example implementation, with the requested element remaining correctly rendered after updates and resizing.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
I'm making a dashboard that will call an LLM to generate some random fact every time i open up nvim, but there doesn't seem to be a way to add a callback for later update. Since waiting for the LLM to response will take about 3-4 seconds and the whole dashboard will be block from loading.

Describe the solution you'd like
An example implementation or an expose api of some kind to update the dashboard asynchronously like logo, footer,...

Additional context
Dashboard with random fact:
image

Dashboard while loading:
image

I try to inject asynchronously into the buffer using vim.api.nvim_buf_set_lines but it doesn't follow the theme of the dashboard and the actual fact will disappear for any changes of the window size.
image

Any suggestion appreciated since i'm still new as this and wonder if this is even possible.

Dominant language
Lua
Stars
2.9k
Forks
201
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 nvimdev/dashboard-nvim

All issues in nvimdev/dashboard-nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.