-
-
Notifications
You must be signed in to change notification settings - Fork 7.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sort
command not found
#1227
Comments
What does |
Hey there, I'm on Linux Mint (Ubuntu 14.04). Yes, it is available - see the |
What about |
command sort needed to be ctrl-c'd |
I'm using version v0.30.1 I tried:
But it didn't help :-/
|
So I found a work around. This code was in a called script. #!/bin/bash
blah
../../deploy-some-apps.sh blah blah blah Then the error happened in
But if I moved the
and
Anyways, thanks for nvm. It's cool. |
Glad you figured it out - not sure why it wasn't working :-/ |
I'm crap at bash, but thinking about it, the environment wasn't getting passed to nvm (PATH to sort). So probably changing |
getting this in v0.32.0 as well. Is there a v0.32.1 coming with this fix in tow? |
@artlawry there's no fix yet, since we're still not sure what the problem was. What's your |
This is all on a MacBook Air recently restored to factory and upgraded to Sierra - I'm unsure if this is related to Sierra as I had installed nvm and autoenv a good deal ago on El Capitan before this. I'm using autoenv (runs nvm use on cd), digging into what the actual nvm command it executes is cd control
Found '/Users/alawry/dev/brighttag/ui/control/.nvmrc' with version <v5.7.1>
-bash: sort -t. -u -k 1.2,1n -k 2,2n -k 3,3n: command not found
Version 'v5.7.1' not found - try `nvm ls-remote` to browse available versions. here's proof that v5.7.1 is on my system: $ nvm use
Found '/Users/alawry/dev/brighttag/ui/control/.nvmrc' with version <v5.7.1>
Now using node v5.7.1 (npm v3.6.0) Debug information: $ nvm debug
nvm --version: v0.31.7
$SHELL: /bin/bash
$HOME: /Users/alawry
$NVM_DIR: '$HOME/.nvm'
$PREFIX: ''
$NPM_CONFIG_PREFIX: ''
nvm current: v5.7.1
which node: $NVM_DIR/versions/node/v5.7.1/bin/node
which iojs:
which npm: $NVM_DIR/versions/node/v5.7.1/bin/npm
npm config get prefix: $NVM_DIR/versions/node/v5.7.1
npm root -g: $NVM_DIR/versions/node/v5.7.1/lib/node_modules $ which sort
/usr/bin/sort $ type sort
sort is /usr/bin/sort $ command sort
^C had to |
Hmm, I haven't tested on Sierra yet since I'm still on El Cap everywhere. I don't understand why |
will do |
I've been struggling with this for weeks. From what I can tell, what is happening in this command:
is that I'm not entirely sure //why//, but that seems to be the case. I solved this for //me// (probably not portable to all supported shells) by changing
Not making a pull request because I don't think it's portable, but maybe this will help track down the issue? |
@aegarbutt can you open a new issue with your problem, and fill out the issue template? my first suspicion is that you're using zsh and have an interesting zsh option set, but let's flesh that out independently :-) |
Will do.
(Nope, bash from homebrew)
|
I'm running into this on our linux CI server. I don't see any resolution or a follow up issue from @aegarbutt Was there any resolution ? |
@apsoto nope; please file an issue and fill out the template |
Hi, I actually found the source of the problem. I'm using 'bash strict mode'.
The change of the field separator from space to I worked around it by setting the
You still need a separate issue since this ticket is what google sent me to when I searched for the same error? |
(I thought I had sent an email response in finding my problem, but I apparently did not.) My root cause was an IFS leakage from my bash config. Never actually determined why it only seemed to impact |
@aegarbutt because @apsoto yes, a separate issue about IFS would be great, just because this thread is so long (but it appears that was the OP's issue too) |
Fixes nvm-sh#1227. Fixes nvm-sh#1244. Fixes nvm-sh#1514. Fixes nvm-sh#1518.
Hi, I'm getting this error:
From this script:
Any suggestions?
The text was updated successfully, but these errors were encountered: