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

installation fails under windows for users with a space in their usernames #10

Closed
mikapfl opened this issue Sep 15, 2021 · 5 comments
Closed

Comments

@mikapfl
Copy link

mikapfl commented Sep 15, 2021

Hi,

I tried installing Reel under windows as per the instructions. Running the setup script seems to work, but starting Reel doesn't work, and the error message indicates that the problem is a space in the program's path, which happens because my username has a space in it. Probably something needs more quoting? Sorry, I have no clue about windows so can't diagnose the problem further.

Cheers,

Mika

@mikapfl
Copy link
Author

mikapfl commented Sep 15, 2021

The full message in the cmd window when trying to start Reel is:

Opening Reel 1.0...
Der Befehl "C:\Users\Hein" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Drücken Sie eine beliebige Taste . . .

The user name here is "Hein Mück".

@mikapfl
Copy link
Author

mikapfl commented Sep 15, 2021

The content of my Run_Reel file is:

@ECHO off 
TITLE Reel 
CD C:\Users\Hein M�ck\PycharmProjects\Reel\Reel1.0\ 
ECHO Opening Reel 1.0... 
C:\Users\Hein M�ck\AppData\Local\Microsoft\WindowsApps\python.exe Refinement_evaluator_ver1.0.py 
PAUSE 
EXIT 

It also looks like the "ü" in my username broke.

@fgjorup
Copy link
Owner

fgjorup commented Sep 23, 2021

Hi Mika
I can change the batch file to include quotation marks around the path, but I am currently not sure how to fix the issue with special characters. However, I can add a note in the instructions, both the README.md and the quick guide, so users may fix the issue manually.

@mikapfl
Copy link
Author

mikapfl commented Sep 23, 2021

I think the special characters are actually fine, quotation marks fixed everything for me. I guess notepad can't show the special characters, but windows finds the file anyway.

@fgjorup
Copy link
Owner

fgjorup commented Sep 23, 2021

I see, well that's great!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants