When I type in the ‘ember serve’ command on Win7, the command line remains in the state of being executed, and I can not type in any command during this time. Please give me an answer to solve this problem, thanks.
That’s how server-type executables work, they block the terminal until they are finished executing (in this case when you kill the server). In unix based systems you can use the ampersand to run things in the background but I don’t think windows has any such functionality (see here for reference). I’m not a windows expert but I think for you the solution is just “open another terminal window”. That’s actually what I do (well, tab, but same thing) and I’m on OSX so I could probably background it, i just prefer to run it in its own tab.
EDIT: I’m dumb, I should read my own links fully before linking 
apparently if you prefix the command with start /B it will background it without opening a new command prompt? I haven’t tested it but you can try playing around with it.
Based on your description, it sounds like it’s working correctly. Typically, development servers will keep running while you’re working on your app. As you run your app in the browser, they may emit information that’s useful to you, such as information about syntax errors or when rebuilds have taken place.
If I need to be doing other things at the command line, I usually open another tab or window so I can keep entering commands while the server is running.
Hope that helps!
1 Like
You are right, I can do other things by opening another window while the server is running. Thank you!
You are right. I can do other things by opening another window while the server is running. Thank you!