SavchenkoValeriy / emacs-powerthesaurus

Powerthesaurus integration for Emacs

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Interacts badly with tramp

bon opened this issue · comments

When using emacs-powerthesaurus while editing a remote file using tramp, something goes wrong in the request

Debugger entered--Lisp error: (wrong-number-of-arguments (6 . 7) 5)
  tramp-make-tramp-file-name("ssh" nil "example.com" "~/" nil)
  request--curl("https://www.powerthesaurus.org/book/synonyms" :parser #f(compiled-function () #<bytecode 0x1e013f1>) :success #f(compiled-function (&rest rest) #<bytecode 0x3d530b1>) :error #f(compiled-function (&rest args2) #<bytecode 0x3d530f1>) :url "https://www.powerthesaurus.org/book/synonyms" :response #s(request-response :status-code nil :history nil :data nil :error-thrown nil :symbol-status nil :url "https://www.powerthesaurus.org/book/synonyms" :done-p nil :settings (:parser #f(compiled-function () #<bytecode 0x1e013f1>) :success #f(compiled-function (&rest rest) #<bytecode 0x3d530b1>) :error #f(compiled-function (&rest args2) #<bytecode 0x3d530f1>) :url "https://www.powerthesaurus.org/book/synonyms" :response #1) :-buffer nil :-raw-header nil :-timer nil :-backend curl :-tempfiles nil))
  apply(request--curl "https://www.powerthesaurus.org/book/synonyms" (:parser #f(compiled-function () #<bytecode 0x1e013f1>) :success #f(compiled-function (&rest rest) #<bytecode 0x3d530b1>) :error #f(compiled-function (&rest args2) #<bytecode 0x3d530f1>) :url "https://www.powerthesaurus.org/book/synonyms" :response #s(request-response :status-code nil :history nil :data nil :error-thrown nil :symbol-status nil :url "https://www.powerthesaurus.org/book/synonyms" :done-p nil :settings #1 :-buffer nil :-raw-header nil :-timer nil :-backend curl :-tempfiles nil)))
  request("https://www.powerthesaurus.org/book/synonyms" :parser #f(compiled-function () #<bytecode 0x1e013f1>) :success #f(compiled-function (&rest rest) #<bytecode 0x3d530b1>))
  powerthesaurus-lookup-word(1 5)
  powerthesaurus-lookup-word-at-point(5)

@bon, thank you for reporting the issue.
I will look into this.

I don't know what has changed, but it seems to be working now.