mhinz / mhinz/vim-startify

:bd does not close the current tab when using Startify

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

Nobody has claimed this yet.

Dominant language
Vim Script
Stars
5.4k
Forks
181
PR merge metrics
No merged PRs in 30d

Description

Description

Hi, I found a possible issue related to tab behavior when Startify is installed.

Steps to reproduce:

Open Vim.

Startify appears in the first tab.

Create a second tab:
:tabnew

Open any file in the second tab.

In the second tab, run:
:bd

Expected behavior (normal Vim behavior):

If a tab contains only one window and its only buffer is deleted with :bd,
Vim should automatically close that tab.

Actual behavior (with Startify installed):

After running :bd, the file buffer is closed,
but the tab does not close.

Instead, the tab switches to a Startify buffer,
so the tab never becomes empty.
Therefore Vim will not close the tab automatically.

This does not happen in a clean Vim environment without Startify.
It seems that Startify’s buffer becomes a fallback buffer, preventing Vim from closing the tab.

Environment:

Vim version: 9.1.1825

Startify version: latest

OS: Windows 11

Additional notes:

I expect :bd to close the tab when it becomes empty, just like default Vim behavior.
But Startify keeps a buffer available inside the tab, so the tab never closes.

Could this be a bug or unintended behavior?

Thank you!

Contributor guide

Open the contributing guide

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.

Research direction

Reproduce the behavior in Vim with Startify installed by opening a second tab, editing a file, and running :bd; compare it with a clean Vim environment. Trace the Startify fallback-buffer behavior and confirm that the finished change lets :bd close a tab containing only that buffer, without regressing the startup screen.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.