eclim 1.5.3 release and eclim git repository has moved to github

[Eric Van Dewoestine]

Hello all,

Earlier today I released version 1.5.3 of eclim. This is mostly a
maintenance release, but there are a few new features as well. More
info can be found in the change log[1].

I've also moved eclim's git repository to github[2] today. I'm hoping
that this move will make it a little bit easier for people to follow
and contribute to eclim's development.

Please note that any existing clones from the previous sourceforge
repository are not directly compatible with the new repos on github.
I had to clean up the author values for all the pre-git commit
history, so attempting to set the github repos as the new origin for
an existing sourceforge repos and then pulling may cause some issues.
So please clone a fresh version instead. My apologies for any
inconvenience this may cause.

If anyone has any comments or concerns, please let me know.

[1] http://eclim.org/changes.html
[2] http://github.com/ervandew/eclim

--
eric

[Kannan Rajah]

Eric,
  I just tried 1.5.3 and noticed a minor issue with LocateFile. When I type in a wrong character that does not match any file, I cannot use the backspace to remove that character. I have to press Esc to start again. I noticed that you added a drop down listing possible key strokes; not sure if that caused this side effect.


Kannan

--

You received this message because you are subscribed to the Google Groups "eclim-user" group.
To post to this group, send email to eclim...@googlegroups.com.
To unsubscribe from this group, send email to eclim-user+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/eclim-user?hl=en.

[Eric Van Dewoestine]

On Mon, Dec 14, 2009 at 10:58:39AM -0800, Kannan Rajah wrote:
> Eric,
> I just tried 1.5.3 and noticed a minor issue with LocateFile. When I type
> in a wrong character that does not match any file, I cannot use the
> backspace to remove that character. I have to press Esc to start again. I
> noticed that you added a drop down listing possible key strokes; not sure if
> that caused this side effect.

Yeah, I noticed that same issue soon after the release. To fix it
simply remove the <c-?> mapping (line 256) from:

eclim/autoload/eclim/common/locate.vim

--
eric

[Kannan Rajah]

Thanks, it works as before.

One question related to indentation. I have a logger.gst defined in ~/.vim/eclim/resources/jdt/templates/ and it has:
*************
import org.apache.commons.logging.Log;
import org.apache.commons.logging.LogFactory;
private static final Log log = LogFactory.getLog(${class}.class);
*************

When I type log, it automatically adds these to my source code. But it uses a hard tab for declaration of log. I have configured eclim to use only spaces. Any idea why this is happening? If I remember correctly, this was working fine for a long time. Not sure what I changed to cause this behavior. The other templates continue to work fine.


Kannan

--
eric

[Kannan Rajah]

Sorry, I spoke too soon. The change I made caused the LocateFile functionality itself to not work. I took the latest code. Here are the contents of line 255 and 256.

  exec 'imap <buffer> <silent> <cr> ' .
    \ '<c-r>=<SID>LocateFileSelect("' . a:action . '")<cr>'

Please tell me what to change.

Kannan

[Kannan Rajah]

Seems like the latest code itself has the fix.

Kannan

[Eric Van Dewoestine]

On Tue, Dec 15, 2009 at 11:47:35AM -0800, Kannan Rajah wrote:
> Thanks, it works as before.
>
> One question related to indentation. I have a logger.gst defined in
> ~/.vim/eclim/resources/jdt/templates/ and it has:
> *************
> import org.apache.commons.logging.Log;
> import org.apache.commons.logging.LogFactory;
> private static final Log log = LogFactory.getLog(${class}.class);
> *************
>
> When I type log, it automatically adds these to my source code. But it uses
> a hard tab for declaration of log. I have configured eclim to use only
> spaces. Any idea why this is happening? If I remember correctly, this was
> working fine for a long time. Not sure what I changed to cause this
> behavior. The other templates continue to work fine.

What is the result of the following in vim:

:echo &expandtab
:echo char2nr(g:EclimIndent)

--
eric

[Eric Van Dewoestine]

On Tue, Dec 15, 2009 at 12:25:18PM -0800, Kannan Rajah wrote:
> Seems like the latest code itself has the fix.

Yes, the latest code in git should work correctly, did you grab the
latest version or do you still need help fixing the version that
shipped with eclim 1.5.3?

--
eric

[Kannan Rajah]

I took the latest and so it was fixed. I realized it only after sending the mail.

I had asked a question on indentation. Can you please help me with that?

Kannan

--
eric

[Eric Van Dewoestine]

On Tue, Dec 15, 2009 at 08:48:44PM -0800, Kannan Rajah wrote:
> I took the latest and so it was fixed. I realized it only after sending the
> mail.
>
> I had asked a question on indentation. Can you please help me with that?

I replied to that one as well, but here is my response from that mail:

[Kannan Rajah]

Sorry, I overlooked. Here is the output.

:echo &expandtab ----> 0
:echo char2nr(g:EclimIndent) ------> 9

Kannan

eric

[Eric Van Dewoestine]

On Tue, Dec 15, 2009 at 09:45:56PM -0800, Kannan Rajah wrote:
> Sorry, I overlooked. Here is the output.
>
> :echo &expandtab ----> 0
> :echo char2nr(g:EclimIndent) ------> 9

That's why it's inserting a tab. If you enable expand tab in your
vimrc file then that should resolve the issue:

set expandtab

--
eric

[Kannan Rajah]

It is already set in ~/.vim/ftplugin/java.vim. Why isn't it picked up by eclim?

Kannan

--
eric

[Eric Van Dewoestine]

On Tue, Dec 15, 2009 at 10:03:51PM -0800, Kannan Rajah wrote:
> It is already set in ~/.vim/ftplugin/java.vim. Why isn't it picked up by
> eclim?

Probably because eclim's g:EclimIndent variable is initialized prior
to your ftplugin/java.vim being sourced. As a workaround, you can add
the following to your ftplugin/java.vim (set it to the number of
spaces you use for one level of indenting):

let g:EclimIndent = ' '

I may modify eclim to initialize this variable on demand which should
fix this case.

--
eric

[Kannan Rajah]

It works. Thanks.

Kannan

--
eric