tpope / tpope/vim-obsession

Obsession not work automatically when attached to a existing session.

Open
#56 4 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

Hi Tim!

When I open a session and do changes and then pause Obsession it doesnt seem to save anything. This can be tested by opening the session after layout changes.

But when I use :Obsession command twice so it says that it stops and track again.. and do some changes and then :Obsession to pause.. it actually saves the changes such as layout etc.

I use

:source ~/.config/nvim/sessions/test

to open the session up.

Not sure how to get logs for this behaviour.

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 by sourcing ~/.config/nvim/sessions/test, making layout changes, and pausing Obsession, then compare it with starting tracking via :Obsession twice. Begin at the :Obsession command and session-tracking behavior; done means changes made after opening an existing session are saved when tracking is paused.

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
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.