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.

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

Command line not working AND back button misbehaving #506

Open
Alex-Shelega opened this issue Dec 6, 2024 · 1 comment
Open

Command line not working AND back button misbehaving #506

Alex-Shelega opened this issue Dec 6, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Alex-Shelega
Copy link

Alex-Shelega commented Dec 6, 2024

When trying to type npm start in the spf command prompt using : it does not work as well as any other commands as can be seen in the video; the back button behaviour is wrong as well .

To reproduce:
For command prompt:
1. Open cmd
2. Open spf
3. Navigate to the location (expected behaviour that it navigates (cd) in background)
4. Open command prompt (:)
5. Type a command (in this case npm start)

For back button behaviour:
1. Click backspace in a nested direction

Expected behavior: The command should be excecuted and spf be closing automatically if necessary; back button should bring to the previous/parent location, insted it brings to supposedly the home directory.

Video for visual representation: https://github.com/user-attachments/assets/6e4de35f-cb48-41b4-8cec-93e290f91595

System information:

  • OS: Windows 11 (Tiny11 if it is important)
  • Version: 23H2
  • Superfile Version: 1.1.0

I hope this helps to tackle the issue

With Respect; Thanks in advance

@Alex-Shelega Alex-Shelega added the bug Something isn't working label Dec 6, 2024
@wassup05
Copy link
Contributor

Hi there, the back-button misbehaving bug has been resolved recently... Try building from source and let us know if it works well. Regarding the npm start command, are you sure you have a script named start in your package.json ? and if there is, it is not returning with a non-zero exit code because these are the only cases where I am able to reproduce this behaviour, try defining other custom scripts and run them using npm run <script>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants