Skip to content
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

Discussion file-management layer #3848

Closed
punassuming opened this issue Nov 17, 2015 · 6 comments
Closed

Discussion file-management layer #3848

punassuming opened this issue Nov 17, 2015 · 6 comments
Labels
- Mailling list - File browser stale marked as a stale issue/pr (usually by a bot)

Comments

@punassuming
Copy link
Contributor

I will be revising vinegar layer as a package and wondered if we want a configurable file mgmt layer with options, or keep as separate layers for packages? Options I am thinking of would be vinegar, dired, diredp, ranger, dired-k, and sunrise-commander.

@punassuming
Copy link
Contributor Author

Neotree is only the sidebar, so I am thinking it should stay separate.

@StreakyCobra
Copy link
Contributor

Does it imply there will be a limitation to use only one file-management package at a time? There is maybe people that like to use both vinegar and ranger. I'm not in this case, just askin' :-)

@punassuming
Copy link
Contributor Author

No, I think we make them all accessible for use, but have a primary file manager using something like mentioned here: #3170

@StreakyCobra
Copy link
Contributor

I like it then 👍

@a13ph
Copy link

a13ph commented Feb 25, 2016

I'd put them all together, including neotree - see shells layer and how search tools are done for possible inspiration.
Mapping layers and packages one-to-one sound not great to me, it's not hard to teach people to use blacklist/whitelist keywords, I hope, at least for those who care about "cruft" packages in their setup.

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid!

@github-actions github-actions bot added the stale marked as a stale issue/pr (usually by a bot) label Feb 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
- Mailling list - File browser stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

3 participants