bibretrieve icon indicating copy to clipboard operation
bibretrieve copied to clipboard

Regexp error?

Open adenchfi opened this issue 6 years ago • 6 comments

Hi, Fresh install of AUCTeX and bibretrieve. Upon compile of BibRetrieve, I got some errors about wrong number of arguments to some killbuffer command. Ignoring it, I now get errors on the regexp part:

Wrong number of arguments: #[(regexp &optional internal-too) "Å Æ^X\211^Y\205:^@ @^PÇ^H!\211^Z\2031^@ È\230\2041^@^K\204&^@ ÉHÊU\2041^@Ë^L "\2031^@Ì^H!\210) A\211^Q\204 ^@Æ*\207" [buffer --dolist-tail-- name internal-too regexp buffer-list nil buffer-name "" 0 ...] 4 1800778 "sKill buffers matching this regular
expression: P"], 3

Bibretrieve doesn't seem to work on my work machine, though it seemed fine on my laptop, weirdly enough. EDIT: now it seems to complete the command, but the error still results after, which is workable I suppose. I think it may be the kill buffer command. Here's a better error traceback:

Debugger entered--Lisp error: (wrong-number-of-arguments #[(regexp &optional internal-too) "\305 \306^X\211^Y\205:^@ @^P\307^H!\211^Z\2031^@ \310\230\2041^@^K\204&^@ \311H\312U\2041^@\313^L "\2031^@\314^H!\210) A\211^Q\204 ^@\306*\207" [buffer --dolist-tail-- name internal-too regexp buffer-list nil buffer-name "" 0 32 string-match kill-buffer-ask] 4 1800778 "sKil$ P"] 3) kill-matching-buffers("^bibretrieve-results-" nil t) byte-code("\301 \210\302\303!\210\302\304!\210\305\306^HP\307\310#\207" [bibretrieve-buffer-name-prefix reftex-kill-temporary-buffers reftex-kill-buffer "BibRetrieve Record" "*Ref$ bibretrieve() call-interactively(bibretrieve record nil) command-execute(bibretrieve record) execute-extended-command(nil "bibretrieve") call-interactively(execute-extended-command nil nil)

adenchfi avatar Jun 21 '18 14:06 adenchfi

The function kill-matching-buffers gained a 3rd argument in Emacs 26, I believe, that allows to kill without confirmation. Probably Emacs on your work machine is old.

pzorin avatar Jun 22 '18 10:06 pzorin

Interesting. Is there an easy fix I can do myself? I don't have sudo privileges on my machine, and I tried removing the third argument from the kill-buffers call to no avail

On Fri, Jun 22, 2018, 5:04 AM Pavel Zorin-Kranich [email protected] wrote:

The function kill-matching-buffers gained a 3rd argument in Emacs 26, I believe, that allows to kill without confirmation. Probably Emacs on your work machine is old.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/pzorin/bibretrieve/issues/11#issuecomment-399392260, or mute the thread https://github.com/notifications/unsubscribe-auth/AKHbiM4YvR83ED9jCvl0laKp9U3V1S-9ks5t_MEqgaJpZM4UyM_C .

adenchfi avatar Jun 22 '18 13:06 adenchfi

Have you looked at documentation for kill-matching-buffers on your machine (with C-h f)?

pzorin avatar Sep 01 '18 09:09 pzorin

Also seem to be having this issue. M-x bibretrieve, then input author and title, and get back Wrong number of arguments: (1 . 2), 3. Am I understanding correctly that the fix is to upgrade Emacs to version 26?

godfrey-cw avatar May 02 '19 19:05 godfrey-cw

This error does not affect the main functionality and can be safely ignored. The only possible consequence is that temporary buffers are not killed.

pzorin avatar May 02 '19 19:05 pzorin

Okay, I will safely ignore then!

On Thu, May 2, 2019, 12:40 PM Pavel Zorin-Kranich [email protected] wrote:

This error does not affect the main functionality and can be safely ignored. The only possible consequence is that temporary buffers are not killed.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/pzorin/bibretrieve/issues/11#issuecomment-488804891, or mute the thread https://github.com/notifications/unsubscribe-auth/AJGIXUVQ4DUIULVUTN7SZRDPTM7P7ANCNFSM4FGIZ7BA .

godfrey-cw avatar May 02 '19 22:05 godfrey-cw