Ensime not highlights code errors on Mac OsX

281 views
Skip to first unread message

Luigi Antonini

unread,
Feb 22, 2013, 3:55:35 AM2/22/13
to ens...@googlegroups.com
Hello everyone,
i'm new to this group and to Ensime, 
after years of java/scala development with full IDE's , Eclipse and Netbeans,
i'm trying some texteditor with some scala tools.

So i tried ensime on Linux with emacs and sublime 2 , and works fine,
but , same configuration , doesn't works in my mac with emacs.
Ensime server start without problems , but errors are not highlighted,
other things , like code formatting work well.
It seems that is wrong in compiling, 
because if i build project with ensime i says not errors.
.ensime project's file is generated through ensime-sbt-cmd.

Any idea?

Alex Gleyzer

unread,
Feb 25, 2013, 5:15:49 PM2/25/13
to ens...@googlegroups.com
I had a similar problem; saw the errors reported in *inferior-ensime-server* buffer, but they were not highlighted. Later I realized flymake-mode was not running, once I started it, everything worked fine. 

Alex

Luigi Antonini

unread,
Feb 25, 2013, 6:23:09 PM2/25/13
to ens...@googlegroups.com
Flymake solved perfectly the problem!

Tank you Alex!

Aemon Cannon

unread,
Feb 25, 2013, 8:13:24 PM2/25/13
to ens...@googlegroups.com
Hmm
You should not need flymake...
I think I see the problem. We recently starting using flymake's type-faces to color warnings/errors. So if flymake is not (required) somewhere.. it will probably not show correctly. Will fix in upcoming release!


--
You received this message because you are subscribed to the Google Groups "ENSIME" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ensime+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Luigi Antonini

unread,
Feb 26, 2013, 3:52:37 AM2/26/13
to ens...@googlegroups.com
Good!
This will help others emacs/ensime beginners like me to not scratch the head!

Alex Gleyzer

unread,
Feb 26, 2013, 2:25:55 PM2/26/13
to ens...@googlegroups.com
Aha, now it makes sense... I had flymake required by prelude (https://github.com/bbatsov/prelude) then turned it off for some other reason and a bit later realized ensime stopped highlighting errors. 

Aemon Cannon

unread,
Feb 26, 2013, 7:54:56 PM2/26/13
to ens...@googlegroups.com
fyi, uploaded 0.9.8.9 which should fix this issue.

Luigi Antonini

unread,
Feb 27, 2013, 2:06:04 PM2/27/13
to ens...@googlegroups.com
Tested new version just now ..
I works! Tanks!

aidy lewis

unread,
May 17, 2013, 10:22:42 AM5/17/13
to ens...@googlegroups.com
Hi,


I have started to investigate ENSIME today.

I am using Scala 2.9.1 and this version of ENSIME => 2.9.2-0.9.8.9. 

Unfortunately, I am not receiving highlight on errors.

I have enabled flymake-mode to no effect.

Thanks

Aidy

bull....@gmail.com

unread,
Sep 24, 2013, 6:57:50 AM9/24/13
to ens...@googlegroups.com
Did anybody found a solution to aidy's problem? I am experiencing the same problem.

Regards
Fabian

anild...@gmail.com

unread,
Jul 27, 2014, 2:33:32 PM7/27/14
to ens...@googlegroups.com, bull....@gmail.com
Same issue here.

It's not highlighting errors.

Scala 2.10.3
Ensime-sbt 0.1.5-SNAPSHOT

--
Thanks,
A

Rory Graves

unread,
Jul 27, 2014, 3:01:44 PM7/27/14
to ens...@googlegroups.com
Hi,

Can you try a couple of things:

1) Ensure you have the latest version of ensime
2) Confirm your java/sbt version.
2) Look at the output in the *inferior-ensime-XXX* buffer (errors with
the server ould end up here)

I was just using the lastest (admittedly on a Scala 2.11 project) on my
mac without issue.

If nothing pops out of the above - can you raise a ticket at
https://github.com/ensime/ensime-server/issues?state=open with as much
information as possible.

Thanks

Rory

snu...@hortonworks.com

unread,
Aug 1, 2014, 8:25:48 PM8/1/14
to ens...@googlegroups.com
New ensime user here. I can confirm this problem with the latest version available from melpa.
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.

Rory Graves

unread,
Aug 2, 2014, 4:09:17 AM8/2/14
to ens...@googlegroups.com
Hello,

Can you take a look at
https://github.com/ensime/ensime-server/issues/535 and see if any of it
applies to your
experience. If not, can you raise a ticket with somre more information
about your project structure (an example repo is great).

Thanks

Rory

Steve Nunez

unread,
Aug 2, 2014, 1:52:37 PM8/2/14
to ens...@googlegroups.com
It seems to be related to earlier reports about file location. When the
file is in src/main/scala/ the first letter of the string with the syntax
error is highlight. When the same file is at the top level of the project,
no error is reported.

IMO this should work regardless of file location, since it¹s a useful
feature and you might want it for quick & dirty small projects too.

- SteveN
>--
>You received this message because you are subscribed to a topic in the
>Google Groups "ENSIME" group.
>To unsubscribe from this topic, visit
>https://groups.google.com/d/topic/ensime/6947osHtXSU/unsubscribe.
>To unsubscribe from this group and all its topics, send an email to
>ensime+un...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.

Rory Graves

unread,
Aug 2, 2014, 1:53:56 PM8/2/14
to ens...@googlegroups.com
Cool, at least its the same error - I'm going to investigate this one.

Thanks

Rory


On 02/08/2014 18:52, Steve Nunez wrote:
> It seems to be related to earlier reports about file location. When the
> file is in src/main/scala/ the first letter of the string with the syntax
> error is highlight. When the same file is at the top level of the project,
> no error is reported.
>
> IMO this should work regardless of file location, since it零 a useful
Reply all
Reply to author
Forward
0 new messages