I haven’t tried WSL myself, but I understand the “Linux universe” is still pretty isolated from the “Windows universe”, and things like filesystem access and process spawning can be surprisingly slow because it’s still running on the NT kernel.
yes bash in windows is so isolated from the windows world that it is pretty useless to use in my daily work.
Hello Cduret,
Did you try the solution of supermarin to have kakoune on Windows ?
I did installed already kakoune in bash subsystem but it integrates poorly compared to vim
How so? I’ve installed kakoune into WSL and it appears to work exactly the same on Linux, except for a bug where a Kakoune server gets permanently stopped if you quit the creator of the session before the clients. Given this works on Linux just fine though I suspect the bug is actually in WSL.
I used to run Kakoune on WSL for quite a while (an before that on Cygwin) at work, what kind of problems are you experiencing on WSL ?
no pb with wsl, kakoune run same as linux box.
But I still use vim on my windows 10 workstation because vim is well integrated in my contextual menu of explorer and I can drop files on vim to open it, etc…
I want native software on windows, that wsl shit adds impedence and slow down my productivity compared to vim on that platform.
Could you use for your professional work your win32 favorite editor on linux with wine ?
I guess we have pretty different usage patterns, when I was on windows, in the end, I was running a X11 desktop through WSL to avoid having to deal with windows… So I did not mind that Kakoune was not really integrated. I had written a quick .bat file that was able to run Kakoune in mintty through cygwin on an arbitrary windows file, that could have been added to a context menu, but I do agree with WSL this would be even harder.
Kakoune relies on having a posix environment around it, I am not sure what a native windows port could look like, maybe building kakoune in msys could work ?
You can do the context menu thing – https://github.com/mawww/kakoune/wiki/Windows-tips – drag and drop would require a level of awareness about the greater world of windows, so unlikely in the short term.
As for drag and drop, I don’t even think Windows consoles support drag and drop events do they?
I know a guy who uses Emacs on windows 7 in a VM. He installed Arch Linux in it, Emacs starts at login and is running full-screen without window manager. He uses shared folders to access windows files. I suppose if he would like to use Kakoune, he would do the same setup for it. It sure has some overhead but he says it works just fine for him.
Indeed console do not support DnD on windows, I do not use vim in plain console but rather gvim.
The cygwin experience is not enough, I will stick with gvim on windows.
cheers
Hi all, for those coming from osx to win10.
I just moved to win10 platform this month (Feb 2019) and using the wsl/ubuntu. I found ‘apt-get’ did not install the same kakoune experience I had been used to on the osx. I used homebrew package manager for linux which solved my kakoune problems and am now back to normal with little effort.
As I read this thread on my way to eventually finding a solution thought it might help others posting it here.
linuxbrew
brew formulae kakoune
ubuntu/bionic apt-get kakoune
windows subsystem for linux
If you don’t mind, I would like to ask you, what kind of problems/differences you had during the usage of kakoune installed with apt compared to the one installed with brew?
It was only late last year that the Debian package for Kakoune started getting updated regularly. Even the most recent Ubuntu release has a Kakoune from 2016, but the next release (in April) should be up-to-date.
Oh my…
Thanks for the explanation Screwtapello that answers my head scratching as well.
Winkoune vote it up.
The console team at Microsoft have put together a blog on the future direction of ‘Windows Command-Line applications’. And quote ‘The new Win32 ConPTY API provides a mechanism that is similar to the POSIX PTY model’.
Link: Introducing the Windows Pseudo Console (ConPTY) API
With a github repo “EchoCon” ConPTY Sample App.
Link: EchoCon
The terminal IO (which ConPTY would help with) is an easy problem, Kakoune already has user interfaces abstracted away, so implementing a win32 based UI (with actual windows widgets) is doable and might be relatively easy to write.
The hard problem for native windows support is that the interaction/extension model of Kakoune expects a posix shell and the basic posix tools to be available, most interaction of Kakoune with the external world starts by it forking a shell process (I am thinking of |command<ret> and %sh{...}). I suspect we can get relatively far if there was (did not check if that exists) a windows native busybox, then its just a matter of tweaking ShellManager to use win32 api to run busybox in shell mode with the relevant arguments and redirections.
1 Like
Yeesss of course…for those who are thinking along the lines of IO redirection to win32 from wsl Windows and Ubuntu Interoperability another great blog post from Microsoft.
The continuous development of the wsl on win10 and with Terminus I am enjoying an uninterrupted experience with Kakoune. The new April 2019 windows patch will add file sharing between the mediums.
So I think I will head over to @Screwtapello @andreyorst help on kakoune documentation (racket/scribble just putting it out there have not looked if it is possible yet, docs::OOP->Functional).
Make more sense @andreyorst we back to playing nice.
Don’t mind me I am on a new badge frenzy emoji time 
.