logo       

Re: Groovy and (X)Emacs: msg#00166

lang.groovy.user

Subject: Re: Groovy and (X)Emacs

On Tue, 2004-11-23 at 22:41, Jeremy Rayner wrote:
> On Tue, 23 Nov 2004 14:56:16 -0500, Michael Campbell
> <michael.campbell-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:
> > I was just about to suggest to you ambitious types to take a look at
> > the mode that comes with the ruby distribution, as it doesn't require
> > semicolons either.

I was about to suggest the same thing, Of the languages already
supported by (X)Emacs, Ruby has the most similarity to Groovy in its
formatting issues so would make the best start point. Assuming of
course that the Ruby mode is good as a piece of elisp :-)

> OK, I've been brave and had a quick peek at ruby-mode. It looked quite simple
> to convert, so I've uploaded a new groovy-mode hook for emacs.
>
> details: http://groovy.codehaus.org/Other+Plugins

Splendid fellow, I was about to do the same, you beat me to it. But you
also managed to get it all in place on teh Web site which I wouldn't
have known how to start doing. Thanks for that, most splendid.

> It works fine in emacs on OSX 10.3,
> doing good stuff with curly braces, tabs etc,
> also I've added some keywords too.

It works on XEmacs 21.4.15 to the extent that it autoloads and stuff --
I have no body of Groovy code to try things out on so I can't really say
more.

> Let me know if it works for you, and if someone can confirm the
> details for xemacs,
> lets hope it's not too different from normal console based emacs.

In my .xemacs/init.el file I have a comment that global-font-lock-mode
only works in Emacs not in XEmacs and so have a selection -- I have
coded up my .emacs to use .xemacs/init.el and so use the same file for
Emacs and XEmacs.

I guess we have to discuss how to evolve the file. Does it go into CVS
somewhere where we can update it or do we send patches to you and have a
more manual system.

Issue number 1 of course is that Ruby comments start with a # whereas
Groovy comments start with // (is /*...*/ also allowed?

I wonder if the Hilit19 stuff is worth keeping, does anyone use this now
or does everyone just use Font Lock? (Saves keeping two sets of regular
expressions up-to-date.)

I guess that unless Groovy is going to add all the hideous pattern
matching syntax of Perl that Ruby took on board, this can be removed,
especially from the font-lock stuff.

Is there a set of scripts that I can make use of to test the features,
i.e. a few scripts that use all the known structures and features of
Groovy even if they do not make semantic sense.

PS Is this now development work rather than user work? :-)
--
Russel.
=============================================
Dr Russel Winder +44 20 7585 2200
41 Buckmaster Road +44 7770 465 077
London SW11 1EN, UK russel-Q5fiE77zhxfe9xe1eoZjHA@xxxxxxxxxxxxxxxx

Attachment: signature.asc
Description: This is a digitally signed message part

<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise