The buffer "list" is supposed to act as a stack (this is borrowed from emacs). If you want to "bury" the current buffer at the end, that's easily done. I'll commit a patch doing this in a moment.
Cheers, JP. On Fri, Mar 27, 2009 at 7:41 PM, <steffen.sier...@gmail.com> wrote: > Fri Mar 27 19:37:11 CET 2009 steffen.sier...@gmail.com > * fixed nextBufW bug > > Bug description: > nextBufW only switches back to previously used buffer, thus nextBufW switches > only between 2 buffers regardless of the number of buffers available. > I recognized this behaviour in vim-Mode when executing ":n". prevBufW works > fine. > > Possible Fix: > the function fixCurrentBufferA_ used by tabsA seems to interfere with > bufferStack handling, thus > nextBufW was broken. I temporarely fixed nextBufW by "duplicating" the > switchToBufferE-function > plus adding correct bufferStack-Handling for given use-case in data-accessor > function. > > I consider this fix to be dirty at the moment, but at least it removes > (at least for some users, uhm... me :) ) an very annoying Bug. > > There might be more funny behaviours due to fixCurrentBufferA_ and it might > be prefferable to > fix this in tab handling ?!? > > > > > --~--~---------~--~----~------------~-------~--~----~ Yi development mailing list yi-devel@googlegroups.com http://groups.google.com/group/yi-devel -~----------~----~----~----~------~----~------~--~---
