Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Bug#630987: Tab-completion is totally broken

23 views
Skip to first unread message

Juhapekka Tolvanen

unread,
Jun 19, 2011, 11:00:02 AM6/19/11
to

Package: zsh
Version: 4.3.12-1
Severity: important

Whenever I hit the Tab-key, all I get is this:

(eval):2: bad set of key/value pairs for associative array
_main_complete:126: command not found: [@][@]
_main_complete:165: command not found: _complete[@]
_main_complete:186: bad output format specification

Problem is the same in zsh-beta.

If you want to see my zsh-configs, you can get them here:

http://iki.fi/juhtolv/configs/shellrc/


-- System Information:
Debian Release: wheezy/sid
APT prefers stable
APT policy: (990, 'stable'), (500, 'testing-proposed-updates'), (500, 'stable-updates'), (500, 'proposed-updates'), (102, 'testing'), (101, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.39-2-686-pae (SMP w/1 CPU core)
Locale: LANG=fi_FI.utf8, LC_CTYPE=fi_FI.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages zsh depends on:
ii libc6 2.13-7 Embedded GNU C Library: Shared lib
ii libcap2 1:2.21-1 support for getting/setting POSIX.
ii libncursesw5 5.9-1 shared libraries for terminal hand

Versions of packages zsh recommends:
ii libc6 2.13-7 Embedded GNU C Library: Shared lib
ii libpcre3 8.12-3 Perl 5 Compatible Regular Expressi

Versions of packages zsh suggests:
ii zsh-doc 4.3.12-1 zsh documentation - info/HTML form

-- Configuration Files:
/etc/zsh/zprofile changed:

. /etc/profile


-- no debconf information

--
Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv
"Quidquid Latine dictum sit altum videtur."

--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Axel Beckert

unread,
Jun 21, 2011, 10:30:02 AM6/21/11
to
tag 630987 + moreinfo
kthxbye

Hi Juhapekka,

Juhapekka Tolvanen wrote:
> Package: zsh
> Version: 4.3.12-1
> Severity: important
>
> Whenever I hit the Tab-key, all I get is this:
>
> (eval):2: bad set of key/value pairs for associative array
> _main_complete:126: command not found: [@][@]
> _main_complete:165: command not found: _complete[@]
> _main_complete:186: bad output format specification

Hmmm, I also had issues when hitting Tab directly after installation,
but only in still running 4.3.11 shells. Newly started 4.3.12 shells
worked fine.

Can you confirm that this happens also in newly created shells?

> If you want to see my zsh-configs, you can get them here:
>
> http://iki.fi/juhtolv/configs/shellrc/

Thanks. That may help later with debugging the issue.

Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5

Frank Terbeck

unread,
Jun 21, 2011, 10:40:02 AM6/21/11
to
Axel Beckert wrote:
[...]

>> http://iki.fi/juhtolv/configs/shellrc/
>
> Thanks. That may help later with debugging the issue.

Actually, what I'd be way more interested in, is if the zsh defaults
plus compsys trigger the problem, too:

% zsh -f
% autoload -Uz compinit
% compinit

...and then, in that fresh shell (after the compinit call), retry.

If that *still* yields the problem then the problem is not with your
setup and I'd bet on compcache being the culprit. Then you'd

% rm ~/.zcompdump

...and retry.

If the problem is caused by your configuration (which I doubt, if it
worked with 4.3.11), then we'd need a minimal example that triggers the
problem.

Regards, Frank

Juhapekka Tolvanen

unread,
Jun 21, 2011, 12:30:02 PM6/21/11
to

On Tue, 21 Jun 2011, +17:53:52 EEST (UTC +0300),
Frank Terbeck <f...@bewatermyfriend.org> pressed some keys:

> Axel Beckert wrote:
> [...]
> >> http://iki.fi/juhtolv/configs/shellrc/
> >
> > Thanks. That may help later with debugging the issue.
>
> Actually, what I'd be way more interested in, is if the zsh defaults
> plus compsys trigger the problem, too:
>
> % zsh -f
> % autoload -Uz compinit
> % compinit
>
> ...and then, in that fresh shell (after the compinit call), retry.

In that case problem do not appear.

> If that *still* yields the problem then the problem is not with your
> setup and I'd bet on compcache being the culprit. Then you'd
>
> % rm ~/.zcompdump
>
> ...and retry.

I moved that file to other name and started a new shell in my normal
way. In that case problem still appeared.

> If the problem is caused by your configuration (which I doubt, if it
> worked with 4.3.11), then we'd need a minimal example that triggers the
> problem.

Yes, there may be something wrong with my configs.


--
Juhapekka "naula" Tolvanen * http colon slash slash iki dot fi slash juhtolv
"Quidquid Latine dictum sit altum videtur."

--

0 new messages