Skip to content
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.

Sign up for GitHub

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

Jump to bottom

scripts/environment-project: line 67:  [: command not found #89

Closed
hohwille opened this issue Apr 8, 2019 · 4 comments
Closed

scripts/environment-project: line 67:  [: command not found #89

hohwille opened this issue Apr 8, 2019 · 4 comments
Labels
bash related to bash shell or scripts bug Something isn't working help wanted Extra attention is needed scripts related to shell scripts (bash and CMD) windows specific for Microsoft Windows OS
Milestone
release:3.2.0

Comments

@hohwille
Copy link
Member

hohwille commented Apr 8, 2019

Since a while I see this error.

scripts/environment-project: line 67:  [: command not found

Usually this is some kind of syntax error in the bash scripts (e.g. as missing space between if and the opening bracket for the condition). However, I seem to be blind and can not spot the error in the script:
https://github.com/devonfw/devon-ide/blob/b3bdaf0dcdf4d05d86fd020076c69f06e9449490/scripts/src/main/resources/scripts/environment-project#L67

Any hint would be very welcome.
@hohwille hohwille added bug Something isn't working help wanted Extra attention is needed scripts related to shell scripts (bash and CMD) labels Apr 8, 2019
@hohwille hohwille added this to the release:3.0.0 milestone Apr 8, 2019
@hohwille hohwille added bash related to bash shell or scripts windows specific for Microsoft Windows OS labels Apr 8, 2019
@hohwille
Copy link
Member Author

hohwille commented Apr 9, 2019

I can only reproduce this issue on windows and still have no clue why it is happening. Maybe some bug in git-bash.

@hohwille
Copy link
Member Author

hohwille commented Jun 5, 2019

As you can see in #116 this error also occurs on mac and not only on windows/git-bash.
Maybe again an invisible unicode character or some nonsense like that.

@hohwille hohwille mentioned this issue Jun 5, 2019
Merged
@hohwille
Copy link
Member Author

hohwille commented Jun 5, 2019

Bingo. Gotcha. BTW: this invisible unicode character is produced by TextMate on MacOS when you type [Ctrl][Space]. Nasty. However, finally fixed.

hohwille added a commit that referenced this issue Jun 5, 2019
@hohwille
#89: fixed command not found error (#121)
affb156
@hohwille
Copy link
Member Author

hohwille commented Jun 5, 2019

Finally merged and therefore done.

@hohwille hohwille closed this as completed Jun 5, 2019
@hohwille hohwille mentioned this issue Jul 29, 2019
Merged
hohwille added a commit that referenced this issue Jul 29, 2019
@hohwille
#145: #149: #150: #84: #89: various fixes (#148)
f891f21 
* #145: improved verification of eclipse installation
* #145: fixed/improved installation to auto-detect if archive has a single top-level folder (except macos *.app dir) to omit in installation dir
* #84: install CobiGen from public update site
* #89: fixed another invisible unicode space character
* #148: updated vscode to 1.36.1
* #145: fixed proper download URL for vscode on windows to prevent broken ZIP download issue
* #145: fixed node installation verification to work also on windows
* #150: fixed m2e lifecylce-mapping config
* #149: prevent eclipse lock stopping to launch other IDEs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bash related to bash shell or scripts bug Something isn't working help wanted Extra attention is needed scripts related to shell scripts (bash and CMD) windows specific for Microsoft Windows OS
Projects
None yet
Milestone
release:3.2.0
Development

No branches or pull requests
1 participant
@hohwille