-
Notifications
You must be signed in to change notification settings - Fork 55
A pull request :) #4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should keep Bclose! here because the behaviour is not the same. If I split a tab in two windows and then I open un file in one window with ranger, the window in delete and the file is open in the other window... Can you try this? Do you use neovim?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I use neovim and do not have Bclose, and @bramblex's changes work perfectly. In fact the tabnew change makes it function in a much more useful way.
It's hard to explain what it's even doing, because it isn't actually opening things in new tabs. It's opening them where I expect them. If I make a new split, and then open ranger from that buffer, the selected file from ranger is opened inside that buffer.
|
Hi, thank you for your contribution! but I would merge it if made some changes. Please don't modify the indentation because it is harder to see the changes. Then I don't understand why you say 'Use new tab instead new buffer to open terminal.' |
|
I have tried these changes on my fork as well and they work great with neovim. I admit i don't fully understand the implications of enew vs tabnew or bdelete! vs bclose! But it does work well and I am happy to use all vim commands and no shell invocations. The code also looks sane. I also think this should be merged. |
|
@bramblex I am using your fork, and it works great. You don't have issues enabled for it, so I'm asking a question here. Can we handle opening multiple files in some sane way? Right now if you open multiple files, it just opens them in a bunch of buffers in vim. I'm not sure what it should do, but opening them in splits or tabs seems more sane. Thoughts? |
|
I don't use to open multiple files at once. what I do usually is:
Bclose is useful for the following use case:
|
|
About the multiple files selection ranger's feature, I don't use it so I have no clear ideas about that... I think, by default, it should open the files in buffers and let the user to open the buffers in tabs and/or windows. This seems to be the closest to the vim philosophy. But we could provide a setting to open the files in the tabs or splitted windows... like that everyone would be happy. |
|
Why open ranger in new tab instead of new buffer? Because using a new tab to open ranger won't change the existed windows or buffers, so it just close the tab using |
|
I think you need a buffer explore, such as minibufexpl or smart tab line in airline. : ) |
|
Because if you open ranger from a window, you expect to open the file from ranger in the same window, no? |
|
it seems that each persons expect different behaviors so I agree if you want to add options for changing the default behaviors |
|
The features added in this PR are now implemented or are coming (like using new tab instead of new buffer, will come as an option #65). I have to close it now since it's getting old but thank you for your contribution and the good ideas you brought. |
: )