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

Still maintained? #31

Closed
emanuelen5 opened this issue Jan 15, 2019 · 4 comments
Closed

Still maintained? #31

emanuelen5 opened this issue Jan 15, 2019 · 4 comments

Comments

@emanuelen5
Copy link
Collaborator

I am developing a plugin with almost identical feature set Word-highlighter (name subject to change) and wanted to publish my package on Package Control and therefore issued a pull request. However, the maintainers quickly noted that my package is eerily similar to yours.

They therefore suggested that I should reach out to you and see if you are still maintaining this package, as well if you accept pull requests. I however do not feel like taking your package and turning it into mine since that would require a lot of work for me (writing test cases all over etc.).

Do you feel like our plugins are too similar to coexist on PC (don't consider the name - it will change before being published on PC)?

@xacid
Copy link
Contributor

xacid commented Jan 17, 2019

I am not the owner but was an contributor.
I installed Word-highlighter and played around a bit. Some comments:

  1. Good see the color palette is configurable through the file (that has been long-requested here). It will be even better if the file is accessible from the menu.
  2. "Edit highlight color" doesn't work for some color schemes.
  3. I personally feel the keys are too long. Using the menu to edit it, I got "error: The settings file "res://Packages/word_highlighter/Controls/Default (Windows).sublime-keymap" could not be opened".

@emanuelen5
Copy link
Collaborator Author

emanuelen5 commented Jan 23, 2019

Hi, thanks for the comments.

  1. Sure, I can add the scheme template to the menu.
  2. This is hard to investigate without more details.
  3. Fixed the error and added test cases for it.

You’re welcome to submit issues to the Github page if you have any more comments or suggestions.

@seanliang
Copy link
Owner

seanliang commented Jan 24, 2019

@emanuelen5 Sorry for the late response. I've invite you as a collaborator, please feel free to make your changes.

@emanuelen5
Copy link
Collaborator Author

Sure, I can be a collaborator. However, I do not think our plugins are similar enough to be completely merged. Also, adding coverage testing etc. would be too much work for me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants