1

I have an issue with copy and paste from or to Emacs (GUI); as precised in the title, I'm using Windows 7. The Emacs version is 25.1.1

kill and yank are working properly though ; to copy or paste, I have to use the mouse, which is annoying.

I have nothing special in my .emacs file, I added the following lines but nothing has changed :

(setq select-enable-primary t)
(setq select-enable-clipboard t)
(setq save-interprogram-paste-before-kill t)

thanks in advance for your insights.

Improve this question
1
  • It's not clear to me what behavior you are seeing. When you copy from another Windows application and then switch to Emacs and yank, it does not work? But there is something you can do with the mouse that /does/ work? You should try running emacs with -Q and see if the problem persists, otherwise it is likely an issue in your .emacs file. Note that I have the Emacs 25.1.1 defaults for all the variables you mention and Windows clipboard works as I expect.
    – glucas
    Commented Apr 11, 2017 at 18:53

2 Answers 2

Reset to default
1

I use simpleclip, there is a short explanation on the github page for what may be going on:

https://github.com/rolandwalker/simpleclip

I bind simpleclip-paste to f9 f9

Improve this answer
2
  • thanks, I've tried but it does not do the trick...
    – loukios
    Commented Apr 10, 2017 at 21:38
  • What didn't work? simpleclip works for me on Windows 7. Note I have to use Ctrl-Insert as the key-press to copy, since Super-C is intercepted by the OS. This is using the default key bindings.
    – InHarmsWay
    Commented Apr 20, 2017 at 11:15
0

I am not sure whether it is really caused by Windows OS. I am using Win7 and simple.el to support the basic copy, cut and paste operations, which work quite well. And my recommendations are:

  • key binding: try "C-h k", and press the key you bind to paste or copy operations (by default, it is "C-y"), to test whether your key binding is correct.
  • package error: turn the debug with "toggle-debug-on-error", and run the copy functions. By looking at the backtrace, you will probably find errors out. Based on your describing, it is less likely to be a function error.
Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.