Open russel opened 10 years ago
Oh my goodness, this either got buried in the notifications section or I saw this and forgot to make a mental note of it because I was at work. It has been a crazy few months lately.
I'm sorry for the lack of communictiaon. I use your groovy mode and it is pretty great!
I realize that e-lisp activity is pretty limited for Groovy/Grails as well. I don't think this 'gradle' mode should be the focus of all activity. I like the functionality it brings, but it is still pretty sparse.
There is another grails mode that I have recently started to use, it hooks in with projectile-mode You can see it at emacs-grails-mode-ext. Unfortunately, it is not on MELPA though :(.
What if there was a single repository for these packages, like grails does with the grails community does with gpc here? something like groovymacs or some other better name. I wonder if the emacs grails mode project would be amenable to that? I could ask him.
Sorry again for the super late reply. :expressionless:
Another late comment,
I concur with @russel that maybe another repository could become the main one. Maybe just Groovy-Emacs-Modes ??
I created some time ago emacs-grails-mode-ext
which became grails-projectile-mode, available on MELPA. Nowadays, I work only with pure Java
, so improvements will likely come from pull requests.
I noticed recently emacs-grails which doesn't have any external dependencies. @lifeisfoo, I believe that it's a duplicated effort on your end, what about the following:
grails-projectile-mode
(built-in, projectile, etc.) ?On an other note, my previous issues with the official groovy-mode
were weird indentation in regards to array declaration, multi-line statements, closures. Improvements in that regards would be great.
I have just discovered this repository, as it's grails-mode has entered MELPA. There is also https://github.com/russel/Emacs-Groovy-Mode the groovy-mode of which is in MELPA, but the grails-mode of which was never picked up. Given E-Lisp activity in the Groovy/Grails community is strictly limited and it would be best to focus where the activity is, should this repository become the new focus of all Groovy Emacs activity?