tpope / tpope/vim-obsession

Just a question about how you guys handle swap files

Open
#18 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

You see, my Macbook likes to freeze a lot. It's not enough to warrant me to be really upset (for more than a few minutes when it happens, as it averages once every 2 weeks) but it's enough that it gives me reason to set up a plugin such as this one.

Now what happens when I go and re-open with vim -S after my machine dies is that I get a flood of "What should I do with your swap file".

How do you guys deal with this? I find that I usually try to mash D, but this is not really ideal for the reason that if I keep pressing D I will eventually start to erase lines from some buffers.

If I don't mash D, say I Recover with R, I am re-presented with the prompt the next time because Vim is just so nice/dumb. Not to mention R will lead me to replace some letter in some buffer with the r character.

The other obvious reason why mashing D sucks is that I'm just actually choosing to throw away any unsaved buffers.

Honestly this wouldnt be problematic if my goddamned fruit machine will just stop freezing up.

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

This issue names no project file, test, or implementation entry point; it asks how Vim swap-file prompts behave after reopening with vim -S. Start by checking whether the plugin documents this workflow, and consider the issue resolved only if a clear, safe handling explanation is available.

Written by the indexing model from the issue text.

Assessment

Tech stack
vim
Domain
tooling
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.