[ 
https://issues.apache.org/jira/browse/GSHELL-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606412#action_12606412
 ] 

Jason Warner commented on GSHELL-117:
-------------------------------------

I'm not sure if that would work or not.  The error occurs during parsing of the 
command line, which occurs before gshell attempts to determine what the command 
is or what arguments are present.  Any character replacement would have to be 
done blindly, without any knowledge of context.  I'm not familiar enough with 
all the use cases of gshell to accurately predict whether this could cause 
failures in certain situations or not.  Alternatively, we could have a check 
for the specific commands in which a file name could be provided and have 
preparsing done before the command reaches the parser on just those commands.  
That seems like a really large hack, though, and is really not a solution in my 
mind, although it's probably the easiest solution to implement that has the 
least chance of breaking other commands.  I'm having trouble coming up with a 
fix that I'd personally be comfortable with short of figuring out just what the 
parser hates so much about '\' and teaching it how to play nice.  I'm not 
familiar enough with the parser to estimate how difficult that would be.  Maybe 
someone who is more familiar with the parser or gshell as a whole could comment 
on that, or anything else I just said for that matter.  

> GShell doesn't support "\" in the path in Widnows platform
> ----------------------------------------------------------
>
>                 Key: GSHELL-117
>                 URL: https://issues.apache.org/jira/browse/GSHELL-117
>             Project: GShell
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: CLI
>    Affects Versions: 1.0-alpha-1, 1.0-alpha-2
>         Environment: Windows
>            Reporter: YunFeng Ma
>            Assignee: Jason Dillon
>             Fix For: 1.0-alpha-3
>
>
> Run the following command and get errors in Windows
> {noformat}
> deploy/deploy H:\FTP_ROOT\Build\cviewer.war
> ERROR TokenMgrError: Lexical error at line 1, column 18.  Encountered: "F" 
> (70), after : "\\"
> {noformat}
> It works fine for double slash:
> deploy/deploy H:\\FTP_ROOT\\Build\\cviewer.war
> It's not convenience for windows users.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to