Code Monkey home page Code Monkey logo

Comments (7)

NickNeck avatar NickNeck commented on June 12, 2024 2

Hello @slashmili
here is a little asciicast to show the problem: https://asciinema.org/a/FYGuCyVfrfa4kmkBTWYrZxV9D

from alchemist.vim.

slashmili avatar slashmili commented on June 12, 2024 2

Ok maybe asyncomplete.vim is not for everyone. I'm also new to it! (for buffer you need asyncomplete-buffer.vim)

So it looks like for some reason when deoplete offers auto-complete based on around source, it decides to put extra IO.

I would expect that since the source of around is not Alchemist, it shouldn't have done that 🤷

To be honest I don't have any clue why this is happening. I've been using asyncomplete.vim past few months. I've just switched back to deoplete and try to debug it.

However I can't give you a time when it's going to happen. could be this week or the worst case end of the next month but it will happen since I myself will get annoyed with it 😆

from alchemist.vim.

NickNeck avatar NickNeck commented on June 12, 2024 1

Yeah, that doesn't fix the problem it just reduces the pain. Hopefully, @slashmili can say a little bit more about this problem. @rmad17 have you asked in the elixir forum if someone else has this problem?

from alchemist.vim.

slashmili avatar slashmili commented on June 12, 2024 1

Hi!

Sorry for the late respond, I tried it locally an it looks ok(as usual 😉 )
https://asciinema.org/a/zHREnYcDur7ejdJHXif7oaJWr

Can you show me how do you get into the situation with IO.IO.inspects ?

I also think texts in buffer are causing the issue. if I can reproduce it, I'll see if I can somehow skip putting prefix for buffers. Also not sure why buffers are passed to Alchemist ...

On the side note, I just released a new version that has support for asyncomplete.vim plugin(#161). If you are not a deoplete user and just trying it because of alchemist.vim you might want to try asyncomplete.vim.

from alchemist.vim.

NickNeck avatar NickNeck commented on June 12, 2024

I have the same problem. This seems to happen when you take the proposed text from the source around. As a workaround, you can disable the source. I am not sure if this behavior comes up with the source buffer too.

Config to ignore sources:

let g:deoplete#ignore_sources = {}
let g:deoplete#ignore_sources._ = ['buffer', 'around']

from alchemist.vim.

rmad17 avatar rmad17 commented on June 12, 2024

@NickNeck Now the error has reduced in frequency but it still exisits. Also buffer does not help.

from alchemist.vim.

balena avatar balena commented on June 12, 2024

I was having exactly the same problem and it gone away after migrating to asyncomplete.vim. Other problems came, though, as now I don't get completion for the current file, like, I don't get local variable names, functions, etc. But at least the annoyance described here doesn't happen anymore.

from alchemist.vim.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.