GNU bug report logs -
#10053
Wrong use of minibuffer-completion-table in tmm-add-prompt
Previous Next
Full log
View this message in rfc822 format
> Debugger entered--Lisp error: (wrong-type-argument listp closure)
> car(closure)
> mapcar(car (closure (t) (&rest args) (apply (quote
> completion-table-with-predicate) (quote internal-complete-buffer) (quote
> #[257 "\211:\203\n.\211@\202.\211\300\232?\207" ["anything.el"] 3 "\n\n(fn
> NAME)"]) (quote nil) args)))
> tmm-add-prompt()
> #[nil "\301\302\"\210\303 \207" [setup-hook remove-hook
> minibuffer-setup-hook tmm-add-prompt] 3]()
> read-string("Menu bar (up/down to change, PgUp to menu): " nil nil "")
> anything-read-pattern-maybe("Menu bar (up/down to change, PgUp to menu): "
> nil nil noresume nil "")
[...]
> anything-completing-read-default("Menu bar (up/down to change, PgUp to
> menu): " (("a==>Anything" Anything keymap "Anything" (All\ anything\
> commands menu-item "All anything commands"
[...]
> completing-read("Menu bar (up/down to change, PgUp to menu): "
> (("a==>Anything" Anything keymap "Anything" (All\ anything\ commands
> menu-item "All anything commands" anything-execute-anything-command) (Find\
I think the chunks of backtrace above show that the
anything-completing-read-default has a problem: it creates a minibuffer,
like the default completing-read code, but it fails to set
minibuffer-completion-table, which breaks callers such as tmm.
Stefan
This bug report was last modified 13 years and 248 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.