Package: emacs-goodies-el
Version: 35.2
Severity: normal

Somewhere between emacs23 and emacs24, the shell-command-completion-mode stopped
working as it should.

Behavior in stock emacs24:

If I launch a clean emacs with "emacs -Q", and then run shell-command (M-!), I
get a prompt in the minibuffer, asking me for the command to run. In emacs24,
tab-completion works here, and the current directory is displayed in the prompt.


With (shell-command-completion-mode):

If I launch a clean emacs, and then eval the following from emacs-goodies-el:

(load-library "shell-command")
(shell-command-completion-mode)

Now, M-! prompt shows the current directory, however the tab-completion no
longer works. If I press [tab] after partially entering a command, I get the
error

apply: Wrong number of arguments: (3 . 4), 5

in the minibuffer. This works OK in emacs23.



In both emacs23 and emacs24, completion works with or without this mode; the
only difference is the directory displayed in the prompt. Maybe the completion
functionality should be removed from goodies, and just the prompt change should
remain.






-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Shell: /bin/sh linked to /bin/dash

Versions of packages emacs-goodies-el depends on:
ii  bash                            4.2-2
ii  dpkg                            1.16.4.2
ii  emacs-snapshot [emacsen]        2:20121018-1
ii  emacs-snapshot-lucid [emacsen]  2:20121018-1
ii  emacs23 [emacsen]               23.4+1-3
ii  install-info                    4.13a.dfsg.1-10

Versions of packages emacs-goodies-el recommends:
pn  dict      <none>
ii  perl-doc  5.14.2-11
ii  wget      1.13.4-3

emacs-goodies-el suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to