Skip to content
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

ivy-read: Wrong type argument: symbolp, "Completion conflict history" #2

Closed
dalanicolai opened this issue Jan 21, 2021 · 6 comments · Fixed by #5
Closed

ivy-read: Wrong type argument: symbolp, "Completion conflict history" #2

dalanicolai opened this issue Jan 21, 2021 · 6 comments · Fixed by #5

Comments

@dalanicolai
Copy link

The unquoted symbol emacs-conflict--conflict-history in the function emacs-conflict--pick-a-conflict causes errors in Spacemacs when using Helm or Ivy. Quoting the symbol solves the error when using Ivy, but not when using Helm. Removing the symbol fixes functionality for both Ivy and Helm.
As it appears that this symbol does not add functionality, it might be better to just remove it.

@kasteph
Copy link

kasteph commented Jan 24, 2021

I can confirm that this is also an issue in doom when using Ivy and with helm, I get the following:

In ‘emacs-conflict-resolve-conflicts History’ source: ‘#[0 \304\302\300\305\303$\211\205�\0\306\307\310\301�""\207 [nil nil Completion conflict history t helm-comp-read-get-candidates nil delete  helm-cr-default] 6]’ 
 (wrong-type-argument listp "Completion conflict history")

@felixwiemuth
Copy link

In Spacemacs with helm, I'm getting the same as @stephsamson. Removing the emacs-conflict--conflict-history in emacs-conflict--pick-a-conflict also works for me.

@ibizaman
Copy link
Owner

ibizaman commented Apr 23, 2021

Thanks all for the report. I don’t have much time to fix this these days but I’ll get to it eventually. In the meantime I’m happy to accept a PR. :)

Actually I'm working on it and can reproduce.

@ibizaman
Copy link
Owner

ibizaman commented Apr 23, 2021

I'm using ivy and the linked comment fixes the issue. Can anyone check it by checking out the branch?

The easiest way is changing the branch here:

(use-package emacs-conflict
  :straight (emacs-conflict :type git :host github :repo "ibizaman/emacs-conflict" :branch "fix_wrongtypeargument"))

Then you will need to evaluate the following elisp code to clear the variable:

(setq emacs-conflict--conflict-history nil)

ibizaman added a commit that referenced this issue Jun 1, 2021
@ibizaman
Copy link
Owner

ibizaman commented Jun 1, 2021

I went on and merged the PR to avoid keeping this issue ope for too long. Feel free to reopen if there are issues with it.

@felixwiemuth
Copy link

Thank you! I updated to current the master (f4b8358) and the basic emacs-conflict-resolve-conflicts works now without problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants