Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workspace loading #230

Open
joselevelsup opened this issue Jul 10, 2019 · 9 comments
Open

Workspace loading #230

joselevelsup opened this issue Jul 10, 2019 · 9 comments

Comments

@joselevelsup
Copy link

Describe the bug
I can't properly save the files I am using in my workspace. Everytime I save, close, then load my workspace, the initial file I last left off on, does not load properly. Then if I choose another file from the buffer list, its like a 50/50 chance of it loading my work.

To Reproduce
Steps to reproduce the behavior:

  1. Open a bunch of buffers
  2. Save workspace
  3. Close Neovim or Vim (I use Neovim)
  4. Open Neovim or Vim
  5. Load workspace
  6. See the buffers you last left off on or most of the buffers, not show up

Expected behavior
It should load my buffers properly and I can continue my work

Version(s) (please complete the following information):

  • OS: OSX Mojave 10.14.5
  • Version nvim 0.3.7
@cometsong
Copy link
Member

Hi @joselevelsup
Will you please run [n]vim in 'verbose' mode so we can cehck what's happening in the background?
vim -Vverbose-cs-workspace-vim.log
and/or
nvim -Vverbose-cs-workspace-nvim.log

@joselevelsup
Copy link
Author

Screen Shot 2019-08-12 at 2 03 45 PM

So everytime I load my workspace, this happens.

@joselevelsup
Copy link
Author

I'll do the verbose when I can. but so you can see something

@joselevelsup
Copy link
Author

verbose-cs-workspace-nvim.log

here is the log. Hope it helps.

@cometsong
Copy link
Member

Eww, that's yucky vim output.
Will you please send your [.]cs_workspaces file also?
Plus, where is the project root for this workspace?

Are you saving/loading the project within a [git|svn|etc] repository or in a "normal" folder?
i.e. is the 'fastinventory' in some "version control"?

@joselevelsup
Copy link
Author

The project is loaded within a git repo.

@joselevelsup
Copy link
Author

verbose-cs-workspace-nvim.log

here is another log in case the first one doesn't help.

@cometsong
Copy link
Member

Ok, let's take the next step on troubleshooting this.
Let's minimize your nvim/init.vim config to just this:

filetype plugin on
call plug#begin('~/.config/nvim/plugged')
Plug 'vim-ctrlspace/vim-ctrlspace'
call plug#end()
set hidden

Of course setting those folders as you like.
You can move the whole ~/.config/nvim/ dir to another location for easier restoring from backup afterward.

Then try loading the one you've already saved.
If same issue, then:

  • in a new nvim session (with -Vlogfile)
  • open a few files from relative and absolute directories
  • save a new workspace
  • quit nvim, reopen (with -Vlogfile2 again)
  • load ctrlspace workspace
  • quit
  • send over the cs_workspaces file and the verbose logs.

(I'm crossing my fingers this works, because then we know it's some interaction with one of your other plugins; we can track it down and work out the details that way.)

@Konfekt
Copy link
Collaborator

Konfekt commented May 10, 2020

Please check whether #268 aleviates these issues.

@jyscao jyscao added bug: disruption causes workflow disruption priority: 2 - low and removed neo labels Nov 10, 2020
Konfekt added a commit to Konfekt/vim-ctrlspace that referenced this issue Mar 27, 2021
See neovim/neovim@69fc6c2

Addresses issues

- vim-ctrlspace#293
- vim-ctrlspace#290: same label problem and the latest similar issue, but without the problem of the buffer links missing, and no news since early Feb
- vim-ctrlspace#264: very short thread redirecting other toward issues
- vim-ctrlspace#238: similar, old, unsolved
- vim-ctrlspace#230: similar, interesting, unsolved, old
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants