When I write Python code in a Jupyter Lab cell, often a small window pops up automatically like shown in the screenshot below. When I press enter, it prepends "abs" to "array", so that instead of creating a line break, I get np.absarray([]). As you can imagine, it is a real pain to wait one second for the window to pop up, press Esc, and then insert a linebreak.
I initially thought that this was the "code completion" feature. In the Jupyter Lab settings, under "Code Completion", I set "kernelResponseTimeout": 0, which should disable kernel completion. Unfortunately, this did not change anything. Also, as far as I understood the code completion window should only pop up when I press Tab, which I don't do; it comes up automatically.
My question is therefore: what is this annoying "feature" and how do I get rid of it?
Related
My team has configured ReSharper/Rider to automatically run code-cleanup every time we save. I save a lot, which means code-cleanup runs a lot. Every time I try to Ctrl+Z past a point where code-cleanup ran, Rider prompts me with a pop-up asking if I really want to undo.
Is there a way I can disable this prompt? It's very annoying to move my hand from my keyboard to my mouse every time just to click "yes". I wouldn't have pressed Ctrl+Z in the first place if I didn't want to undo.
To be clear: I'm not trying to disable automatic code-cleanup on save.
I have already tried goolging this question. The only answers I found were about code-cleanup itself, not about disabling the confirmation upon undoing it.
I created a single-window menu scheme using ncurses and got it working.
When I added a second window, I can no longer get my wgetch call to fire (or so it seems).
Somewhat confusing to me is the function prototype :
int wgetch(WINDOW *win);
which says wgetch somehow depends on the window but I don't get the relationship - how does "the window" matter? If it does, and I have more than one window, which one do I use? Also, https://linux.die.net/man/3/wgetch says "There is just one input queue for all windows." which tells me "the window" is a "don't care".
Can someone explain?
Thanks.
The window matters because wgetch refreshes the window before reading characters. That's in the wgetch manual page:
If the window is not a pad, and it has been moved or modified since the
last call to wrefresh, wrefresh will be called before another character
is read.
Each window (including stdscr) may have been altered since the last call to wrefresh. If you make changes in one window without refreshing it, and then call wgetch in another window, the changes to the first window are not automatically displayed. You can use wnoutrefresh to combine refreshes, e.g., using that for the first window and then use the wrefresh done automatically for the second window to refresh both.
I am using Zenity 3.10.2 and any time I use Zenity, regardless of dialog type, the dialog it brings up has focus. i.e. I can straight away press "Enter" straight away and proceed. (I need this ability for automation)
However, there is one exception and it is very difficult to test. It occurs during the KIWI installation of a custom Linux distro and involved a question dialog being created with no focus. Neither enter nor tab have any effect.
There is a bash script which creates this dialog. When I run this in all other contexts, It has focus, but in this install it does not, the cursor appears in random places all around the place. However, from what I can see, the whole point of Zenity is on-top, already focused dialogs.
The actual call to create the dialog is the result of sourcing a file that has the bash script in it i.e. ". ~/.bashrc". Even this approach, always works when I test it manually.
Any ideas as to what could cause a Zenity dialog to be created without focus? Or any way using just Zenity to reclaim / change the focus?
I am aware you can use a window manager such as wmctrl to bring the Dialog to the focus. However this currently not a used package and shouldn't have to do anything else as this is just a simple dialog.
WINDOWMANAGER=/usr/bin/gnome-session
Any guidance would be much appreciated!
I’m currently writing an MFC dialog app which has a menu. The menu displays correctly and the menu entries work correctly via mouse, accelerators, and hotkeys (e.g., to quit: Ctrl+Q or Alt+F,Q).
Unfortunately, the Enter key doesn’t seem to work. That is, pressing Alt+F will open the File menu and pressing ↑ will highlight the Quit entry, but pressing Enter will not select it.
I know that using menus in dialog apps can be a bit tricky, but I’ve done this successfully before. However, that was a long time ago with a customized VS wizard, so I am trying to remember how to do this from scratch. I tried checking my old code, but could not find anything in reference to VK_RETURN. (No, there’s nothing special in PreTranslateMessage.)
These two questions are related, but they want the dialog to receive the key, I need the menu to get it.
Does anyone know what the problem is and how to fix it?
I have a crazy problem on CentOS.
I was doing some editing in emacs when I accidentally hit some keys. Next thing I know, none of my regular keystrokes work.
I wasn't able to close emacs no matter what I tried (mouse on X doesn't work either).
I logged in from another PC and killed the emacs process.
However, this still doesn't fix the problem. Now, when I click my desktop shortcut, I can open another konsole, however, I can't type anything into that console!
When I click on the X to close it, I get this black hand, not the regular arrow.
Further, hitting enter doesn't do anything, and any keystrokes I type don't show up in the terminal.
However, if I type s, the Search heading on the terminal window drops down.
Does anybody know how to get out of this weird mode so I can use my PC again?
EDIT: More information. I think my linux is stuck in something similar to Windows ALT mode. For instance, in Windows, when you hit ALT, followed by F, the File menu will drop down. On my PC, when I hit F, the File menu immediately comes down on the active terminal. However, I cannot for the life of me get out of this mode. Been stuck for over an hour now!!
Hitting the ALT key may have solved the problem. I'm not sure if that was what ended up fixing it, but after I hit the ALT key a bunch of times, I got the VNC display to work properly again.