Sebastian P.

@steelydylan Thank you 👍 :)

I have the same problem under the following circumstances / symptoms (under OS X 10.13.5): - The project is huge / has lots of files - The plugin is reindexing...

@srobbin Thank you for your feedback. I had something similar in mind, but for simplicity and flexibility I was thinking about a new content type e.g. "alias" (or "reference") so...

> I could not find the section where this is mentioned. ~ means your home directory so ~/go/bin is basically for macOS /Users/USERNAME/go/bin/. Something seems weird, have the docs been...

> As suggested here #9369 I believe that adding Ollama LSP support would be a great possibility. Although requiring a GPU with enough memory for he heavier models they all...

I am not even able to open huge files, because it crashes on the file picker code-preview beforehand.

Hi @henomis the custom assistant implementation is only a wrapper/helper function for creating a new lingoose ollama assistant faster/easier (by using a options type). I've created a slim version of...

@ixjb94 thanks for taking the time to explain it this thoroughly 👍 I partly agree on the performance perspective, but I disagree regarding the usability/data error-resilience. If I understand this...

@ixjb94 Awesome thanks 👍 I have not noticed the normalize method in the Indicators class before, that makes it easier to work with without implementing a own helper function :)...

@ixjb94 That's simply wrong, all Moving Averages are by definition Lagging Indicators. Also, if I compare it to other libraries and the official TradingView SMA/EMA, then there is no such...