Shortcut in console; disable popup cards

[srhrnkn]

Two questions:

1. About a year ago I asked this question about getting a keyboard snippet to work in the console as well as the editor - the solution provided there has stopped working. The snippet in question is:

 {
"key": "Ctrl+n",
"command": "type",
"args": { "text": "%in%" },
"when": "editorLangId == r"
}

It seems like Ctrl+n is triggering the down arrow in the console - if I've scrolled up through the command history it'll advance to the next entry (which of course clears what I'm typing and is very frustrating). Might that be why this no longer works in the console?

2. Is there a way to disable the little function definition popup cards that appear (sometimes but not always it seems) when the cursor is in the parentheses after a function name? See screenshot below. I have tried unchecking Editor: Parameter Hints: Enabled but it doesn't seem to have affected them

[juliasilge]

Thanks for sharing these questions!

1. I can definitely reproduce this problem, and I cannot yet identify any recent changes that would have caused this change in behavior. You don't happen to remember around the last time when it did work, do you? Was this a really long time ago, or more recently? It is only Ctrl+N that seems to be the problem; you can map to a different keybinding just fine. I did not get any help from Developer: Toggle Keyboard Shortcuts Troubleshooting; it looked like it was trying to use my user keybinding correctly. I also don't see anything evocative here:

2. Can you double check about how you are setting editor.parameterHints.enabled? I observe that the hover parameter hints do respect that setting. (Also FYI, you can dismiss one of these with Esc.)

[juliasilge]

I'd be interested in more detail on what might be causing the parameter hints to pop up even when disabled. I just played around a bit more, and I did not find that they ever popped up automatically (i.e. without me bring one up on purpose) when they are disabled.

[srhrnkn]

I'll try to notice when it happens - it's inconsistent for sure. Will update if I can figure anything out - thanks.

[srhrnkn]

OK, I think what's going on is that it happens if I choose the function name from the autocomplete menu, but not if I type the full name of the function

[juliasilge]

Ah, thank you! I have opened #9542 to track and prioritize a fix for this. Take a look and see if you have anything additional to add.

[srhrnkn]

That looks right! The other thing I noticed when paying attention to this is that escape does not close the popup in the console like it does in the source file. (The popup after autocomplete thing happens in both)