The whole program is erasing text when I type inbetween something, I can't figure out how to disable this. Previous answers were unhelpful since my keyboard has neither an insert key or a numpad, so I'm not sure how this accidentally happened. There must be some shortcut I accidentally pushed and can't find.
I tried searching the settings of jupyterlab and couldn't anything relevant to disable this typing mode
EDIT: An onscreen keyboard fixed the issue, but I'm wondering what setting in jupyterlab had this enabled
Related
I've been dying to get this working on the default terminal on the mac, this feature is really useful when you write something wrong, and can just cmd + backspace to delete all the lines.
I googled online several times but I couldn't find anything related to this.
Well, the functionality is already there: ⌃+U will delete everything left to your cursor to the beginning of the line. You cannot, however, change this keyboard shortcut.
You can change application-specific keybindings by installing additional tools like, for example, Karabiner.
Alternatively, you can install iTerm2 as a Terminal replacement. That will allow you to enable this - and many other text editing keybindings - with one click in the settings.
I am just install Octave 4.2.0 in Windows 10 and try to do some Machine Learning exercises. I notice that I can't paste the normal clipboard content to the Octave.
Does anyone else have this issue? If so, any work around? Or is it just bug in the program?
Although your description doesn't indicate the exact place you're trying to paste contents into, there were a couple bugs around the time of Octave 4.2 specifically related to this problem. See:
bug #51095: editor doesnt allow paste of exisiting clipboard data
and
bug #52361: Ctrl-C/Ctrl-V only works reliably if executed as very first action
both bugs have since been patched and closed (around version 4.4), and reports seem to indicate that the problem has not resurfaced in later versions. Anyone experiencing similar issues in a recent version of Octave (v5.2.1 as of today) should either comment on one of those closed bug reports or create a new one at https://bugs.octave.org
Run >> preferences, and in the Shortcuts tab, untick the option at the top "Disable global shortcuts when Command Window has focus". (I don't know since what version it is there.)
If you disable global shortcuts, Ctrl-V (for paste) is disabled because it is a Windows thing.
If you do not disable them, Ctrl-V will work. So will Ctrl-C to copy text, but it will also still work to abort an execution.
If you click on the icon in the title bar on the top left corner of the
window, you'll get an edit option, and you can choose to mark (choose
the text to copy), copy, and paste from there.
Earlier I could delete a selected text with delete key in my mac. Now I have to delete it using "shift" + "delete"."delete" deosn't work anymore
Also when I selected a text and delete it, I cannot use arrow keys to move the cursor. It keeps selecting the texts while I move the cursor. I cannot type anything also. I have to press esc key and exit select mode and then type. Also while I'm typing if I press esc key, the cursor turns to a block. Then I cannot type anything. But all the character keys does some weird stuff. Like goes to the bottom of the file.
When I press the key "s", the cursor turns back to the "|" and I can type again.
Please give me some advise. I already tried changing the keymaps, restarting the keymaps, Completely cleaning intellij and reinstalling.
Ok. I figured it out. Vim emulator is the one giving problems. You can disable vim emulator in Tools menu. Then the keyboard works normally.
I don't know what key combination I did, but now each time I click somewhere in the page, Visual Studio selects the text between first and second mouse click.
I tried to escape from this "selection mode", but nothing helps, nor Escape, nor left clicks, nor Ctrl+Up/Down.
I opened another VS window and there is all right - normal selection.
What is it, how to cancel it, what is it for?
I should probably restart Visual Studio. I remember that that happened some times ago in VS 2005. Very annoying VS "feature".
P.S. It disappeared as suddenly as it appeared, but I found similar problem described here. The guy says that "The only way to stop is to press escape or shift and an arrow key."
I have very often the same issue, just after stopping the debugger. No idea how it starts... But I found the key combination to stop it: Press "Alt Gr"+"Ctrl(right)"+"Shift(right)"
I figured out how to turn this issue on and off:
Just press the ins (Insert) key; If you're using a full sized keyboard it will be to the right of backspace and above delete or if you're using a smaller keyboard it'll be the second option of zero key on the number pad to the right of the right arrow key.
Click on tools and then options. Under environment select keyboard. Then there will be a window open up with options. The first drop down says something about mapping. Set that to default.
Brief, if this was previously selected, is an old DOS format and the key bindings will cause similar actions.
I have experienced the same problem (VS 2010). Here is what happens:
I start the debugger on a project whith Unmanaged debugging enabled. When I try use the key combination Ctrl+Shift+L to delete a line I get a dialog saying 'Changes are not allowed when unmanaged debugging is enabled'. The title of the dialog is 'Edit and Continue'. When the dialog is closed the editor gets stuck with this behavior:
Shift+Right-Click behavior: It selects the text between the cursor and the position of the mouse-click
Ctrl+Scroll behavior: If I try to scroll using the mouse wheel it will zoom in or out instead.
It behaves like the Shift and Ctrl keys are being held down.
I have found these key combinations that will get me out of this situation:
Shift + Arrow down
Ctrl + Arrow down
Until I discovered this I had to restart Visual Studio.
Use the (insert) Key in the Key board.
I have this issue when I VPN to a machine running VS. Here is the key combination I have found to get me out of this state. I do a ctrl-f to open the find window. I type some characters in the find textbox and I notice that the letters are all capital (even though I did not set the caps lock). I hit the caps lock key and test using the find text box to make sure my caps lock is not set (lowercase). Once the lowercase is set, the selecting text between mouse clicks behavior goes away. Don't know why, but this works for me.
I just got into the office, and booted up my computer to work on my current project.
I hopped into a class file, and selected (through mouse highlighting) a group of events to delete.
What happened though was it only erased one character. Wondering what happened, I clicked at the beginning of the selection and re-highlighted the text to delete it again.
So i just clicked randomly in the middle of the file, and it highlighted from the beginning of the first selection all the way to where I clicked in the middle.
I have rebooted both VS, the computer and insured that sticky keys and all other "accessibility" software was turned off.
UPDATE
When I click shift and try to manually highlight with my arrow keys, the cursor doesn't even move.
UPDATE
When I click escape from the selection it goes to the search drop down:
alt text http://img69.imageshack.us/img69/9591/searchbox.png
The same thing happened to me, I held down the shift key for a few seconds then while still holding it down I clicked anywhere in the open page in Visual Studio, and voilá, my mouse click was back to normal.
I imagine I had unwittingly activated some kind of keyboard shortcut but not sure which
I had this same problem too. I believe I found the solution: check your keyboard options.
Go under tools -> options, under the Environment subtree, click 'Keyboard'. Then, you will see a dropdown with the label "Apply the following additional keyboard mapping scheme". If you select "Brief" from this, you get the keyboard behavior as described. I'm not exactly sure what "Brief" refers to, but it certainly isn't familiar to me.
Change the keyboard layout back to (default) or another one to get the behavior you expect.
Reinstalled VS and now everything is better.