You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
jlanzarotta, first let me say how much I've benefitted from using BufExplorer over several years now. Thanks so much.
I'd love it if I could put the files in the buffer list in whatever order I wanted, completely abandoning any form of automatic sorting. This would accomplish the same thing as dragging tabs around in a graphical IDE.
Some ideas on how this could be implemented: have a separate sorting mode that's called "custom" or something like that. Then, since hitting 'd' in the buffer list deletes that buffer from the current list of open buffers, I could see having some sort of "paste" key, available in custom mode, that would put the most recently closed filename back in the list, but at the place the user hit the paste key. (I realize "p" is already taken, but I'm sure you could find something sensible.) You could maybe even make it so that deleting and pasting a buffer name while in any traditional sort mode would jump it automatically into custom mode at the moment they hit paste.
Then, when I've gotten them in the order I want at that moment, I would love to be able to cycle through the files from within the editor window itself in the order they are in the list. This would accomplish the same thing as ctrl-tabbing through buffer tabs in a graphical IDE. It would be the same thing as ":bp" or ":bn" in normal vim, but instead of going through the files in order of file number it would go by current BufExplorer list order. BufExplorer could maybe have ":BufExplorerPrevious" and ":BufExplorerNext" commands (that users could assign to some shortcut key as they saw fit). This would not need to be limited to custom sort mode, since it'd be super useful regardless of how they're sorted. By making it a command, we could jump between files in our desired order without even going into the buffer list.
Thanks for considering this. Would love to know what you think.
The text was updated successfully, but these errors were encountered:
jlanzarotta, first let me say how much I've benefitted from using BufExplorer over several years now. Thanks so much.
I'd love it if I could put the files in the buffer list in whatever order I wanted, completely abandoning any form of automatic sorting. This would accomplish the same thing as dragging tabs around in a graphical IDE.
Some ideas on how this could be implemented: have a separate sorting mode that's called "custom" or something like that. Then, since hitting 'd' in the buffer list deletes that buffer from the current list of open buffers, I could see having some sort of "paste" key, available in custom mode, that would put the most recently closed filename back in the list, but at the place the user hit the paste key. (I realize "p" is already taken, but I'm sure you could find something sensible.) You could maybe even make it so that deleting and pasting a buffer name while in any traditional sort mode would jump it automatically into custom mode at the moment they hit paste.
Then, when I've gotten them in the order I want at that moment, I would love to be able to cycle through the files from within the editor window itself in the order they are in the list. This would accomplish the same thing as ctrl-tabbing through buffer tabs in a graphical IDE. It would be the same thing as ":bp" or ":bn" in normal vim, but instead of going through the files in order of file number it would go by current BufExplorer list order. BufExplorer could maybe have ":BufExplorerPrevious" and ":BufExplorerNext" commands (that users could assign to some shortcut key as they saw fit). This would not need to be limited to custom sort mode, since it'd be super useful regardless of how they're sorted. By making it a command, we could jump between files in our desired order without even going into the buffer list.
Thanks for considering this. Would love to know what you think.
The text was updated successfully, but these errors were encountered: