Skip to content

Conversation

Varriount
Copy link
Contributor

No description provided.

@joneshf
Copy link
Collaborator

joneshf commented Feb 27, 2014

Does @leonardoce's package https://github.com/leonardoce/nimrod-sublime not do the things you need it to do? Have you checked if @leonardoce would accept a PR for your changes?

@FichteFoll
Copy link
Collaborator

@Varriount ping

@Varriount
Copy link
Contributor Author

The trouble is that yes, while we might be able to merge our repo into @leonardoce's, he's not on the #nimrod irc channel, and it might be irritating to him/her to have to keep accepting changes into his/her repository.

@joneshf Our package has various features to integrate with the nimrod compiler, including syntax and compiler checking, compiler driven syntax suggestion, etc. @leonardoce's package only does syntax highlighting.

Right now, I am endeavoring to move our repository to @nimrod-code, since that's the user for official nimrod stuff, and will give access to those that come after me.

@FichteFoll
Copy link
Collaborator

In that case, maybe @leonardoce is willing to let you take over his package (Package Control has ways to do that). Since yours is likely to be the official package it's a good argument for higher priority over similar plugins. It would only benefit the users.

(Disclaimer: I have no idea how "nimline" and "nimrod" are affiliated with each other, I don't even know what they are.)

@Varriount
Copy link
Contributor Author

"NimLime" is that name of our proposed package, being a portmanteau of "Nimrod" and "Sublime".

Nimrod itself is a statically compiled systems programming language, with a focus on compile-time evaluation. github.com/Araq/nimrod is the main repo, and nimrod-lang.org is the website.

@FichteFoll
Copy link
Collaborator

@leonardoce, please show some cooperation. If not, we will assume that you either don't care or are not responsive enough and will just remove your package in favor of the "more official" one here for the reasons mentioned by @Varriount above.

@leonardoce
Copy link

Hi @FichteFoll. I think you can just remove my package in favour of the @Varriount one that supports more functions other than syntax highlighting.

@FichteFoll
Copy link
Collaborator

All right.

@Varriount, can you remove the "Nimrod" package and add that to a previous_names array of your package?

@FichteFoll
Copy link
Collaborator

@Varriount ping

@Varriount
Copy link
Contributor Author

Will do, as soon as I get out of class.

@Varriount
Copy link
Contributor Author

@FichteFoll Updated.

@joneshf
Copy link
Collaborator

joneshf commented Apr 25, 2014

I don't know how PC handles case, so let's assume you need to use the same casing. You'll want to change nimrod to Nimrod. Also you need to push a tag greater than 0.2014.x in order to actually get things working.

Also, thanks for Nimrod :D

@Varriount
Copy link
Contributor Author

@FichteFoll Updated and fixed.

@FichteFoll
Copy link
Collaborator

I recommend 1.0.0 for your version, but you.re free to use whatever you want to as long as it's a valid semver.

FichteFoll added a commit that referenced this pull request Apr 28, 2014
@FichteFoll FichteFoll merged commit 5449fc5 into wbond:master Apr 28, 2014
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

Successfully merging this pull request may close these issues.

4 participants