-
Notifications
You must be signed in to change notification settings - Fork 12
Looking for a new maintainer #17
Comments
I'm interested in being maintainer. |
I just sent you an invite. |
@asok May I ask why you turn out not to use this feature? Did you find a better alternative? |
There's ranger.el which implements the same feature (and much more). But that's not reason why I do not use it. |
I have a similar feature in diredc, but in the style of midnight-commander, and with more exclusion options besides file extensions (eg. mime-types and other ueries). My plan is to also support hexl-mode preview for binary files, and for users of GUI emacs to support pdf and image previews. |
Added to the readme. |
Thank you.
…On 2021-03-19 02:38, Adam Sokolnicki wrote:
Added to the readme.
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
|
Well, @HawaiinPizza proposed their interest. What do you expect a maintainer to do? I am also interested. |
@jcguu95 I just added you as a collaborator. |
Does this project have a new maintainer since this post? I'm interested in maintaining it too, and I have some ideas for where to take it (without piling on features/bloat). |
I think the best would be to add volunteers as collaborators. I would move ownership to whoever shows some interest in the project. I wouldn't want to just hand it over to someone who wouldn't find time and will to maintain it. There might be users of this package who depend on it. @karthink I'll add you as a collaborator. |
I've creating this issue so I could find someone that is willing to maintain this project.
Originally I've created
peep-dired
to learn and play with Emacs. The idea of peeping the files from dired sounded very interesting so I've decided to code it. But as it turned out I don't actually use this feature! So the project got abandoned, and yet from time to time someone is creates an issue or replies to some. So some kind of maintenance would be useful.So if you would like to take this project over from me please write in this issue and and we can think of something.
The text was updated successfully, but these errors were encountered: