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

Minor bug related to buffer-file-name in jedi:call-deferred #54

gbrunick opened this Issue May 17, 2013 · 2 comments


None yet
2 participants

gbrunick commented May 17, 2013

jedi:call-deferred can fail when the string bound to buffer-file-name contains text properties. I would assume that this is because the lisp representation of the string becomes much more complicated and brakes the RPC mechanism. Now buffer-file-name probably should not contain text properties in the first place, but I had a custom piece of code that did this accidentally and this broke jedi-emacs. I would assume that the solution is as simple as replacing buffer-file-name with (substring-no-properties buffer-file-name) which is a small price to pay for a little more robustness.

This is a great piece of code. Thanks.

@tkf tkf closed this in ba59fa8 May 17, 2013


This comment has been minimized.


tkf commented May 17, 2013

Thanks. This should be fixed by the latest commit. Please check.


This comment has been minimized.

gbrunick commented May 17, 2013

Works for me now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment