rbong
rbong
Yes, the plugin only supports Lua 5.1 unfortunately, because this is the version used by LuaJIT and Neovim. I recommend using LuaJIT if you can, as it is much faster....
>Maybe it would be worth to document that on windows the ^M symbol can appear when calling lua externally. Unfortunately it's likely not that simple and things may still be...
>Tag 3.0.0 with luajit shows flog buffer like this Thanks. FYI I *believe* the path issue that caused the LuaJIT error may be fixed. But I haven't tested it on...
I pushed fixes that should reliably remove carriage returns on Windows. Let me know if there are still issues. Thanks again for reporting this bug.
Sorry, I missed that. The `v3.0.0` screenshot looked fine to me at a glance before. I will take a look. PRs welcome for this issue though because I will have...
Since it's the same as `v3.0.0`, does that mean it still shows a carriage return at the end of every line?
Sorry for lack of progress on this ticket. I still have to set up a pure Windows testing environment for issues like this. >The issue with the carriage returns in...
>Let me know your thoughts or if you have any ideas. Probably differences in how your shell is escaping strings. >I can confirm this works Thank you, closing this issue...
Unfortunately I was not able to recreate this. Flog seems to work with the Nu shell for me. You may find it works with this setting on, although it worked...
> I am using Windows 11 Thanks for the info. WSL or native Windows 11?