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

Shift + Enter / Shift + Tab doesn't;t work on Mac Monterey #50

Open
Kingdom-Of-Heaven opened this issue Jun 3, 2022 · 10 comments
Open
Labels
bug Something isn't working external

Comments

@Kingdom-Of-Heaven
Copy link

Kingdom-Of-Heaven commented Jun 3, 2022

I've just installed dotnet reply on my Mac Monterey 12.4. According to documentation SHIFT + Enter should start multiline nevertheless id doesn't work. Same with Shift+Tab to see last line from history it also doesn't work. Is it a bug or am I missing something?

@jonsequitur
Copy link
Owner

Shift+Enter does seem to be broken on Mac.

Shift+Tab doesn't show history, it's intended to navigate through completions.

If you type Console.<Tab> it cycles forward through completions and if you type Console.<Shift+Tab> it cycles backwards...

In theory. This seems to be broken on the Mac and on Windows, I'm seeing the order of the completions is wrong.

@jonsequitur jonsequitur added the bug Something isn't working label Jun 4, 2022
@Kingdom-Of-Heaven
Copy link
Author

I agree, this is a bug hopefully dev team will fix it asap as it's annoying to work without that basics shortcuts.

@DamianReeves
Copy link

Any update on this? On a Mac and using F# and no Shift-Enter makes this a pain

@cartercanedy
Copy link

Currently I'm getting a total crash when I press Tab or Shift-Tab, Shift-Enter works for me though.

@cartercanedy
Copy link

Maybe this was already determined to be a dotnet interactive api bug, but debugging the dotnet interactive source is showing that the bug is in the command parser within Microsoft.DotNet.Interactive.Kernel. Not fixable here @jonsequitur

@cartercanedy
Copy link

I made the fix in dotnet-interactive upstream, but the tnterface has changed significantly since the package version referenced in the project file. It's going to take some work to update

@jonsequitur
Copy link
Owner

My understanding is this is a .NET console API bug.

@cartercanedy, can you point me to a fix that you tried in .NET Interactive?

@cartercanedy
Copy link

See this commit

@jonsequitur
Copy link
Owner

Thanks!

@cartercanedy
Copy link

Just confirming that the process doesn't crash after the most recent release, don't know if the issue above was also a result of the same kind of kernel crashes or smth else

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working external
Projects
None yet
Development

No branches or pull requests

4 participants