New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Args out of range #<killed buffer>, 0, 0 #13
Comments
Sorry for taking so long to respond, I have been away on travels. Since I am not experiencing this problem, it would be helpful if you could provide a setup in which I can reproduce this (minimal init.el, emacs version, etc.). To zero in on the problem:
|
Thanks @benma for looking into it. I will definitely try those suggestions this afternoon and post what I get. |
Hi @benma: |
Also, |
In case it helps, I am using:
|
This Emacs and Python version should both work. Since you are seeing the matches when entering the search string, Emacs and Python are able to talk. Please set |
Thanks @benma Below is the trace for a test with
Let me know if there is anything else I can provide or test. |
Seems like your Python interpreter inserts "On GitHub as avazquez@xxx.com" on either stdout or stderr, which messes with the parsing. Can you report the output of Does it contain the "On Github ..." string? If so, is it printed on stdout or stderr (if it is stderr, I can easily write a patch to fix it)? In any case, try to figure out where it comes from and get rid of it ;) I googled for that string but couldn't really find anything. What happens if you use python2 (python2.7.x interpreter) instead of python3? |
Thank you @benma That did it! I removed the line that was printing that string to |
If you don't mind, please update the Stackoverflow post as solved. |
Original post in StackExchange here.
I have been trying to use
visual-regexp-steroids
without luck (a thread on this package can be found here)When I do
vr/replace (C-c p)
, I get a prompt in the minibuffer. I can enter regexps and Emacs shows interactively every match in the buffer. So far so good.The problem comes when I click
RET
and then enter another string (the one I want to replace my matches with). If I now doRET
(to do the actual replacements), I get the following message in the mini-buffer:Why? How can I debug the problem and get it to work?
The text was updated successfully, but these errors were encountered: