LStinson
commented
10 years ago That is a long standing bug that I have not been able to fix yet. When buffers are closed it's a bit complex what happens and I have not figured it all out yet. I'm hoping to get it fixed when my work load lessens. Sorry.
On Thu, Nov 21, 2013 at 9:58 PM, Dmitriy notifications@github.com wrote:
Got to go through my vimrc and plugins and found out the long-bugging thing for me is caused by TagmaBufMgr plugin. (moved out other plugins from my bundler folder and deleted all my vimrc contents - only the plugin makes the change)
Why is there an unnamed buffer created when deleting a current one and can I change this behavior?
If it's not a defined behavior, let me explain.
It goes like this: [1:buffer1&][2:buffer2!] when i run a :bd, it goes like this: [1:buffer1&][4:No_Name!]
Willing to find out about this more [image: :wink:]
Cheers!
— Reply to this email directly or view it on GitHubhttps://github.com/JessicaKMcIntosh/TagmaBufMgr/issues/11 .
Got to go through my vimrc and plugins and found out the long-bugging thing for me is caused by TagmaBufMgr plugin. (moved out other plugins from my bundler folder and deleted all my vimrc contents - only the plugin makes the change)
Why is there an unnamed buffer created when deleting a current one and can I change this behavior?
If it's not a defined behavior, let me explain.
It goes like this: [1:buffer1&][2:buffer2!] when i run a :bd, it goes like this: [1:buffer1&][4:No_Name!]
Willing to find out about this more :wink:
Cheers!