-
Notifications
You must be signed in to change notification settings - Fork 34
MS WIndows #17
Comments
Could you explain what issues you encountered? I would also suggest you not work on a pull request yet because there are some large changes in plenary notably async await. We will probably be converting to async await jobs after async await is merged in plenary. |
Sure! One thing is that the autocmds do not work, because the path in neuron_dir contains backslashes and autocmd only accepts /. local pathpattern = string.format("%s/*.md", config.neuron_dir):gsub("\\","/") in The other issues are related to running neuron in WSL. You can start neuron from the WIndows side by calling: wsl.exe /bin/bash --login -c neuron Since neuron.nvim has the command "neuron" hardcoded, I tried to make a CMD file "neuron.cmd" and put it somewhere in PATH: @echo off
wsl.exe /bin/bash --login -c 'neuron %*' This lets me call it by simply typing "neuron ..." in CMD or Powershell just fine, the This might also be a way to solve my last problem: As neuron is running in WSL it return paths as they are mounted there. Of course those are not valid in the Win environment. I could translate the WSL paths in the wrapper. I hope this gives some insights into the current situation under Windows. |
Thanks for explaining. If you want to work on a pr that adds a configuration variable to change the |
Ok, I will try to do that, when I have some free time on my hands. Currently, I am a little busy with work. For now, I got it to work, with the little gsub "hack" and a simple Rust program which essentially emulates the CMD file from above + a simple regex substitution for the paths in the output. Btw. I really want to thank you, for this amazing plugin. It extremely enhanced my note taking experience so far 👍 |
Is there a recommended way of using the plugin under WIn10? I have neuron installed under WSL2 and its working quite well on its own. Only the interplay between neuron and the plugin does not work for my setup, yet. My first impession after looking at the code is, that the problems should not be too hard to solve. Maybe I will do a corresponding pull request in the next days, if I have the time.
But before I start working on this I wanted to ask, if you already solved this without modifying the plugin.
The text was updated successfully, but these errors were encountered: