Add Elevator

[kapitanluffy]

• I'm the package's author and/or maintainer.
• I have have read the docs.
• I have tagged a release with a semver version number.
• My package repo has a description and a README describing what it's for and how to use it.
• My package doesn't add context menu entries. *
• My package doesn't add key bindings. **
• Any commands are available via the command palette.
• Preferences and keybindings (if any) are listed in the menu and the command palette, and open in split view.
• If my package is a syntax it doesn't also add a color scheme. ***
• If my package is a syntax it is named after the language it supports (without suffixes like "syntax" or "highlighting").
• I use .gitattributes to exclude files from the package: images, test files, sublime-project/workspace.

My package is Elevator

There are no packages like it in Package Control.

My package is similar to ... However it should still be added because ...

[packagecontrol-bot]

Automated testing result: ERROR

Repo link: Elevator
Results help

Packages added:
  - Elevator

Processing package "Elevator"
  - ERROR: Invalid key '<character>'
    - File: Default.sublime-keymap
    - Binding: {"args": {"forward": false}, "command": "elevator_move", "keys": ["alt+up", "<character>"]}
  - ERROR: Invalid key '<character>'
    - File: Default.sublime-keymap
    - Binding: {"args": {"forward": true}, "command": "elevator_move", "keys": ["alt+down", "<character>"]}

[packagecontrol-bot]

Automated testing result: SUCCESS

Repo link: Elevator

Packages added:
  - Elevator

Processing package "Elevator"
  - All checks passed

[braver]

Looks like you're basically providing what LineJumper already does. That's a pretty stale package though. Please find out if you can contribute to that package instead of adding a new package. Maybe you can even take over that repo. Otherwise, if that does not work out, we can consider removing that existing package with yours, and bring the updated and improved functionality to more users.

[braver]

Please let us know if things worked out with LineJumper.

[kapitanluffy]

Please let us know if things worked out with LineJumper.

Will do. I contacted the author 👍

[braver]

Looks like the answer to your question is "no" 😄. Feel free to proceed with a replacement of the existing entry with yours.

[kapitanluffy]

Looks like the answer to your question is "no" 😄. Feel free to proceed with a replacement of the existing entry with yours.

Oh, this has been out of my radar. Yeah, tried reaching out but he did not reply. What should I do to proceed?

[braver]

The cleanest thing to do is remove the existing entry for LineJumper, and add "LineJumper" to the previous_names of your package (example: https://github.com/wbond/package_control_channel/pull/8875/files#diff-2b7dc45bc94d46ab4847d3281d04dac17d5f228e762a8491333857d6ca7cc6d2R455). Also ensure your package has a version higher than the last one for LineJumper (1.0.0). This effectively replaces that with yours and will upgrade existing users to the latest version of your package. Bonus points for adding an upgrade message (docs) telling those users what happened.

[kapitanluffy]

Ok. Got it. I will close this for now. I will add the highlighting feature from linejumper and reopen this PR.