Bash completion is broken on ubuntu 13.04 #4549

Closed
mkschreder opened this Issue Jan 25, 2014 · 6 comments

Comments

Projects
None yet
4 participants
@mkschreder

Something is wrong with npm bash completion. If I do npm install pack it hangs the whole terminal. I tried removing /etc/bash_completion.d/npm and then it works fine. It's something wrong with that file, unfortunately I have not had time to look into it further.

@mkschreder

This comment has been minimized.

Show comment Hide comment
@mkschreder

mkschreder Jan 25, 2014

Must point out that this hang is really annoying because it can not be canceled by ctrl-c. Have to restart the terminal.

Tested even in the raw console. Same problem.

Must point out that this hang is really annoying because it can not be canceled by ctrl-c. Have to restart the terminal.

Tested even in the raw console. Same problem.

@edi9999

This comment has been minimized.

Show comment Hide comment
@edi9999

edi9999 Jun 16, 2014

Same problem for me, except I have an error that shows up:

npm ERR! Error: ENOENT, open '/usr/share/npm/lib/utils/completion.sh'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.13.0-29-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "completion"
npm ERR! cwd /home/edgar/
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /usr/share/npm/lib/utils/completion.sh
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/edgar/npm-debug.log
npm ERR! not ok code 0

It seems that the completion.sh doesnt exist anymore:

Here is the current structure of /usr/share/npm/lib/utils

.
├── completion
│   ├── file-completion.js
│   ├── installed-deep.js
│   └── installed-shallow.js
├── error-handler.js
├── fetch.js
├── find-prefix.js
├── gently-rm.js
├── is-git-url.js
├── lifecycle.js
├── link.js
└── tar.js

edi9999 commented Jun 16, 2014

Same problem for me, except I have an error that shows up:

npm ERR! Error: ENOENT, open '/usr/share/npm/lib/utils/completion.sh'
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR!     <npm-@googlegroups.com>

npm ERR! System Linux 3.13.0-29-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "completion"
npm ERR! cwd /home/edgar/
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! path /usr/share/npm/lib/utils/completion.sh
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR! 
npm ERR! Additional logging details can be found in:
npm ERR!     /home/edgar/npm-debug.log
npm ERR! not ok code 0

It seems that the completion.sh doesnt exist anymore:

Here is the current structure of /usr/share/npm/lib/utils

.
├── completion
│   ├── file-completion.js
│   ├── installed-deep.js
│   └── installed-shallow.js
├── error-handler.js
├── fetch.js
├── find-prefix.js
├── gently-rm.js
├── is-git-url.js
├── lifecycle.js
├── link.js
└── tar.js
@edi9999

This comment has been minimized.

Show comment Hide comment
@edi9999

edi9999 Jun 16, 2014

Installing with the recommended method (from the readme https://github.com/npm/npm) worked.
Can be closed

edi9999 commented Jun 16, 2014

Installing with the recommended method (from the readme https://github.com/npm/npm) worked.
Can be closed

@othiym23

This comment has been minimized.

Show comment Hide comment
@othiym23

othiym23 Sep 23, 2014

Contributor

Closing as resolved!

Contributor

othiym23 commented Sep 23, 2014

Closing as resolved!

@othiym23 othiym23 closed this Sep 23, 2014

@oshybystyi

This comment has been minimized.

Show comment Hide comment
@oshybystyi

oshybystyi May 4, 2015

Error is present in Ubuntu 14.04. I've sent a mail here with request to update package.

Error is present in Ubuntu 14.04. I've sent a mail here with request to update package.

@oshybystyi

This comment has been minimized.

Show comment Hide comment
@oshybystyi

oshybystyi May 7, 2015

I found out that the problem is not in debian but in ubuntu old package version. (1.3.10 on ubuntu, whereas 1.4.21 on debian).
I am investigating how to solve that for ubuntu distribution.

I found out that the problem is not in debian but in ubuntu old package version. (1.3.10 on ubuntu, whereas 1.4.21 on debian).
I am investigating how to solve that for ubuntu distribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment