Sorry, for the first point: when I use ":bd! NoOfBuffer", it is not listed yet. So bd is working well.
Le dim. 17 févr. 2019 à 18:32, Salman Halim <[email protected]> a écrit : > > > > On Sun, Feb 17, 2019, 11:54 <[email protected] wrote: > >> Le dimanche 17 février 2019 14:52:20 UTC+1, Salman Halim a écrit : >> >> > After the "bd!", does listing buffers again confirm that it's gone? >> > >> no. >> > > Ah, so the session and autocommand aren't to blame. If you call "bd!" and > the buffer is still there, then maybe bufwipe or something needs to be > checked? > > > >> > Have you examined the contents and timestamp of the session file to see >> if it contains the details of that buffer? >> > >> timestamp is good at vim leaving and it contains infos of that buffer : >> >> let SessionLoad = 1 >> if &cp | set nocp | endif >> let s:so_save = &so | let s:siso_save = &siso | set so=0 siso=0 >> let v:this_session=expand("<sfile>:p") >> silent only >> if expand('%') == '' && !&modified && line('$') <= 1 && getline(1) == '' >> let s:wipebuf = bufnr('%') >> endif >> set shortmess=aoO >> argglobal >> %argdel >> $argadd ~/Desktop/thatbuffer.txt >> winpos 278 74 >> > > It seems as if the session process isn't at fault here, but the buffer > wiping is. > > The call to winpos seems to indicate that the buffer is still open in an > active window? That's not consistent with a deleted buffer. > > >> > >> > How about disabling the autocommand and manually saving the session? >> > >> I don't want to lose interest of autocmd but I can try. >> > > I was trying to isolate the three different variables: buffer delete, > autocommand and session making. > > > >> > Anything in your session options or viminfo that might be contributing >> something? >> > >> just classical set sessionoptions=help,winsize,winpos >> > > Yeah, that's innocuous. I was wondering whether viminfo might have > something to do, but based on your session snippet above, it's clearly not > viminfo. > > Salman > >> -- > -- > You received this message from the "vim_use" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to a topic in the > Google Groups "vim_use" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/vim_use/DuaO_Sj9hg4/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
