#CTRL C DOESN T WORK SOFTWARE#

#CTRL C DOESN T WORK SOFTWARE#

What a huge oversight, having Microsoft Word try to impose a shortcut from Macs (as it seems) to longtime Windows users (especially when other software the user works with use other set of shortcuts for copy-paste). Wonder why Microsoft didnвЂ™t add both the old and new shortcuts there, since it seems the dialog does support it. Now, from the right box select the following Command: EditCopy Look at the 'Current Keys' Box you will see 'Ctrl+Insert' which is the NEW mapping now put your cursor in the 'Press new shortcut key' and Press Ctrl+C, a button on the bottom named Assign will light up, and you click on it.Дo the same for all the shortcuts you like, such as EditPaste, EditUndo, EditRedo, EditCut, SelectAll etc. On the Categories box, scroll until you find 'All Commands' and select it. To 'restore' word to the way you remember, you need to go to, File->Options->Customize Ribbon On the bottom there is a label 'Keyboard Shortcuts' and a button 'CustomizeвЂ¦' вЂ“ click it Today had enough so after some Google search on it, found the best fix by Moshe Eschel at: So I had to move my fingers far away to SHIFT+INSERT to paste. I would press CTRL+C at some other software and then would press ALT+TAB to go into an open Word document and press CTRL+V to paste, but it would not. For some time now, I was getting very annoyed while copy-pasting content from other software into Microsoft Word 2010. I use xinit through cdm to launch x - here is my. Option 'AccelMethod' 'EXA' # or XAA, EXA, XAA more stable, XAA is deafult Option 'EnablePageFlip' 'on' #Faster than default (off) Option 'SWcursor' 'off' #Faster than default (on) Option 'AGPFastWrite' 'on' #Faster than default (off) Option 'XkbOptions' 'terminate:ctrl_alt_bksp' ДЇontPath '/usr/share/fonts/100dpi:unscaled'ДЇontPath '/usr/share/fonts/75dpi:unscaled' The easiest to understand explanation of 'trap' that I have found is at. If 'trap' returns 'SIGINT' or '^C', you will have to find the program that is setting the trap. Then try 'Ctrl-C'.ДЄlso try the command 'trap', with no arguments.

I suggest you set 'intr' to Ctrl-C with the 'stty' command. $ # but the command carries through to the end. $ # What Ctrl-C, or any keypress, does to a ping command is erratic, $ # Ctrl-C just leaves the cursor on this line. XDG_DATA_HOME=/home/arachnid92/.local/share XDG_DATA_DIRS=/usr/share/:/usr/local/share/ XAUTHORITY=/var/run/gdm/auth-for-arachnid92-v6v3EV/database PATH=/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/usr/bin/vendor_perl:/usr/bin/core_perl:/opt/qt/bin I say GUI, because everything works excellent in my TTY's.ДBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-1CFKmBu3kT,guid=31f1162b7b8110b9933758a900000038 I'll report back in a while.Д®DIT: Nope, even with default keymap options, ^C does not work in GUI. Still, now I'm going to try reverting all keyboard changes to default, and see if that helps. But I did try removing the SetXKbmap option from my xorg config, and setting the keymap using rc.conf and nf instead. I thought it might be what you suggest, but after checking out all my settings, I couldn't find any conflicting layouts. Hopefully this is the same problem that you're having, and hopefully it'll fix it for you.Д®ven better if the root of this bug is found and patched. If I have USA Dvorak keyboard layout as being the 1st layout in the list, and USA as the 2nd layout in the list, but have USA as the current layout, then to send a Ctrl+C to the GUI terminal I would have to press 'Ctrl + i' (an 'i' in USA is 'c' in USA Dvorak). Move your preferred keyboard layout to be at the top of the list in the keyboard layout options in your GUI of choice.

It's difficult to explain, so to fix it you'll need to:

If you do have 2 different keyboard layouts configured, and you're using the 2nd keyboard layout (as can be found in the keyboard layout GUI in gnome / whatever you use), then the Ctrl key sequences will only work if you are using the 1st keyboard layout (even if the active keyboard layout is the 2nd layout). I've come across this problem before, for me it was because I was using 2 different keyboard layouts.

Ctrl c doesn t work