-
-
Notifications
You must be signed in to change notification settings - Fork 17
nano cursor movement not working in Windows default console #55
Comments
I'm of a mind to drop nano on Windows entirely and use notepad. |
I like the fact or running the editor in the same console you are working and not spanning more windows. For my next workshop I'll consider moving to MobaXterm. I know it's not free as in freedom, but the free version is quite good, and we do use eg. GitHub for the git lessons, so... I also noticed that it has a package manager for Cygwin packages, so the stack installation would be trivial. Somethign as "open a MobaXterm terminal an type"
Although perhaps we have to take care of Anaconda paths. |
You do have a point there. New learners have a hard time as it is groking the relationship between command-line programs and GUI programs (something I wish the shell lesson focused more on, over contrived wildcard patterns). FWIW |
(I would die without |
I spent a little time on this today, but I can't for the life of me find a solution. nanorc doesn't allow rebinding commands to arbitrary keyboard controls, so I can't get it to bind the "move left" "move right" etc. commands to control codes that are actually being sent when I press "left" "right", etc. |
This would be very useful now that Windows has the official OpenSSH support. It would be nice to log in to a Windows Server via |
+1 |
Same issue here. Started worked with Windows Server Core and use OpenSSH as it works nice now. But with need of an editor and already use nano on mac and linux I loved to use nano here as well. So I installed using Any ideas? |
Using Git for Windows 2.9.0 installed selecting "Use Windows' default console window" nano launches correctly but when trying to move the cursor using the keyboard arrow keys it complains with a
[ Unknown Command ]
message, and the cursor does not move.This was a known problem when using MinTTY terminal and launching nano with
winpty nano
#31 (comment) in order to avoid the
redirection is not supported
error with MinTTY #50, but for me it happens the same in the default windows console.You can circumvent this running nano doing
which opens up nano in a new window, where the arrow keys work properly.
Or you can use
but in my opinion this adds up too much cognitive load to shell newcomers.
The text was updated successfully, but these errors were encountered: