You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Running native interactive command-line app breaks history #571
I'm not certain #495 will solve this. By necessity it will reuse the readline implementation we have, because it's cross-platform and its existing one is Windows native specific.
Oh, my understanding was that "host ~ readline". So src/Microsoft.PowerShell.Linux.Host/readline.cs would stay? I then will start filling more usability bugs.
sergei (@vors)#495 is porting the Nano host to Linux. However, it will really only replace main.cs. Its UI implementation (the readline, ui, rawui, etc.) does not utilize System.Console; instead it P/Invokes to Windows native APIs. So even after porting the Nano host... most of it will be replaced with what we already have.
I still have reservations about "porting" the Nano host, because ours is already (seemingly) close to feature-parity. I'd like to determine what managed code only features are available in the Nano that we don't have, before deciding which host to use as the primary one.
Activity
andyleejordan commentedon Feb 21, 2016
I'm not certain #495 will solve this. By necessity it will reuse the readline implementation we have, because it's cross-platform and its existing one is Windows native specific.
palladia commentedon Feb 21, 2016
#495 does not address this issue. This issue is same as #461.
vors commentedon Feb 21, 2016
Oh, my understanding was that "host ~ readline". So
src/Microsoft.PowerShell.Linux.Host/readline.cswould stay? I then will start filling more usability bugs.andyleejordan commentedon Feb 21, 2016
sergei (@vors) #495 is porting the Nano host to Linux. However, it will really only replace
main.cs. Its UI implementation (the readline, ui, rawui, etc.) does not utilizeSystem.Console; instead it P/Invokes to Windows native APIs. So even after porting the Nano host... most of it will be replaced with what we already have.I still have reservations about "porting" the Nano host, because ours is already (seemingly) close to feature-parity. I'd like to determine what managed code only features are available in the Nano that we don't have, before deciding which host to use as the primary one.
andyleejordan commentedon Feb 23, 2016
This is really similar to #484 as well.
andyleejordan commentedon Mar 1, 2016
This has been fixed upstream in dotnet/corefx#6488. Waiting to integrate changes.