search

yadex205 / consult-ag

The Silver Searcher integration for GNU Emacs using Consult
MIT License
7 stars 6 forks source link

`wrong-type-argument buffer-or-string-p t` when selecting a match #2

Open ft opened 2 years ago

ft commented 2 years ago

When running consult-ag, presenting searches works perfectly well. However when I hit Enter to select a match to go to that position, I get a wrong-type-argument error. When enabling debug-on-error I get this backtrace:

Debugger entered--Lisp error: (wrong-type-argument buffer-or-string-p t)
  consult-ag--grep-position(t #f(compiled-function (&optional name) #<bytecode -0xd9c7602ea9be80b>))
  #f(compiled-function (action cand) #<bytecode 0x1d8a882c9a6812eb>)(#("ROADMAP.org:47:51:ers may decide to rather impleme..." 0 11 (filename "ROADMAP.org" row "47" column "51" face consult-file) 11 12 (filename $
  #f(compiled-function () #<bytecode -0x6e760d6a5ea07ba>)()
  consult--with-preview-1(any #f(compiled-function (action cand) #<bytecode 0x1d8a882c9a6812eb>) #f(compiled-function (input cand) #<bytecode 0x1a6b6dd330dca502>) #f(compiled-function (&rest args2) #<bytecode 0x7$
  consult--read-1(#f(compiled-function (action) #<bytecode 0x19883e7d2866da7c>) :prompt "Consult ag:  (Project makemehappy): " :lookup consult--lookup-member :state #f(compiled-function (action cand) #<bytecode 0$
  consult--read(#f(compiled-function (action) #<bytecode 0x19883e7d2866da7c>) :prompt "Consult ag:  (Project makemehappy): " :lookup consult--lookup-member :state #f(compiled-function (action cand) #<bytecode 0x1$
  consult-ag()
  funcall-interactively(consult-ag)
  command-execute(consult-ag)

This is happening consult-ag with this version information on top of consult-ag.el:

;; Author: Kanon Kakuno <yadex205@outlook.jp>
;; Homepage: https://github.com/yadex205/consult-ag
;; Package-Requires: ((emacs "27.1") (consult "0.16"))
;; Package-Version: 20220419.1721
;; Package-Commit: 2460ae6829e86c9f1186a852304d919526838cb8
;; SPDX-License-Identifier: MIT
;; Version: 0.1.2
ft commented 2 years ago

Not sure if this is a compatibility issue, but I reinstalled all of my package.el based packages from scratch, and now the issue is gone. Unfortunately I did not check the consult version I had installed before. Now it's 20220508.928 from melpa.