swank:call-completion

45 views
Skip to first unread message

richard emberson

unread,
Apr 30, 2012, 1:17:04 PM4/30/12
to ens...@googlegroups.com
In the documentation and comments for the protocol
swank:call-completion
are references to
swank:scope-completion
and
swank:type-completion
which can be used to get the type id that is used
to get method/function information.

What should be used instead of
swank:scope-completion
and
swank:type-completion
since they do not exist?

Richard Emberson
--
Quis custodiet ipsos custodes

Aemon Cannon

unread,
Apr 30, 2012, 1:37:35 PM4/30/12
to ens...@googlegroups.com
swank:completions is now the preferred method. 

richard emberson

unread,
Apr 30, 2012, 6:18:49 PM4/30/12
to ens...@googlegroups.com
If I have the following

val myStr: String = ...
val myStrSize = myStr.si<c-x><c-o>

object-dot-method, then Ensime completion produces "size" so I get

val myStrSize = myStr.size

But, if I have

val myStr: String = ...
val myStrSize = myStr si<c-x><c-o>

object-space-method, Ensime does not find the String method size.

Is this an issue with Ensime or with the front-end
I am using (Envim) that commmunicates with Ensime?

Thanks

Aemon Cannon

unread,
Apr 30, 2012, 6:55:37 PM4/30/12
to ens...@googlegroups.com
Richard,

Ensime *should* handle this case transparently. Can I see the RPC call/response for both cases?

richard emberson

unread,
Apr 30, 2012, 7:16:03 PM4/30/12
to ens...@googlegroups.com, Aemon Cannon
Attached is first the case:

val s = "hi"
val i = s.si

and the second is for

val s = "hi"
val i = s si

Richard
RPC_ONE
RPC_TWO

richard emberson

unread,
Apr 30, 2012, 7:21:30 PM4/30/12
to ens...@googlegroups.com, Aemon Cannon
Aemon,

Looks like in the second case, object-space-method, only the base
class/trait methods are being returned.

Richard

On 04/30/2012 03:55 PM, Aemon Cannon wrote:

Aemon Cannon

unread,
May 1, 2012, 12:25:56 AM5/1/12
to richard emberson, ens...@googlegroups.com
Richard,

Tried this case in ensime-on-emacs this evening. Seems to work fine. Is it possible you're not
writing the buffer before doing the lookup?

richard emberson

unread,
May 1, 2012, 9:52:28 AM5/1/12
to Aemon Cannon, ens...@googlegroups.com
I am going to have to write a bug against Envim.
val i = s.si
returns size
while
val i = s si
returns pattern not found.

Thanks
Richard

On 04/30/2012 09:25 PM, Aemon Cannon wrote:
> Richard,
>
> Tried this case in ensime-on-emacs this evening. Seems to work fine. Is
> it possible you're not
> writing the buffer before doing the lookup?
>
> On Mon, Apr 30, 2012 at 7:21 PM, richard emberson
> <richard....@gmail.com <mailto:richard....@gmail.com>> wrote:
>
> Aemon,
>
> Looks like in the second case, object-space-method, only the base
> class/trait methods are being returned.
>
>
> Richard
>
> On 04/30/2012 03:55 PM, Aemon Cannon wrote:
>
> Richard,
>
> Ensime *should* handle this case transparently. Can I see the RPC
> call/response for both cases?
>
> On Mon, Apr 30, 2012 at 6:18 PM, richard emberson
> <richard....@gmail.com <mailto:richard....@gmail.com>
> <mailto:richard.emberson@__gmail.com

Aemon Cannon

unread,
May 1, 2012, 11:43:02 AM5/1/12
to richard emberson, ens...@googlegroups.com
Great.
Thanks, Richard


       <mailto:richard.emberson@gmail.com>>> wrote:

           If I have the following

           val myStr: String = ...
           val myStrSize = myStr.si<c-x><c-o>

           object-dot-method, then Ensime completion produces "size" so
       I get

           val myStrSize = myStr.size

           But, if I have

           val myStr: String = ...
           val myStrSize = myStr si<c-x><c-o>

           object-space-method, Ensime does not find the String method
       size.

           Is this an issue with Ensime or with the front-end
           I am using (Envim) that commmunicates with Ensime?

           Thanks

           --
           Quis custodiet ipsos custodes



   --
   Quis custodiet ipsos custodes


Reply all
Reply to author
Forward
0 new messages