-
Notifications
You must be signed in to change notification settings - Fork 3
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
Terminal User Interface Issues When Running Windows Executable from PowerShell Desktop (Version 0.1.33) #18
Comments
Thanks for the report. |
Hope this will help you in debugging your app. When running the precompiled Windows executable (version 0.3.1 - 2024-07-17), executing 'serp.exe -V' results in an incorrect configuration path: 'Config directory: C:\Users\user\AppData\Roaming\yassinebridi\serpl\config'. I had a glance at the source code, but I couldn't locate the problem. This issue may also occur with precompiled binaries on other platforms. |
Thanks, i didn't test the config on windows, the path is weird, but this shouldn't have been produced by a wrong config file, since the config file isn't necessary to run the application, the default config will be used. |
On Windows, what is the expected directory where the app sources its configuration file? %appdata%\serpl\config ? |
I'm using this package to manage config files: From their documentation, it seems that that the config should be inside Though from what you have posted earlier:
This might be the correct path too, windows might use org name(yassinebridi). |
This may be unnecessary if the application can correctly source the config file from ~\AppData\Roaming\serpl\config.json |
Seems like RipGrep returns windows line ends There seems to be another call here https://github.com/yassinebridi/serpl/blob/2a195169e14d3a871f31cac89bfef68c3524c048/src/redux/thunk/process_search.rs#L69C58-L69C64 but I haven't investigated very well. |
When running the Windows exe directly from PowerShell desktop, I encounter issues with the terminal user interface. I'm unsure if this is related to Rust's Ratatui, Windows Terminal, PowerShell itself, or another factor. Interestingly, it works fine when executed from the command prompt. I'm using version 0.1.33.
The text was updated successfully, but these errors were encountered: