You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug Q (quit and change directory) doesn't work on Windows.
To Reproduce
Type Q on Windows :)
Additional context
The problem is here that the current directory of the parent process must be changed after clifm (the child process) has ended. That's why a shell script is used on Unix like operating systems.
On Windows the parent process is mostly cmd.exe, the Windows command interpreter. This would need at least a real batch file with a chdir in it but I'm not sure how to start it.
But it fails also when I use a real shell like GNU bash as the parent process on Windows. Perhaps a reason is that the COMSPEC environment variable contains still cmd.exe in this case. Instead there's an additional BASH variable in this case, also a SHELL variable containing bash. But, I see the problem: every shell has it's own variables - how to find the shell that is really used?
Not that important, I just saw it doesn't work.
The text was updated successfully, but these errors were encountered:
Describe the bug
Q
(quit and change directory) doesn't work on Windows.To Reproduce
Type
Q
on Windows :)Additional context
The problem is here that the current directory of the parent process must be changed after clifm (the child process) has ended. That's why a shell script is used on Unix like operating systems.
On Windows the parent process is mostly cmd.exe, the Windows command interpreter. This would need at least a real batch file with a chdir in it but I'm not sure how to start it.
But it fails also when I use a real shell like GNU bash as the parent process on Windows. Perhaps a reason is that the COMSPEC environment variable contains still cmd.exe in this case. Instead there's an additional BASH variable in this case, also a SHELL variable containing bash. But, I see the problem: every shell has it's own variables - how to find the shell that is really used?
Not that important, I just saw it doesn't work.
The text was updated successfully, but these errors were encountered: