From: Eric Cook <llua@gmx.com>
To: zsh-workers@zsh.org
Subject: Re: BUG: Zsh crashes
Date: Fri, 13 Jan 2017 23:08:34 -0500 [thread overview]
Message-ID: <155b81e2-7199-e2e5-1d11-628df66492ca@gmx.com> (raw)
In-Reply-To: <20170113175242.16210658@pwslap01u.europe.root.pri>
On 01/13/2017 12:52 PM, Peter Stephenson wrote:
> You always need to report both the zsh version and, in the case of
> completion crashes, how this is set up (looks like in your case this is
> down to oh-my-zsh so I guess you don't have explicit details of your
> own setup beyond that).
With less steps:
curl https://raw.githubusercontent.com/robbyrussell/oh-my-zsh/3705d47bb3f3229234cba992320eadc97a221caf/plugins/rust/_rust > /path/in/fpath/_rust
autoload -Uz _rust; compdef _rust rustc
rustc --pretty flowgraph==<^I>
The interesting parts of _complete_debug
```
+_description:109> return 0
+_next_label:19> set -A expl -M 'm:{[:lower:][:upper:]}={[:upper:][:lower:]} r:|[._-]=** r:|=* l:|=*' -J arguments -X 'Completing <F0>&8^A'
+_next_label:22> return 0
+_values:147> '`' -M 'm:{[:lower:][:upper:]}={[:upper:][:lower:]} r:|[._-]=** r:|=* l:|=*' -J arguments -X 'Completing <F0>&8^A' '>2^A'
_values:147: command not found: `
+_values:146> _next_label arguments expl '<F0>&8^A'
+_next_label:3> local __gopt __descr __spec
+_next_label:5> __gopt=( )
+_next_label:6> zparseopts -D -a __gopt 1 2 V J x
```
and
```
+_description:13> [[ -n files ]]
+_description:13> _lastdescr=( '' TYPE NODEID files directories '<F0>&8^A' files )
+_description:15> zstyle -s :completion::complete:rustc:argument-1:argument-1 group-name gname
+_description:16> [[ -z '' ]]
+_description:16> gname=argument-1
+_description:18> _setup argument-1 argument-1
```
There are a few other places where the control characters show up but i am not sure what is creating it.
I can get zsh to crash by adding a space before _values on line 52 of the completer.
next prev parent reply other threads:[~2017-01-14 4:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170113174208epcas1p109452434d2f95e52b24e49029ce15943@epcas1p1.samsung.com>
2017-01-13 17:40 ` Bjorn Baron
2017-01-13 17:52 ` Peter Stephenson
2017-01-14 1:09 ` Phil Pennock
2017-01-14 2:48 ` Daniel Shahaf
2017-01-14 20:19 ` Peter Stephenson
2017-01-14 20:36 ` Peter Stephenson
2017-01-14 22:10 ` Peter Stephenson
2017-01-14 22:12 ` Bart Schaefer
2017-01-15 2:32 ` Daniel Shahaf
2017-01-14 4:08 ` Eric Cook [this message]
2017-01-14 4:18 ` Eric Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=155b81e2-7199-e2e5-1d11-628df66492ca@gmx.com \
--to=llua@gmx.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).