Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dotnet-fsi doesn't allow the use of up-arrow or moving the cursor without --readline #6185

Closed
cartermp opened this issue Feb 4, 2019 · 3 comments
Milestone

Comments

@cartermp
Copy link
Contributor

cartermp commented Feb 4, 2019

  1. Install a build of .NET Core that comes with dotnet fsi (link)
  2. Launch it
  3. Attempt to move the cursor around

This fails with dotnet fsi. However, it works fine with fsharpi from Mono:

fsharpi-move-cursor

@zpodlovics
Copy link

@cartermp Please also try the dotnet fsi with --readline+

#2407 (comment)

@cartermp
Copy link
Contributor Author

cartermp commented Feb 4, 2019

Thanks @zpodlovics this actually solves this problem and #6185, and lets ctrl+D work if you hit it twice (#6188).

@sasmithjr
Copy link

sasmithjr commented Feb 8, 2019

--readline+ also fixes an issue where the up arrow on macOS seems to be broken.

@cartermp cartermp changed the title FSI on .NET Core doesn't allow moving the cursor back (at least on macOS) dotnet-fsi doesn't allow the use of up-arrow or moving the cursor without --readline Feb 19, 2019
@cartermp cartermp modified the milestones: 16.1, Core 3.0 Mar 19, 2019
@cartermp cartermp modified the milestones: .NET Core 3.0, 16.3 Aug 5, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants