search

devonfw / IDEasy

Tool to automate the setup and updates of a development environment for any project (Successor of devonfw-ide).
Apache License 2.0
11 stars 23 forks source link

IDEasy not working properly in CMD #764

Open hohwille opened 1 week ago

hohwille commented 1 week ago

Expected behavior

As a IDEasy user on Windows, I want to be able to use IDEasy also in CMD so that I can use it from some *.bat scripts or keep my odd legacy habbits ;)

Actual behavior

grafik

Steps to reproduce (bug) / Use Case of feature request (enhancement)

  1. Install IDEasy
  2. Open CMD
  3. cd to an IDEasy project
  4. run e.g. ide intellij

Related/Dependent Issues

Comments/Hints:

Affected version:

hohwille commented 17 hours ago

PR #784 does not fix this problem entirely. Good news is that starting an IDE or any tool where we create a start script for now works from CMD and from BASH. However, there is something generally broken, when we execute bash scripts in case we have been initially launched from CMD:

D:\projects\IDEasy\software\java\bin>ide install intellij
C:/Program Files/Git/mingw64/libexec/git-core\git-submodule: line 7: basename: command not found
C:/Program Files/Git/mingw64/libexec/git-core\git-submodule: line 7: sed: command not found
C:/Program Files/Git/mingw64/libexec/git-core\git-submodule: line 22: .: git-sh-setup: file not found
Running command 'C:\Program Files\Git\cmd\git.exe' with arguments '--no-pager' 'pull' '--quiet'
failed with exit code 1!
Git pull on branch master failed for repository D:\projects\_ide\urls.
Failed to update git repository at D:\projects\_ide\urls
See above error for details. If you have local changes, please stash or revert and retry.
Typically you should abort and fix the problem. Do you want to continue anyways?
Option 1: yes
Option 2: no

IMHO the shebang detection should be debugged to see what is really going on. To me it looks as if the bash script is executed by CMD without calling the real git-bash to execute it.

Workaround: Do not use CMD at all as suggested in the documentation. However, we still need to fix this.