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
What steps will reproduce the problem?
1. go to any directory out of boar on your local disk c:\temp for example
2. type boar ls
3. You get error no repository specified
4. set REPO_PATH="c:\path\to\your\repository"
5. type same command again boar ls
6. you get error: ERROR: The path c:\temp\"c:\path\to\your\repository"
What is the expected output? What do you see instead?
see above
What platform are you using? (Windows XP, Windows 7, Linux, ...)
Win7 64 bit
What version of Python are you using?
no idea, the one delivered with boar
What version of boar are you using? (Mercurial change id or daily build
date)
Boar version boar.16-Nov-2012
Please provide any additional information below.
Original issue reported on code.google.com by ph...@richard-vanek.eu on 14 Jun 2013 at 11:36
The text was updated successfully, but these errors were encountered:
Wait... Actually, turns out that the "set" command uses the entire string to
the right of the equal sign, including any citation marks.
Hence, if you replace
REPO_PATH="c:\path\to\your\repository"
with
REPO_PATH=c:\path\to\your\repository
then, it works. Windows is weird... So, not really a bug in Boar. Still,
probably a common mistake in DOS. I'll leave this bug as an open minor, and add
some kind of helpful error message.
Original comment by ekb...@gmail.com on 22 Jun 2013 at 12:32
Changed title: Misleading error message when using citation marks in the REPO_PATH in windows
Thank you for looking into it. The reason I use citation marks was that I had
space in path name to the repository and it felt like correct thing to do. Even
Command prompt in Win7 does add them automatically.
Strange is that, as you noted yourself, that when setting env. variable using
set command it take whole string until end of line. This means also all spaces
in path to repository.
-r-
Original comment by ph...@richard-vanek.eu on 13 Jul 2013 at 9:42
Original issue reported on code.google.com by
ph...@richard-vanek.eu
on 14 Jun 2013 at 11:36The text was updated successfully, but these errors were encountered: