<p>In my program, I'm parsing the arguments passed in on the command line to perform certain actions. However, it appears that if os.Args[1:] contains the word "do" and perhaps others, my whole program does nothing. I've tested this by removing "do" and it seems to be okay. Is there a way around this? I know that "do" is a reserved word in my command line, but shouldn't arguments following a program invocation not be treated as such? Not exactly sure why it's happening. Thanks in advance for any advice!</p>
<hr/>**评论：**<br/><br/>jamesrr39: <pre><p>do you quote do when you run your program, so it looks like <code>./myApp do</code> or <code>./myApp 'do'</code>? And which shell are you using - bash?</p></pre>ConfuciusBateman: <pre><p>I'm using zsh, and actually I just narrowed it down to what I think is the culprit: when the args contain "=>". And no, nothing is quoted when running ./myApp fun args go here => stuff stuff.</p>
<p>I get this error when => is at the end of the arguments:
zsh: parse error near `\n'</p>
<p>If => is anywhere in the middle, such as ./myProgram word word => more words, it simply exits without a message. Any ideas? => doesn't seem to be an alias for anything, so it's sort of weird. Not sure if it's worth copying the function that is causing this, it's extremely simple and just printing out the full os.Args slice so I can see what's going on. </p>
<p>Quick edit: even just echoing "=>" in my shell causes the same error, so I'm quite sure this is independent of my program.</p></pre>justinisrael: <pre><p>Zsh also interprets other characters as special, such as a question mark (?) when the arg might be a url with a query string. You have to enclose those args in quotes to prevent the shell from interpreting them</p></pre>ConfuciusBateman: <pre><p>Got it, in fact I just realized it's not the fat arrow, it's specifically '>'. </p>
<p>Would there be any other possible solution? As what I'm trying to do involves running my program with the arrow to signify something special about the text that follows. Perhaps I just need to choose a different symbol, because I don't want to have to type </p>
<pre><code>./myProgram add thing "=>" here's the special text
</code></pre></pre>justinisrael: <pre><p>Yea, you just have to accept the fact that you are using a special stream redirection symbol in a shell command. Either quote it, or quote the entire text string as a whole, or pick another symbol.</p></pre>justinisrael: <pre><p>I don't know why it would be os.Args tripping up on certain words. It just contains the args passed when the process was executed. It is probably your shell command. What kind of command are you running? They may never have made it to the actual Go process. </p></pre>skelterjohn: <pre><p>If you post the source to a simple program (say, one that prints the args) and a script that runs it to reproduce, I'm sure we can figure out what the issue is.</p>
<p>It's almost certainly an issue with how you're invoking the program, rather than an issue with the program itself.</p></pre>drvd: <pre><p>This has absolutely nothing to do with os.Args as os.Args just transports the arguments from program invocation to your code and does not do anything beside that, especially not look at the arguments provided. Stop looking where nothing is hiding and focus on what you do wrong invoking your program, especially when invoking through a shell which might do tons of stuff to what you type (and see in the terminal) before handing it down to your code.</p></pre>ConfuciusBateman: <pre><p>I responded to another person in the thread, but I believe I found the source of the problem and I don't think it has anything to do with my program. It appears that when a fat arrow ("=>") is present in the arguments to the program, zshell doesn't like it. Even if I just run echo =>, I get:</p>
<pre><code>zsh: parse error near `\n'
</code></pre>
<p>Another quick edit: it's actually just '>', not the arrow.</p></pre>
