Completion causing command line to disappear

[OliverJAsh]

I have an npm script called watch. When I use npm's tab completion, e.g.:

$ npm run wat<tab>

The autocompletion works, but my command line disappears and only the completed text is shown:

ch

Versions:

$ zsh --version
zsh 5.2 (x86_64-apple-darwin15.4.0)

$ npm --version
3.9.3

[OliverJAsh]

Any ideas on this one?

[busches]

@OliverJAsh are you still seeing this? Have you tried bash or any other terminal? The problem does not exist on Windows with clink in 3.10.5.

[OliverJAsh]

Just tried and I can't reproduce in bash… hmm!

[busches]

But the latest version of npm still fails in zsh?

[OliverJAsh]

Tested with npm 3.10.3 which ships with latest Node stable I believe (6.6.0)

On Thu, 22 Sep 2016 at 14:02 Scott Busche notifications@github.com wrote:

But the latest version still fails in zsh?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#13047 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA4QCbr2_otQy5GceQ2C7yzE-jr5jpy-ks5qsnxqgaJpZM4I1F-J
.

[busches]

Is it only the run scripts autocompletion causing the error or does tabbing
on npm r to complete run also cause an issue?

On Thu, Sep 22, 2016 at 8:30 AM, Oliver Joseph Ash <notifications@github.com

wrote:

Tested with npm 3.10.3 which ships with latest Node stable I believe
(6.6.0)

On Thu, 22 Sep 2016 at 14:02 Scott Busche notifications@github.com
wrote:

But the latest version still fails in zsh?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#13047 (comment), or
mute
the thread
<https://github.com/notifications/unsubscribe-
auth/AA4QCbr2_otQy5GceQ2C7yzE-jr5jpy-ks5qsnxqgaJpZM4I1F-J>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#13047 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA0WZL7GL47L1vyNUP5EXNHlkNDb7R6Zks5qsoMAgaJpZM4I1F-J
.

[OliverJAsh]

• If I tab npm r, my command disappears for a second and then comes back
  with a list of options beneath (rebuild, remove, run, etc.)
• If I tab npm ru, my command disappears and then npm complete kicks in, leaving my command line with onlyn`
  So I believe it's a general problem with npm autocompletion

It only happens the first time I try to using npm completion after opening
a shell. It is fine the second time round. That said, it's not rare for me
to be opening/closing shells frequently.

On Thu, 22 Sep 2016 at 14:59 Scott Busche notifications@github.com wrote:

Is it only the run scripts autocompletion causing the error or does tabbing
on npm r to complete run also cause an issue?

On Thu, Sep 22, 2016 at 8:30 AM, Oliver Joseph Ash <
notifications@github.com

wrote:

Tested with npm 3.10.3 which ships with latest Node stable I believe
(6.6.0)

On Thu, 22 Sep 2016 at 14:02 Scott Busche notifications@github.com
wrote:

But the latest version still fails in zsh?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#13047 (comment), or
mute
the thread
<https://github.com/notifications/unsubscribe-
auth/AA4QCbr2_otQy5GceQ2C7yzE-jr5jpy-ks5qsnxqgaJpZM4I1F-J>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#13047 (comment), or
mute
the thread
<
https://github.com/notifications/unsubscribe-auth/AA0WZL7GL47L1vyNUP5EXNHlkNDb7R6Zks5qsoMAgaJpZM4I1F-J

.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#13047 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA4QCSloSxVLb8j4-n3vru3mmrei0H44ks5qsomvgaJpZM4I1F-J
.

[npm-robot]

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

For more information about our new issue aging policies and why we've instituted them please see our blog post.