tpope / tpope/vim-obsession

[ Bug ] cmdheight after restore is incorrect

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

Nobody has claimed this yet.

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

Description

I have issue with NVIM v0.9.4 and use('tpope/vim-obsession').

I have vim.opt.cmdheight = 2 at 41 line in set.lua and if I open nvim with nvim -S -V9nvimlog to restore session from Session.vim and save log file.
In log file I found:

  cmdheight=1
	Last set from ~/config_repo/nvim/lua/pronvis/set.lua line 41

which is weird...
However if I open nvim with just nvim (without restoring session) then cmdheight value is 2 like in my config file.

link to my comment on similar issue: https://github.com/rmagatti/auto-session/issues/64#issuecomment-1870672047

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

Start with the reported configuration in set.lua at line 41, the generated Session.vim, and the -V9nvimlog output. Reproduce both a normal launch and nvim -S session restore, then compare when cmdheight is set and restored. Done means identifying why the restored value is 1 instead of the configured 2 and confirming the corrected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.