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

Wanted - ability to change default directory handler away from dired. #3170

Closed
synic opened this issue Sep 28, 2015 · 9 comments
Closed

Wanted - ability to change default directory handler away from dired. #3170

synic opened this issue Sep 28, 2015 · 9 comments
Labels
Feature request stale marked as a stale issue/pr (usually by a bot)

Comments

@synic
Copy link
Contributor

synic commented Sep 28, 2015

There are lots of cool filemanagers for emacs, and a few of them are available in layers for spacemacs, including ranger, and neotree.

Learning one of these, however, is not sufficient for using emacs, because the default directory handler is dired, and spacemacs doesn't change it. So even if you learn everything about ranger, you're still going to need to learn dired and switch back and forth between them.

Links on the spacemacs homepage provided by projectile open in dired. Typing :e ~/ sometimes loads it in dired, sometimes in ranger. Sometimes it's a minimal version of dired, sometimes it's a full buffer version of dired. I have not figured out what changes this.

IMHO, people should only have to learn to use one file manager. It should be easy to change what file manager that is.

@synic
Copy link
Contributor Author

synic commented Sep 28, 2015

Related ranger ticket: punassuming/ranger.el#49

@syl20bnr syl20bnr added this to the release 0.105 milestone Sep 29, 2015
@punassuming
Copy link
Contributor

I am baking something into ranger to optionally default to opening in deer, but do we want to develop a handler in spacemacs to cover all managers?

@synic
Copy link
Contributor Author

synic commented Oct 4, 2015

@Ralesi has put this into ranger. I'm going to leave this ticket open as I still think it's probably something people will be looking for in spacemacs. If someone wants to use neotree, they are going to want to use neotree for all file operations. It seems strange to install a file manager that you can't use everywhere a file manager is required.

@robbyoconnor
Copy link
Contributor

@Ralesi -- yes :D

I am baking something into ranger to optionally default to opening in deer, but do we want to develop a handler in spacemacs to cover all managers?

@punassuming
Copy link
Contributor

@synic, @robbyoconnor, I have something working as a macro, what directory handlers would we like outside of dired, ranger / deer, and neotree? I need to test the possible options to make sure it works.

@synic
Copy link
Contributor Author

synic commented Oct 15, 2015

@Ralesi Looked around in the layers. The only other one I know is a file manager is vinegar: https://github.com/syl20bnr/spacemacs/tree/develop/layers/%2Bvim/vinegar

@punassuming
Copy link
Contributor

Right now, with neotree, it forces as a sidebar , so adding it as a handler disrupts the flow. Vinegar is hooked into dired much the same way as ranger, so if you open a directory in dired, it will automatically show. We can disable that, and make it a separate minor mode in the layer though.

@syl20bnr
Copy link
Owner

syl20bnr commented Jan 6, 2016

I put this one on the side for now as I see it as an advanced feature, let's keep it open for a future version.

@syl20bnr syl20bnr removed this from the release 0.105 milestone Jan 6, 2016
@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
Feature request stale marked as a stale issue/pr (usually by a bot)
Projects
None yet
Development

No branches or pull requests

5 participants