Status: Accepted Owner: coreyoconnor Labels: Type-Defect Priority-Medium Component-Keymap-vim
New issue 228 by coreyoconnor: Actions executed from minibuffer apply to bottom window's buffer not previous windows buffer. http://code.google.com/p/yi-editor/issues/detail?id=228 Only tested using the vim frontend. Though it may apply to all frontends. 1. Start yi 2. Open a file via ":e <path>" ex command. 3. Split the window 4. Go to the bottom window 5. Edit a different file via ":e <path>" ex command 6. Go to the top window 7. Modify buffer. 8. Save the buffer using the ":w" ex command I'd expect to be able to save the buffer of the current window. Instead the buffer of the *bottom* window is saved. I think the issue was introduced with the patch " Fix minibuffer issue in multiwindow environment". However I don't think the real issue is the patch itself. The goal and method of solving the goal were fine IMO. But how the current window and buffer are restored on minibuffer close. Currently the window restored on minibuffer close is the window that becomes current after a WindowSet.delete. Which, due to the minibuffer window being added using addLast, will always be the bottom most window in the current tab. There are a variety of ways to fix this. One is to store the "current window" on minibuffer start. And always restore that window on minibuffer close. Another is to have a window stack separate from the WindowSet or buffer stack. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list [email protected] http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
